# CVE-2007-1886: Integer overflow in n/a

> An integer overflow in PHP's str_replace function allows attackers to cause an off-by-one error, potentially leading to undefined behavior or crashes.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 6 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cxj5-f766-7wwc

## What is CVE-2007-1886?

CVE-2007-1886 is a medium-severity vulnerability in Php Php, published on 6 Apr 2007. It can be exploited over the network.

### Official description

Integer overflow in the str_replace function in PHP 4.4.5 and PHP 5.2.1 allows context-dependent attackers to have an unknown impact via a single character search string in conjunction with a single character replacement string, which causes an "off by one overflow."

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

It affects 1 product.


Products: Php Php.

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

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

## Is CVE-2007-1886 being exploited?

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

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

What it is: CVE-2007-1886 is a medium-severity vulnerability in Php Php, published on 6 Apr 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-1886 in the wild and no public exploit code.

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

## Sources

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

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