CVE-2021-34956
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 Underline 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-14357.
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 handling of Underline Annotations. The vulnerability exists because the code fails to validate the existence of an object before performing operations on it, allowing an attacker to access freed memory and execute arbitrary code in the context of the current process. Exploitation requires user interaction via a malicious PDF file or webpage.
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 software is installedOpen Windows Settings > Apps > Apps & Features, or check the following registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* for entries containing 'Foxit'. Also check common install paths: C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\Affected if No Foxit PDF Editor or Reader is found on the system, the system is not affected by this specific vulnerability
-
Identify the installed Foxit product typeIn the registry or install folder identified in step 1, determine whether the product is Foxit PDF Editor or Foxit PDF Reader. Check the DisplayName in the registry uninstall entry or the executable name in the installation folder (FoxitPDFEditor.exe vs FoxitPDFReader.exe)Affected if The product is neither Foxit PDF Editor nor Foxit PDF Reader
-
Determine the exact installed versionRight-click the Foxit executable (FoxitPDFEditor.exe or FoxitPDFReader.exe) in the installation folder, select Properties, then view the Details tab for Product Version. Alternatively, open the Foxit application, go to Help > About to display the version numberAffected if Unable to determine the version number for comparison
-
Compare version against affected rangesFor Foxit PDF Editor: compare your version against <= 10.1.5.37672, = 11.0.0.49893, or = 11.0.1.49938. For Foxit PDF Reader: compare against <= 11.0.1.49938. Note that versions 10.1.5.37673 through 10.1.x and 11.0.0.x (except exact 11.0.0.49893) may not be affectedAffected if The installed version exactly matches one of the affected version numbers or falls within the <= ranges specified (Editor: 10.1.5.37672 or lower; Reader: 11.0.1.49938 or lower)
-
Verify Underline annotation capability is presentOpen any PDF in the Foxit application, right-click and look for annotation tools. Underline annotation is a standard feature in Foxit PDF products and cannot be disabled. This check confirms the vulnerable feature exists in the installed productAffected if The Underline annotation option is available in the context menu or annotation toolbar
The system is affected if Foxit PDF Editor (version 10.1.5.37672 or lower, or exactly 11.0.0.49893 or 11.0.1.49938) or Foxit PDF Reader (version 11.0.1.49938 or lower) is installed and the Underline annotation feature is accessible.
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.
From vendor dataUpdate Foxit PDF Editor to the latest version to obtain the vendor patch. Until then, avoid opening untrusted PDF files or visiting untrusted websites that could deliver malicious PDF content.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34956 — 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-34956 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