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

> Remote attackers can exploit unsafe variable extraction to execute code, read or modify user preferences, and write arbitrary files in SquirrelMail.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/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:** 13 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wj45-2qrw-hh28

## What is CVE-2005-2095?

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

### Official description

options_identities.php in SquirrelMail 1.4.4 and earlier uses the extract function to process the $_POST variable, which allows remote attackers to modify or read the preferences of other users, conduct cross-site scripting XSS) attacks, and write arbitrary files.

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

It affects 1 product.


Products: Squirrelmail Squirrelmail.

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

Upgrade to a fixed version.

## Is CVE-2005-2095 being exploited?

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

Public exploit code:

- SquirrelMail < 1.4.5-RC1 - Arbitrary Variable Overwrite (exploitdb)

## 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-2095 and fix it if it is affected.

What it is: CVE-2005-2095 is a medium-severity code injection vulnerability in Squirrelmail Squirrelmail, published on 13 Jul 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-2095 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-2095/ (Markdown: https://insights.sbomify.com/CVE-2005-2095/index.md)
```

## Sources

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

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