Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2014-5266: XML Entity Expansion DoS in Incutio XML-RPC (IXR) Library (WordPress, Drupal)

Published Aug 18, 2014 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS25.2%98th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Debian ProjectDrupalWordpress
IdentifiersCVE-2014-5266CWE-400

CVE-2014-5266 is a denial-of-service vulnerability in the Incutio XML-RPC (IXR) Library, used by WordPress before 3.9.2 and Drupal 6.x before 6.33 and 7.x before 7.31. The library fails to limit the number of elements in an XML document, allowing remote attackers to send specially crafted, large XML payloads that consume excessive CPU resources during parsing. This is distinct from CVE-2014-5265 and affects any application using the vulnerable IXR library.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to cause a denial of service (DoS) condition by exhausting CPU resources on the target server, potentially rendering the affected WordPress or Drupal site unresponsive. This can be leveraged for service disruption but does not allow code execution or data compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, consider disabling XML-RPC functionality if not required, or deploy web application firewalls (WAFs) or reverse proxies to filter and limit large or complex XML payloads. Monitor server resource usage for abnormal spikes indicative of attempted exploitation.

Remediation

Patch, then assume compromise.

Upgrade WordPress to version 3.9.2 or later, and Drupal to 6.33, 7.31, or later. Ensure that any standalone or embedded use of the Incutio XML-RPC (IXR) Library is updated to a version that implements proper limits on XML document complexity and size.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
DrupalDrupalapplication
WordpressWordpressapplication
FAQ

Frequently asked questions

Is CVE-2014-5266 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2014-5266 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2014-5266?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2014-5266, the earliest disclosed Aug 6, 2014.
Is there a patch for CVE-2014-5266?
Upgrade WordPress to version 3.9.2 or later, and Drupal to 6.33, 7.31, or later. Ensure that any standalone or embedded use of the Incutio XML-RPC (IXR) Library is updated to a version that implements proper limits on XML document complexity and size.
What products are affected by CVE-2014-5266?
Drupal, Wordpress, and Debian Project Debian Linux.
How severe is CVE-2014-5266?
CVE-2014-5266 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 25.2% (98th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.