CVE-2023-27366
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 Reader Doc Object Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader. 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 Doc 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-20225.
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 vulnerability in Foxit PDF Reader's Doc object handling. The software fails to validate object existence before performing operations, allowing an attacker to exploit freed memory and execute arbitrary code through malicious PDF files or web pages.
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.11.37866>= 11.0.0.49893, < 11.2.5.53785>= 12.0.0.12394, < 12.1.1.15289< 12.1.1.15289CVSS 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.
-
Identify if Foxit PDF software is installedOn Windows, check for Foxit PDF Reader or Foxit PDF Editor in the programs list via Control Panel > Programs and Features, or search for 'Foxit' in the Start menu. On macOS, check /Applications folder for Foxit applications.Affected if Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Determine the installed Foxit versionIn Foxit PDF Reader or Editor, click Help > About Foxit PDF Reader (or About Foxit PDF Editor). The version number is displayed in the dialog box. Alternatively, right-click the application in the Start menu, select Properties, and check the version field.Affected if The displayed version falls outside the safe ranges: for Reader, version 12.1.1.15289 or higher is patched; for Editor, versions 10.1.11.37866 or higher, or 11.2.5.53785 or higher, or 12.1.1.15289 or higher are patched
-
Compare against affected version rangesDocument the exact version number and compare it to the affected ranges: Reader: any version below 12.1.1.15289; Editor: any version below 10.1.11.37866, OR between 11.0.0.49893 and 11.2.5.53784, OR between 12.0.0.12394 and 12.1.1.15288Affected if The installed version matches any of these ranges, indicating the vulnerability is present
A user is affected if Foxit PDF Reader version is below 12.1.1.15289, or Foxit PDF Editor version is below 10.1.11.37866, or falls between 11.0.0.49893-11.2.5.53784, or between 12.0.0.12394-12.1.1.15288.
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 · scoped10.1.11.3786611.2.5.5378512.1.1.15289
Update Foxit PDF Reader to the latest patched version; avoid opening untrusted PDF files or visiting malicious web pages.
Foxit PDF Editor: 10.1.11.37866+ (10.x), 11.2.5.53785+ (11.x), 12.1.1.15289+ (12.x); Foxit PDF Reader: 12.1.1.15289+
- Identify the currently installed Foxit PDF Editor or Foxit PDF Reader version from the Help > About menu
- For Foxit PDF Editor version 10.x: Upgrade to version 10.1.11.37866 or later
- For Foxit PDF Editor version 11.x: Upgrade to version 11.2.5.53785 or later
- For Foxit PDF Editor version 12.x: Upgrade to version 12.1.1.15289 or later
- For Foxit PDF Reader: Upgrade to version 12.1.1.15289 or later
- Download the updated version from the official Foxit website at www.foxit.com
- Verify the version after installation by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 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-2023-27366 — 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-2023-27366 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