CVE-2021-34961
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFoxit PDF Editor Ink Annotation Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Editor. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of Annotation objects. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14363.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a Use-After-Free (UAF) vulnerability in Foxit PDF Editor's Ink Annotation handling. The software fails to validate object existence before performing operations on it, allowing an attacker to manipulate memory through malicious PDF files and achieve arbitrary code execution in the current process context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.1.5.37672= 11.0.0.49893= 11.0.1.49938<= 11.0.1.49938CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Foxit PDF Editor or Reader is installedOpen Windows Control Panel > Programs and Features, or check for Foxit PDF Editor/Foxit Reader in the program files directory (typically C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\)Affected if Foxit PDF Editor or Foxit PDF Reader is present on the system
-
Identify the installed Foxit product versionRight-click the Foxit executable (FoxitPDFEditor.exe or FoxitReader.exe), select Properties, then go to the Details tab to view the Product VersionAffected if The version cannot be determined or is within the affected ranges
-
Compare installed version against affected rangesFor Foxit PDF Editor: check if version is <= 10.1.5.37672, or exactly 11.0.0.49893, or exactly 11.0.1.49938. For Foxit PDF Reader: check if version is <= 11.0.1.49938Affected if The installed version matches any of these: Foxit PDF Editor <= 10.1.5.37672, = 11.0.0.49893, = 11.0.1.49938, or Foxit PDF Reader <= 11.0.1.49938
-
Confirm the vulnerability trigger conditionThis is a Use-After-Free in Ink Annotation handling - the flaw is triggered when opening a PDF file containing specially crafted Ink Annotations. There is no special configuration to enable; the vulnerable code path executes when processing such PDFsAffected if The software processes PDF files with Ink Annotations and the version is affected
If Foxit PDF Editor or Reader is installed and the version falls within the affected ranges (Editor <= 10.1.5.37672, = 11.0.0.49893, = 11.0.1.49938 or Reader <= 11.0.1.49938), the environment is vulnerable to this Use-After-Free flaw when opening malicious PDF files with Ink Annotations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor security patch by updating Foxit PDF Editor to the latest version; until then, avoid opening untrusted PDF files and disable JavaScript execution in the PDF reader if possible.
Foxit PDF Editor/PDF Reader version > 11.0.1.49938 (check Foxit website for exact patched release)
- 1. Open Foxit PDF Editor or PDF Reader application
- 2. Navigate to Help > About Foxit PDF Editor/Reader to check the current version
- 3. Visit the official Foxit website at www.foxit.com to download the latest version
- 4. Download and install the most recent release of Foxit PDF Editor or PDF Reader
- 5. Verify the version number in Help > About matches a version newer than 11.0.1.49938
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-34961 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data