# CVE-2007-3779: Path traversal in n/a

> Remote attackers can include and execute arbitrary local files via the MOD parameter in the GPG plugin for Squirrelmail.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** No
- **Published:** 15 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wwr9-w8xj-rh7w

## What is CVE-2007-3779?

CVE-2007-3779 is a medium-severity path traversal vulnerability in n/a, published on 15 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PHP local file inclusion vulnerability in gpg_pop_init.php in the G/PGP (GPG) Plugin before 20070707 for Squirrelmail allows remote attackers to include and execute arbitrary local files, related to the MOD parameter.

## Which versions are affected by CVE-2007-3779?

It affects 1 product.


Products: Squirrelmail Gpg Plugin.

## How do I fix CVE-2007-3779?

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

## Is CVE-2007-3779 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1924](https://insights.sbomify.com/CVE-2005-1924/): Command injection in n/a (critical 9.3)
- [CVE-2007-3778](https://insights.sbomify.com/CVE-2007-3778/): Command injection in n/a (high 7.5)
- [CVE-2007-3636](https://insights.sbomify.com/CVE-2007-3636/): Command injection in n/a (high 7.5)
- [CVE-2007-3634](https://insights.sbomify.com/CVE-2007-3634/): Command injection in n/a (medium 6.5)
- [CVE-2006-4169](https://insights.sbomify.com/CVE-2006-4169/): Path traversal in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3779 and fix it if it is affected.

What it is: CVE-2007-3779 is a medium-severity path traversal vulnerability in n/a, published on 15 Jul 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-3779 in the wild and no public exploit code.

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-2007-3779/ (Markdown: https://insights.sbomify.com/CVE-2007-3779/index.md)
```

## Sources

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

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