# CVE-2026-25239: PEAR is Vulnerable to SQL Injection in apidoc_queue Insert via Unescaped Filename

> Attackers can manipulate SQL queries via unescaped filenames in PEAR's apidoc queue, potentially reading or modifying data.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-f9mg-x463-3vxg

## What is CVE-2026-25239?

CVE-2026-25239 is a high-severity SQL injection vulnerability in pearweb, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PEAR is a framework and distribution system for reusable PHP components. Prior to version 1.33.0, a SQL injection vulnerability in apidoc queue insertion can allow query manipulation if an attacker can influence the inserted filename value. This issue has been patched in version 1.33.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-25239?

It affects 1 product.


Products: Pear Pearweb.

## How do I fix CVE-2026-25239?

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

## Is CVE-2026-25239 being exploited?

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

## Other vulnerabilities in pearweb

- [CVE-2026-25241](https://insights.sbomify.com/CVE-2026-25241/): PEAR is Vulnerable to SQL Injection in /get/<package>/<version> Endpoint (critical 9.3)
- [CVE-2026-25237](https://insights.sbomify.com/CVE-2026-25237/): PEAR is Vulnerable to PHP Code Execution via preg_replace /e in Bug Update Emails (critical 9.2)
- [CVE-2026-25238](https://insights.sbomify.com/CVE-2026-25238/): PEAR is Vulnerable to SQL Injection in Bug Subscription Deletion via Weak Email Validation (critical 9.2)
- [CVE-2026-25235](https://insights.sbomify.com/CVE-2026-25235/): PEAR Has a Predictable Verification Hash in Election Account Requests (high 8.2)
- [CVE-2026-25233](https://insights.sbomify.com/CVE-2026-25233/): PEAR Has a Roadmap Authorization Bypass via Operator Precedence Bug (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25239 and fix it if it is affected.

What it is: CVE-2026-25239 is a high-severity SQL injection vulnerability in pearweb, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25239 in the wild and no public exploit code.

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

## Sources

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

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