Sage Pay Direct Module
Vendor:
First CVE: Nov 4, 2012 · Active for 13 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
5.8
Avg CVSS
Higher Avg CVSS than 21% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Sage Pay Direct Module over time
Volume of CVEsAvg CVSS Base Score
First CVE
Nov 4, 2012
13 years ago
Most Recent CVE
Nov 4, 2012
5,014 days ago
CVE Severity & Scoring
Sage Pay Direct Module1 CVEs
100%
All CVEs353,240 CVEs
45%
40%
11%
Medium
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown1 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown1 (100.0%)
User Interaction
None0 (0.0%)
Unknown1 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown1 (100.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2012-5792MEDIUM The Sage Pay Direct module in osCommerce does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certi | Nov 4, 2012 | 5.8 | 18 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Sage Pay Direct Module
Top CWEs
Versions
No cataloged versions.