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

> Remote attackers can inject local code into SquirrelMail via custom preference handlers when register_globals is enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9f2f-wxmh-4h2q

## What is CVE-2005-0075?

CVE-2005-0075 is a medium-severity code injection vulnerability in Squirrelmail Squirrelmail, published on 6 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

prefs.php in SquirrelMail before 1.4.4, with register_globals enabled, allows remote attackers to inject local code into the SquirrelMail code via custom preference handlers.

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

It affects 1 product.


Products: Squirrelmail Squirrelmail.

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

Upgrade to a fixed version.

## Is CVE-2005-0075 being exploited?

There is no known exploitation of CVE-2005-0075 in the wild and no public exploit code.

## Other vulnerabilities in Squirrelmail Squirrelmail

- [CVE-2002-0516](https://insights.sbomify.com/CVE-2002-0516/): Command injection in n/a (critical 10.0)
- [CVE-2020-14932](https://insights.sbomify.com/CVE-2020-14932/): Deserialization in n/a (critical 9.8)
- [CVE-2020-14933](https://insights.sbomify.com/CVE-2020-14933/): Deserialization in n/a (high 8.8)
- [CVE-2017-7692](https://insights.sbomify.com/CVE-2017-7692/): Command injection in n/a (high 8.8)
- [CVE-2007-2631](https://insights.sbomify.com/CVE-2007-2631/): Cross-site request forgery in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0075 is a medium-severity code injection vulnerability in Squirrelmail Squirrelmail, published on 6 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0075 in the wild and no public exploit code.

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

## Sources

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

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