CVE-2011-5194 json
Cross-site scripting (XSS) vulnerability in vendors/samswhois/samswhois.inc.php in the Whois Search plugin before 1.4.2.3 for WordPress all…
published 2012-09-23 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-5094
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in vendors/samswhois/samswhois.inc.php in the Whois Search plugin before 1.4.2.3 for WordPress allows remote attackers to inject arbitrary web script or HTML via the domain parameter, a different vulnerability than CVE-2011-5193.
Patch / fix
Exploit prediction
2.24% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- plugins.trac.wordpress.org http://plugins.trac.wordpress.org/changeset/482954/wordpress-whois-search referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/51244 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/files/view/108271/wpwhois-xss.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/482954/wordpress-whois-search
exploit, patch
-
securityfocus.com
/bid/51244
vdb-entry, exploit
-
packetstormsecurity.org
/files/view/108271/wpwhois-xss.txt
exploit
-
secunia.com
/advisories/47428
third-party-advisory, vendor-advisory
- wordpress.org /extend/plugins/wordpress-whois-search/changelog/
-
exchange.xforce.ibmcloud.com
/vulnerabilities/72074
vdb-entry
Sources
- CVE List CVE-2011-5194
- NVD CVE-2011-5194
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.