dbcve.org
Pdf EditorApplication · Foxit

CVE-2022-37378

HIGH · 7.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 10.1.9 / 11.2.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Editor 11.1.1.53537. 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 optimization of JavaScript functions. 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-16867.

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 confidence

This is a use-after-free type vulnerability in Foxit PDF Editor 11.1.1.53537 where JavaScript function optimization fails to validate object existence before performing operations on it. An attacker can exploit this by crafting a malicious PDF file that, when opened, triggers the vulnerability and allows arbitrary code execution in the context of the current process.

MitigationApply the vendor patch from Foxit to update to a fixed version. Avoid opening untrusted PDF files from unknown sources until the patch is applied.

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
Pdf EditorApplication
Affected:< 10.1.9>= 11.0.0, < 11.2.3= 12.0.0.12394
Pdf ReaderApplication
Affected:< 12.0.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Foxit product
    Open Foxit PDF Editor or Reader, then navigate to Help > About to view the exact version number displayed in the dialog window
    Affected if The version displayed is < 10.1.9, or >= 11.0.0 and < 11.2.3, or equals 12.0.0.12394 for Editor; or < 12.0.1 for Reader
  2. Check Windows installed programs list
    Open Windows Control Panel > Programs and Features (or Settings > Apps > Installed apps on Windows 11), locate Foxit PDF Editor or Foxit PDF Reader in the list, and note the version column
    Affected if The listed version matches the affected version ranges from step 1
  3. Verify JavaScript is enabled in the application
    In Foxit, go to File > Preferences > JavaScript and confirm the 'Enable Adobe JavaScript' checkbox is checked
    Affected if JavaScript is enabled - this is required for the vulnerability to be triggered when opening a malicious PDF

You are affected if your installed Foxit PDF Editor version is before 10.1.9, between 11.0.0 and 11.2.2 inclusive, or exactly 12.0.0.12394; or if Foxit PDF Reader is before version 12.0.1, and JavaScript is enabled in the application settings.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.1.9 / 11.2.3 / 12.0.1 or later
Fixed in 10.1.911.2.312.0.1
Interim mitigation

Apply the vendor patch from Foxit to update to a fixed version. Avoid opening untrusted PDF files from unknown sources until the patch is applied.

Recommended fix High confidence

Pdf Editor: 10.1.9, 11.2.3, or latest version; Pdf Reader: 12.0.1 or latest version

  1. For Pdf Editor: Upgrade to version 10.1.9 or later if on version < 10.1.9
  2. For Pdf Editor: Upgrade to version 11.2.3 or later if on version 11.0.0 - 11.2.2
  3. For Pdf Editor: Upgrade to a version newer than 12.0.0.12394 if currently on build 12.0.0.12394
  4. For Pdf Reader: Upgrade to version 12.0.1 or later if on version < 12.0.1
  5. Verify the installed version after upgrade to confirm remediation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-37378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-37378 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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