CVE-2022-37390
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader 11.2.2.53575. 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 AcroForms. 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-17551.
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 confidenceA use-after-free or null pointer dereference vulnerability in Foxit PDF Reader 11.2.2.53575 allows remote code execution via malicious PDF files containing specially crafted AcroForms. The vulnerability stems from the application failing to validate object existence before performing operations on them, enabling an attacker to execute arbitrary code in the context of the current user process.
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.9>= 11.0.0, < 11.2.3= 12.0.0.12394< 12.0.1CVSS 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.1/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.
-
Determine Foxit PDF Reader versionOpen Foxit PDF Reader, then go to Help > About Foxit Reader. Alternatively, right-click the FoxitReader.exe file, select Properties, and view the Version tab.Affected if Version is below 12.0.1 (for Reader) or below 10.1.9, between 11.0.0-11.2.2, or equals 12.0.0.12394 (for Editor)
-
Determine Foxit PDF Editor versionOpen Foxit PDF Editor, then go to Help > About Foxit PDF Editor. Alternatively, navigate to the installation directory (typically C:\Program Files\Foxit Software\Foxit PDF Editor), right-click the PDFEditor.exe file, select Properties, and view the Version tab.Affected if Version is below 10.1.9, between 11.0.0-11.2.2, or equals 12.0.0.12394 (for Editor)
-
Verify AcroForm functionality is enabledIn Foxit Reader or Editor, go to File > Preferences > Forms. Check if the option to 'Enable Adobe Acrobat JavaScript' or form-related features is checked. This can also be verified in the Windows Registry under HKLM\SOFTWARE\Foxit\Reader\Preferences or HKCU\SOFTWARE\Foxit\Reader\Preferences if accessible.Affected if AcroForm features are enabled and the application processes PDF forms, placing the environment at risk if a malicious PDF is opened
Your environment is affected if Foxit PDF Reader is below version 12.0.1 or Foxit PDF Editor is below 10.1.9, between 11.0.0-11.2.2, or exactly version 12.0.0.12394, and AcroForm functionality is enabled.
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.911.2.312.0.1
Update Foxit PDF Reader to the latest version that includes the security patch. Until patched, instruct users not to open untrusted PDF files and consider disabling AcroForm functionality if feasible.
Pdf Reader: 12.0.1 or later; Pdf Editor: 10.1.9, 11.2.3, or later (avoid 12.0.0.12394)
- 1. Open Foxit PDF Reader or PDF Editor application
- 2. Navigate to Help > Check for Updates or About Foxit PDF [Reader/Editor]
- 3. Download and install the latest version from the official Foxit website (www.foxit.com)
- 4. For Pdf Reader: upgrade to version 12.0.1 or later
- 5. For Pdf Editor: upgrade to version 10.1.9 or later (for 10.x users); upgrade to version 11.2.3 or later (for 11.x users); for 12.x users, upgrade to any version other than 12.0.0.12394
- 6. Restart the application after updating
- 7. Verify the installed version matches a fixed release by checking Help > About Foxit PDF
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-37390 — 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-2022-37390 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