dbcve.org
Pdf Editor CloudApplication · Foxit

CVE-2025-66501

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 pdfonline.foxit.com within the Predefined Text feature of the Foxit eSign section. A crafted payload can be stored via the Identity “First Name” field, which is later rendered into the DOM without proper sanitization. As a result, the injected script may execute when predefined text is used or when viewing document properties.

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 XSS vulnerability in pdfonline.foxit.com allows attackers to inject malicious scripts via the Identity 'First Name' field in the Foxit eSign Predefined Text feature. The injected payload persists and executes without sanitization when users interact with predefined text or view document properties.

MitigationImplement robust input validation on the First Name field and ensure all user-supplied data is properly encoded/escaped before rendering into the HTML DOM. Apply context-aware output encoding based on where the data is inserted (HTML attributes, JavaScript, etc.).

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 usage
    Verify that your account or integration uses Foxit Pdf Editor Cloud (pdfonline.foxit.com) by checking service URLs, API endpoints, or account details.
    Affected if You actively use or access Foxit Pdf Editor Cloud as your PDF editing service.
  2. Identify eSign Predefined Text feature access
    Check if your Foxit Cloud account has the eSign Predefined Text feature enabled or accessible. This is typically found in document signing workflows, template management, or signature settings within the cloud interface.
    Affected if You have access to or use the eSign Predefined Text feature in the Foxit Cloud environment.
  3. Inspect First Name field configuration
    Navigate to the Identity or User Profile settings within the Foxit eSign module. Locate any 'First Name' field associated with predefined text, templates, or signature blocks.
    Affected if A First Name field exists in your eSign Predefined Text configuration and contains or can contain user-supplied data.
  4. Verify service version or update date
    Check your Foxit Pdf Editor Cloud account for the last update timestamp, version date, or release notes. This cloud service version is dated by implementation date rather than a traditional version number.
    Affected if The cloud service was last updated or accessed before December 1, 2025 (2025-12-01).

A user is affected if they use Foxit Pdf Editor Cloud with the eSign Predefined Text feature and have a First Name field configured, particularly if the service predates the December 2025 update.

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 on the First Name field and ensure all user-supplied data is properly encoded/escaped before rendering into the HTML DOM. Apply context-aware output encoding based on where the data is inserted (HTML attributes, JavaScript, etc.).

Recommended fix High confidence

Pdf Editor Cloud version 2025-12-01 or later

  1. Verify the current version of Pdf Editor Cloud being used by checking the admin console or contacting Foxit support
  2. Contact Foxit support or account representative to request upgrade to version 2025-12-01 or later
  3. Confirm that the Foxit eSign service has been updated to the patched version
  4. Test the Identity First Name field with a benign test payload (e.g., <script>alert('XSS')</script>) to verify the vulnerability is remediated
  5. Verify that predefined text and document properties no longer execute injected JavaScript

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

Fix this in Pdf Editor Cloud Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
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,872.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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