# CVE-2007-1825: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the PHP imap_mail_compose function using a long boundary string.

- **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:** 2 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mpvc-cmfr-5chg

## What is CVE-2007-1825?

CVE-2007-1825 is a high-severity memory corruption vulnerability in Php Php, published on 2 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the imap_mail_compose function in PHP 5 before 5.2.1, and PHP 4 before 4.4.5, allows remote attackers to execute arbitrary code via a long boundary string in a type.parameters field. NOTE: as of 20070411, it appears that this issue might be subsumed by CVE-2007-0906.3.

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2007-1825 being exploited?

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

Public exploit code:

- PHP 5.1.6 - 'Imap_Mail_Compose()' Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1825 is a high-severity memory corruption vulnerability in Php Php, published on 2 Apr 2007. 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-2007-1825 exists.

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

## Sources

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

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