CVE-2023-27363
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 exportXFAData Exposed Dangerous Method 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 exportXFAData method. The application exposes a JavaScript interface that allows writing arbitrary files. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-19697.
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 confidenceFoxit PDF Reader contains a vulnerability in the exportXFAData method which exposes a JavaScript interface that allows writing arbitrary files to the filesystem. An attacker can craft a malicious PDF file that, when opened by a user, leverages this exposed method to write and execute arbitrary code in the context of the current user, achieving remote code execution.
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.
-
Check Foxit PDF Reader versionOpen Foxit PDF Reader, then go to Help > About Foxit Reader (or right-click the executable file in Program Files and select Properties > Details to view the version)Affected if The displayed version is lower than 12.1.1.15289, indicating a vulnerable version
-
Verify JavaScript execution is enabledIn Foxit PDF Reader, go to File > Preferences > JavaScript and check if JavaScript is enabledAffected if JavaScript execution is turned ON in the application settings
-
Confirm XFA support is activeThe exportXFAData method relates to XFA (XML Forms Architecture) - check if the application handles XFA forms by opening a PDF containing XFA contentAffected if XFA forms can be processed by the reader, which enables the vulnerable exportXFAData interface
-
Review plugin or add-on statusGo to Home > Plugins to see if the Foxit PDF SDK plugin is loaded, which handles the JavaScript API exposureAffected if The PDF productivity plugins are enabled and loaded
You are affected if your Foxit PDF Reader version is below 12.1.1.15289 AND JavaScript execution is enabled in the application preferences, allowing the exportXFAData method to be exploited for arbitrary file write and remote code execution.
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 version incorporating the vendor patch. Until patched, avoid opening untrusted PDF files and consider disabling JavaScript execution in the reader settings.
Upgrade to Pdf Editor 10.1.11.37866 (for v10.x), 11.2.5.53785 (for v11.x), or 12.1.1.15289 (for v12.x); Pdf Reader 12.1.1.15289
- 1. Identify the installed Foxit PDF Editor or Foxit PDF Reader version by opening the application and navigating to Help > About Foxit PDF Editor/Reader
- 2. For Pdf Editor version 10.x: Upgrade to version 10.1.11.37866 or later
- 3. For Pdf Editor version 11.x: Upgrade to version 11.2.5.53785 or later
- 4. For Pdf Editor version 12.x: Upgrade to version 12.1.1.15289 or later
- 5. For Pdf Reader: Upgrade to version 12.1.1.15289 or later
- 6. Verify the upgrade was successful by checking Help > About to confirm the installed version matches or exceeds the fixed release
- 7. Ensure JavaScript execution is disabled in PDF Reader settings if corporate policy permits, as an additional defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27363 — 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-27363 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