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.
Published 2013-07-08 20:55:01
Updated 2013-07-08 20:55:01
Source Red Hat, Inc.
View at NVD,   CVE.org
Vulnerability category: Server-side request forgery (SSRF)

Threat overview for CVE-2013-0235

Top countries where our scanners detected CVE-2013-0235
Top open port discovered on systems with this issue 80
IPs affected by CVE-2013-0235 34
Threat actors abusing to this issue? Yes
Find out if you* are affected by CVE-2013-0235!
*Directly or indirectly through your vendors, service providers and 3rd parties. Powered by attack surface intelligence from SecurityScorecard.

Exploit prediction scoring system (EPSS) score for CVE-2013-0235

Probability of exploitation activity in the next 30 days: 13.01%

Percentile, the proportion of vulnerabilities that are scored at or less: ~ 95 % EPSS Score History EPSS FAQ

Metasploit modules for CVE-2013-0235

  • Wordpress Pingback Locator
    First seen: 2020-04-26
    auxiliary/scanner/http/wordpress_pingback_access
    This module will scan for wordpress sites with the Pingback API enabled. By interfacing with the API an attacker can cause the wordpress site to port scan an external target and return results. Refer to the wordpress_pingback_portscanner module. Thi

CVSS scores for CVE-2013-0235

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source
6.4
MEDIUM AV:N/AC:L/Au:N/C:P/I:P/A:N
10.0
4.9
NIST

References for CVE-2013-0235

Products affected by CVE-2013-0235

This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!