# CVE-2005-1921: Code injection in n/a

> Remote attackers can execute arbitrary PHP code via unsanitized XML input in PEAR XML_RPC and PHPXMLRPC libraries.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2005-2116, DSA-746-1, DSA-747-1, GHSA-7mjj-9265-43wm

## What is CVE-2005-1921?

CVE-2005-1921 is a high-severity code injection vulnerability in Debian Debian Linux, published on 1 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2005-1921?

It affects 5 products.


Products: Debian Debian Linux, Drupal Drupal, Gggeek Phpxmlrpc, Php Xml Rpc, Tiki Tikiwiki Cms\/Groupware.

## How do I fix CVE-2005-1921?

Upgrade to a fixed version.

## Is CVE-2005-1921 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1921 exists.

Public exploit code:

- PHP XML-RPC Arbitrary Code Execution (metasploit)
- XML-RPC Library 1.3.0 - 'xmlrpc.php' Remote Code Injection (exploitdb)
- XML-RPC Library 1.3.0 - 'xmlrpc.php' Remote Command Execution (2) (exploitdb)
- XML-RPC Library 1.3.0 - 'xmlrpc.php' Remote Command Execution (3) (exploitdb)
- XML-RPC Library 1.3.0 - 'xmlrpc.php' Arbitrary Code Execution (Metasploit) (exploitdb)
- PHPXMLRPC < 1.1 - Remote Code Execution (exploitdb)

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1921 and fix it if it is affected.

What it is: CVE-2005-1921 is a high-severity code injection vulnerability in Debian Debian Linux, published on 1 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1921 exists.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-1921/ (Markdown: https://insights.sbomify.com/CVE-2005-1921/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-1921
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-1921
- OSV: https://osv.dev/vulnerability/CVE-2005-1921

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-1921/
Summaries are generated and may contain mistakes; the official description above is the record.