CVE-2025-66502
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 · uneditedA stored cross-site scripting (XSS) vulnerability exists in pdfonline.foxit.com within the Page Templates feature. A crafted payload can be stored as the template name, which is later rendered into the DOM without proper sanitization. As a result, the injected script executes each time the affected PDF is loaded.
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 confidenceA stored XSS vulnerability exists in pdfonline.foxit.com's Page Templates feature where malicious JavaScript can be embedded in a template name. When the affected PDF is loaded, the unsanitized template name is rendered into the DOM, causing the injected script to execute persistently.
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< 2025-12-01CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Foxit Pdf Editor Cloud usageLog into your pdfonline.foxit.com account and verify you are using the Foxit Pdf Editor Cloud service. Check the account dashboard or subscription details to confirm the service in use.Affected if You are actively using Foxit Pdf Editor Cloud as your PDF editing platform
-
Check the service versionAccess the version information for your Foxit Pdf Editor Cloud instance. This may be found in the account settings, about section, or the service dashboard. Compare the version date to the cutoff date of 2025-12-01.Affected if The version or build date is earlier than December 1, 2025 (version < 2025-12-01)
-
Verify Page Templates feature accessNavigate to the Page Templates feature within the pdfonline.foxit.com interface. Look for the template management section where you can create, edit, or view PDF page templates.Affected if The Page Templates feature is accessible and has been used to create or import templates
-
Inspect template names for script contentIn the Page Templates section, review all saved template names. Look for any templates with unusual characters, HTML tags, or JavaScript-like syntax in their names (e.g., <script>, javascript:, onerror=, onload=, alert(, etc.).Affected if Any template name contains HTML tags, JavaScript event handlers, or script-related syntax that was not intentionally encoded by the user
You are affected if you use Foxit Pdf Editor Cloud with a version predating December 1, 2025 and have used the Page Templates feature where template names may contain unsanitized user-supplied content.
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 · scoped2025-12-01
Implement input validation and output encoding on all template names before rendering them in the DOM. Use context-aware escaping (HTML entity encoding for HTML content) to prevent script execution.
Pdf Editor Cloud 2025-12-01 or later
- 1. Identify all users or integrations accessing pdfonline.foxit.com
- 2. Verify the currently deployed Pdf Editor Cloud version is earlier than 2025-12-01
- 3. Upgrade Pdf Editor Cloud to version 2025-12-01 or later through the vendor's update mechanism
- 4. Confirm the upgrade was successful by checking the version information in the admin console or about section
- 5. Validate the fix by creating a test template with a benign payload (e.g., <script>console.log('test')</script>) in the template name field and verifying it is properly encoded/escaped when rendered in the DOM
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-2025-66502 — 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-2025-66502 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