LiveActive security incident?Get immediate response
CVE Record

CVE-2013-0235: The XMLRPC API in WordPress before 3.5.1 allows remote attackers to send HTTP requests to intranet servers,...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older WordPress versions let an outside user abuse the pingback feature to make the site contact internal systems. That could expose intranet reachability or support port-scanning from the WordPress server. The evidence points to WordPress before 3.5.1; no source here proves active exploitation. Exposure is most likely on public WordPress sites running versions before 3.5.1 with the XMLRPC pingback API reachable. Modern, supported WordPress installations should not match the stated vulnerable version range. Treat this as a legacy exposure issue. It is not presented as KEV-active, but affected public WordPress sites can become a proxy into internal networks. Upgrade or retire old instances during normal vulnerability remediation cycles, faster for internet-facing business systems. Mitigation focus: Upgrade WordPress installations older than 3.5.1 to 3.5.1 or a supported current release.; Check WordPress vendor guidance for any XMLRPC or pingback-specific hardening recommendations.; Prioritize externally reachable legacy WordPress systems before internal-only sites..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-0235 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.