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

> Remote attackers can execute arbitrary PHP code in ATutor via eval injection in forum.inc.php, leading to full system compromise.

- **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:** No
- **Published:** 1 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9gc7-f279-pcx9

## What is CVE-2005-3405?

CVE-2005-3405 is a high-severity code injection vulnerability in n/a, published on 1 Nov 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ATutor 1.4.1 through 1.5.1-pl1 allows remote attackers to execute arbitrary PHP functions via a direct request to forum.inc.php with a modified addslashes parameter with either the (1) asc or (2) desc parameters set, possibly due to an eval injection vulnerability.

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


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

No fix has been published for CVE-2005-3405 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-3405 being exploited?

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

Public exploit code:

- ATutor 1.x - 'forum.inc.php' Arbitrary Command Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3405 is a high-severity code injection vulnerability in n/a, published on 1 Nov 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-3405 exists.

Affected product: n/a. 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-3405/ (Markdown: https://insights.sbomify.com/CVE-2005-3405/index.md)
```

## Sources

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

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