dbcve.org
Pdf Editor CloudApplication · Foxit

CVE-2025-66520

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-19
Fix available
A fix is available. Upgrade to 2025-12-01 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A stored cross-site scripting (XSS) vulnerability exists in the Portfolio feature of the Foxit PDF Editor cloud (pdfonline.foxit.com). User-supplied SVG files are not properly sanitized or validated before being inserted into the HTML structure. As a result, embedded HTML or JavaScript within a crafted SVG may execute whenever the Portfolio file list is rendered.

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 · moderate confidence

A stored cross-site scripting vulnerability exists in the Foxit PDF Editor cloud's Portfolio feature. Attackers can upload malicious SVG files containing embedded HTML or JavaScript that execute when the Portfolio file list is rendered, due to improper sanitization of SVG file contents before insertion into the HTML structure.

MitigationImplement robust input validation and sanitization for uploaded SVG files using a dedicated SVG sanitization library (e.g., DOMPurify) to strip or escape any embedded script content before rendering.

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 Editor CloudApplication
Affected:< 2025-12-01

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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. Confirm Foxit PDF Editor Cloud is deployed
    Identify whether your organization uses Foxit PDF Editor Cloud service. Check your software inventory or service subscription documentation.
    Affected if You do not use Foxit PDF Editor Cloud, then you are not affected.
  2. Check the deployed version
    Locate the version information for your Foxit PDF Editor Cloud instance. This is typically found in the service admin panel, about page, or version release notes.
    Affected if Your version is 2025-12-01 or later, then you are not affected by this vulnerability.
  3. Verify Portfolio feature availability
    Determine whether the Portfolio feature is enabled for your Foxit PDF Editor Cloud users. Check user role permissions or feature toggle settings in the admin console.
    Affected if Portfolio feature is disabled for all users, then the attack surface does not exist.
  4. Confirm file upload capability in Portfolio
    Check if users with access to Portfolio have the ability to upload new files into portfolio collections.
    Affected if Users cannot upload files to Portfolio, then they cannot introduce malicious SVG files.
  5. Inspect existing Portfolio uploads
    Review any SVG files already present in Portfolio collections. Examine file contents for embedded script tags, event handlers, or external resource references.
    Affected if SVG files containing unescaped HTML script elements or JavaScript event handlers are present in Portfolio, then exploitation may have occurred.

You are affected if you use Foxit PDF Editor Cloud with a version before 2025-12-01, the Portfolio feature is enabled, and users can upload files to Portfolio.

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 2025-12-01 or later
Fixed in 2025-12-01
Interim mitigation

Implement robust input validation and sanitization for uploaded SVG files using a dedicated SVG sanitization library (e.g., DOMPurify) to strip or escape any embedded script content before rendering.

Recommended fix Moderate confidence

Pdf Editor Cloud version 2025-12-01 or later

  1. Verify the current version of Pdf Editor Cloud (pdfonline.foxit.com) being used
  2. Contact Foxit support to confirm the deployment of version 2025-12-01 or later which contains the fix
  3. If using an older version, request or wait for upgrade to the 2025-12-01 release or newer

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

Fix this in Pdf Editor Cloud Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66520 — 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-2025-66520 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