CVE-2013-0235
The XMLRPC API in WordPress before 3.5.1 allows remote attackers to send HTTP requests to intranet servers, and conduct port-scanning attacks, by specifying a crafted source URL for a pingback, related to a Server-Side Request Forgery (SSRF) issue.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 28.9%, higher than 98% of all known CVEs. Patch or mitigate before the next change window.
Description
The XMLRPC API in WordPress before 3.5.1 allows remote attackers to send HTTP requests to intranet servers, and conduct port-scanning attacks, by specifying a crafted source URL for a pingback, related to a Server-Side Request Forgery (SSRF) issue.
- CVSS 2.0
- 6.4 MEDIUMAV:N/AC:L/Au:N/C:P/I:P/A:N
- EPSS
- 28.86% probability · 98th percentile
- CISA KEV
- Not listed
- Affected
- wordpress/wordpress
- Source
- secalert@redhat.com
References
- http://codex.wordpress.org/Version_3.5.1
- http://core.trac.wordpress.org/changeset/23330Exploit, Patch
- http://wordpress.org/news/2013/01/wordpress-3-5-1/
- http://www.acunetix.com/blog/web-security-zone/wordpress-pingback-vulnerability/
- https://bugzilla.redhat.com/show_bug.cgi?id=904120
- http://codex.wordpress.org/Version_3.5.1
- http://core.trac.wordpress.org/changeset/23330Exploit, Patch
- http://wordpress.org/news/2013/01/wordpress-3-5-1/
- http://www.acunetix.com/blog/web-security-zone/wordpress-pingback-vulnerability/
- https://bugzilla.redhat.com/show_bug.cgi?id=904120
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.