VIR Vulnerability Intelligence Relay

CVE-2013-2199

medium
Published 2013-07-08 · Modified 2026-04-29
💬 Discuss on Community ✚ Propose mitigation
CVSS v3
—
CVSS v4 NEW
—
not yet in upstream
VIR risk
4.3

Description

The HTTP API in WordPress before 3.5.2 allows remote attackers to send HTTP requests to intranet servers via unspecified vectors, related to a Server-Side Request Forgery (SSRF) issue, a similar vulnerability to CVE-2013-0235.

Predictions

Exploit likelihood
20%
Patch ETA
—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact
OSVersionStatusFixed in
debian debianbookwormfixed3.5.2+dfsg-1
debian debianbullseyefixed3.5.2+dfsg-1
debian debianforkyfixed3.5.2+dfsg-1
debian debiansidfixed3.5.2+dfsg-1
debian debiantrixiefixed3.5.2+dfsg-1

Application impact
VendorProductVersionsFixed
wordpress wordpresswordpress{"endIncluding":"3.5.1"}
wordpress wordpresswordpress0.71
wordpress wordpresswordpress1.0
wordpress wordpresswordpress1.0.1
wordpress wordpresswordpress1.0.2
wordpress wordpresswordpress1.1.1
wordpress wordpresswordpress1.2
wordpress wordpresswordpress1.2.1
wordpress wordpresswordpress1.2.2
wordpress wordpresswordpress1.2.3
wordpress wordpresswordpress1.2.4
wordpress wordpresswordpress1.2.5
wordpress wordpresswordpress1.3
wordpress wordpresswordpress1.3.2
wordpress wordpresswordpress1.3.3
wordpress wordpresswordpress1.5
wordpress wordpresswordpress1.5.1
wordpress wordpresswordpress1.5.1.1
wordpress wordpresswordpress1.5.1.2
wordpress wordpresswordpress1.5.1.3
wordpress wordpresswordpress1.5.2
wordpress wordpresswordpress1.6.2
wordpress wordpresswordpress2.0
wordpress wordpresswordpress2.0.1
wordpress wordpresswordpress2.0.2
wordpress wordpresswordpress2.0.4
wordpress wordpresswordpress2.0.5
wordpress wordpresswordpress2.0.6
wordpress wordpresswordpress2.0.7
wordpress wordpresswordpress2.0.8
wordpress wordpresswordpress2.0.9
wordpress wordpresswordpress2.0.10
wordpress wordpresswordpress2.0.11
wordpress wordpresswordpress2.1
wordpress wordpresswordpress2.1.1
wordpress wordpresswordpress2.1.2
wordpress wordpresswordpress2.1.3
wordpress wordpresswordpress2.2
wordpress wordpresswordpress2.2.1
wordpress wordpresswordpress2.2.2
wordpress wordpresswordpress2.2.3
wordpress wordpresswordpress2.3
wordpress wordpresswordpress2.3.1
wordpress wordpresswordpress2.3.2
wordpress wordpresswordpress2.3.3
wordpress wordpresswordpress2.5
wordpress wordpresswordpress2.5.1
wordpress wordpresswordpress2.6
wordpress wordpresswordpress2.6.1
wordpress wordpresswordpress2.6.2
wordpress wordpresswordpress2.6.3
wordpress wordpresswordpress2.6.5
wordpress wordpresswordpress2.7
wordpress wordpresswordpress2.7.1
wordpress wordpresswordpress2.8
wordpress wordpresswordpress2.8.1
wordpress wordpresswordpress2.8.2
wordpress wordpresswordpress2.8.3
wordpress wordpresswordpress2.8.4
wordpress wordpresswordpress2.8.5
wordpress wordpresswordpress2.8.5.1
wordpress wordpresswordpress2.8.5.2
wordpress wordpresswordpress2.8.6
wordpress wordpresswordpress2.9
wordpress wordpresswordpress2.9.1
wordpress wordpresswordpress2.9.1.1
wordpress wordpresswordpress2.9.2
wordpress wordpresswordpress3.3
wordpress wordpresswordpress3.3.1
wordpress wordpresswordpress3.3.2
wordpress wordpresswordpress3.3.3
wordpress wordpresswordpress3.4.0
wordpress wordpresswordpress3.4.1
wordpress wordpresswordpress3.4.2
wordpress wordpresswordpress3.5.0

References

CWEs

CWE-264

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.