# CVE-2013-10068: Foxit Reader <= 5.4.5.0114 Plugin URL Processing Buffer Overflow

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in Foxit Reader when processing a PDF with a long URL.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 25 May 2026
- **Also known as:** GHSA-7v2f-pw6h-v9vh

## What is CVE-2013-10068?

CVE-2013-10068 is a critical memory corruption vulnerability in Foxit Reader, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Foxit Reader versions through 5.4.5.0114, including the bundled Foxit Reader Plugin 2.2.1.530, contains a stack-based buffer overflow vulnerability in the npFoxitReaderPlugin.dll module. When a PDF file is loaded from a remote host, an overly long query string in the URL can overflow a buffer, allowing remote attackers to execute arbitrary code.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2013-10068?


## How do I fix CVE-2013-10068?

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

## Is CVE-2013-10068 being exploited?

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

Public exploit code:

- Foxit Reader Plugin URL Processing Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-10068 and fix it if it is affected.

What it is: CVE-2013-10068 is a critical memory corruption vulnerability in Foxit Reader, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-10068 exists.

Affected product: Foxit Reader. 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-2013-10068/ (Markdown: https://insights.sbomify.com/CVE-2013-10068/index.md)
```

## Sources

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

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