Payments Standard vulnerabilitiesRanked by how likely they are to be used.
Payments Standard is made by Paypal. We track 2 published vulnerabilities in it, across 1 version. None of them is on the list of flaws known to be exploited today. If you run Payments Standard, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Payments Standard vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Payments Standard's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Payments Standard flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.6%CVE-2012-5789Medium
PayPal Payments Standard PHP Library before 20120427 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 certificate, which allows...
- 0.6%CVE-2012-5790Medium
PayPal Payments Standard PHP Library 20120427 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 certificate, which allows...
Running Payments Standard? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
PayPal Payments Standard PHP Library before 20120427 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 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, related to intentional disabling of certificate-validation checks through a "FALSE" value.
- Matched to
- Payments Standard on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 2 published vulnerabilities listed under the name Payments Standard, across 1 version.
None of Payments Standard's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Payments Standard. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.