CVE-2005-1921

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 79.1% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 5 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 79%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 79%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 5

A fix is available — apply it.

Eval injection vulnerability in PEAR XML_RPC 1.3.0 and earlier (aka XML-RPC or xmlrpc) and PHPXMLRPC (aka XML-RPC For PHP or php-xmlrpc) 1.1 and earlier, as used in products such as (1) WordPress, (2) Serendipity, (3) Drupal, (4) egroupware, (5) MailWatch, (6) TikiWiki, (7) phpWebSite, (8) Ampache, and others, allows remote attackers to execute arbitrary PHP code via an XML file, which is not properly sanitized before being used in an eval statement.

Live · internet exposure

5 internet-exposed hosts are running an affected version of CVE-2005-1921 right now.

across 5 countries (Australia, Brazil, Ireland, Spain, Switzerland)top: drupal
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
70(Track)
EG Risk 70/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation79% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
79%
EPSS %ILE
100%
KEV
Not listed

Published

July 5, 2005

Last Modified

April 16, 2026

References (100)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuphp4-pear () @ hoary2026-05-31ubuntu
redhatphp-0:4.3.9-3.72005-07-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 13:26 UTCEG score recompute▲ 7.50
  2. 2026-07-24 14:11 UTCEPSS rescore
  3. 2026-07-23 00:48 UTCEG score recompute
  4. 2026-07-23 00:28 UTCEG score recompute▼ 8.00
  5. 2026-07-22 23:52 UTCEG score recompute▲ 8.00
  6. 2026-07-22 21:32 UTCEG score recompute▼ 9.00
  7. 2026-07-15 16:53 UTCEPSS rescore
  8. 2026-07-13 06:07 UTCEPSS rescore
  9. 2026-07-13 06:07 UTCEPSS rescore
  10. 2026-07-11 08:22 UTCEPSS rescore
  11. 2026-07-11 08:22 UTCEPSS rescore
  12. 2026-07-02 14:00 UTCEPSS rescore
  13. 2026-07-01 15:01 UTCEPSS rescore
  14. 2026-06-28 04:52 UTCEPSS rescore
  15. 2026-06-25 13:46 UTCEPSS rescore
  16. 2026-06-24 14:01 UTCEPSS rescore
  17. 2026-06-23 21:29 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-16 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-15 17:44 UTCEPSS rescore
  23. 2026-06-13 22:56 UTCEPSS rescore
  24. 2026-06-12 23:08 UTCEPSS rescore
  25. 2026-06-11 13:55 UTCEPSS rescore
Show 22 more
  1. 2026-06-10 13:17 UTCEPSS rescore
  2. 2026-06-08 14:13 UTCEPSS rescore
  3. 2026-06-06 13:44 UTCEPSS rescore
  4. 2026-06-06 13:44 UTCEPSS rescore
  5. 2026-06-05 22:43 UTCEPSS rescore
  6. 2026-06-05 22:43 UTCEPSS rescore
  7. 2026-05-31 12:47 UTCEG score recompute
  8. 2026-05-31 12:47 UTCVendor advisory
  9. 2026-05-31 12:47 UTCGHSA enrichment
  10. 2026-05-31 00:13 UTCEPSS rescore
  11. 2026-05-31 00:13 UTCEPSS rescore
  12. 2026-05-29 13:40 UTCEPSS rescore
  13. 2026-05-29 13:40 UTCEPSS rescore
  14. 2026-05-28 13:42 UTCEPSS rescore
  15. 2026-05-28 13:42 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-26 13:41 UTCEPSS rescore
  18. 2026-05-26 13:41 UTCEPSS rescore
  19. 2026-05-22 21:15 UTCEPSS rescore
  20. 2026-05-20 22:36 UTCEPSS rescore
  21. 2026-05-20 22:36 UTCEPSS rescore
  22. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(6 references)

Working exploit code is in the public domain (1 Metasploit module) (5 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-43829
    First seen Jul 2, 2015

    PHPXMLRPC < 1.1 - Remote Code Execution

    Open source ↗
  • Exploit-DBEDB-16882✓ verified
    First seen Jul 25, 2010

    XML-RPC Library 1.3.0 - 'xmlrpc.php' Arbitrary Code Execution (Metasploit)

    Open source ↗
  • Exploit-DBEDB-1083✓ verified
    First seen Jul 4, 2005

    XML-RPC Library 1.3.0 - 'xmlrpc.php' Remote Command Execution (2)

    Open source ↗
  • Exploit-DBEDB-1084✓ verified
    First seen Jul 4, 2005

    XML-RPC Library 1.3.0 - 'xmlrpc.php' Remote Command Execution (3)

    Open source ↗
  • Exploit-DBEDB-1078✓ verified
    First seen Jul 1, 2005

    XML-RPC Library 1.3.0 - 'xmlrpc.php' Remote Code Injection

    Open source ↗
  • Metasploitexploit/unix/webapp/php_xmlrpc_eval✓ verified
    First seen Jun 29, 2005

    PHP XML-RPC Arbitrary Code Execution

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2005-1921?
CVE-2005-1921 is a high vulnerability published on July 5, 2005. Eval injection vulnerability in PEAR XML_RPC 1.3.0 and earlier (aka XML-RPC or xmlrpc) and PHPXMLRPC (aka XML-RPC For PHP or php-xmlrpc) 1.1 and earlier, as used in products such as (1) WordPress, (2) Serendipity, (3) Drupal, (4) egroupware, (5) MailWatch, (6) TikiWiki, (7) phpWebSite, (8) Ampache,…
When was CVE-2005-1921 disclosed?
CVE-2005-1921 was first published in the National Vulnerability Database on July 5, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-1921 actively exploited?
CVE-2005-1921 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79% probability of exploitation in the next 30 days, which ranks it in the top 0.4% of all scored CVEs.
How do I remediate CVE-2005-1921?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-1921, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-1921

Explore →

Is Your Infrastructure Affected by CVE-2005-1921?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs