CVE-2026-1591
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 · uneditedFoxit PDF Editor Cloud (pdfonline) contains a stored cross-site scripting vulnerability in the file upload feature. A malicious username is embedded into the upload file list without proper escaping, allowing arbitrary JavaScript execution when the list is displayed. This issue affects pdfonline.foxit.com: before 2026‑02‑03.
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 confidenceFoxit PDF Editor Cloud (pdfonline) contains a stored cross-site scripting vulnerability in the file upload feature where malicious usernames are embedded into the upload file list without proper escaping, allowing arbitrary JavaScript execution when the list is displayed.
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< 2026-02-03CVSS 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.
-
Identify Foxit PDF Editor Cloud usageConfirm your organization uses Foxit PDF Editor Cloud (pdfonline) for PDF editing or collaboration services. Check your installed software, cloud subscription, or integrated services.Affected if Your environment uses Foxit PDF Editor Cloud as a service.
-
Check the deployed version dateLocate the version or build number of your Foxit PDF Editor Cloud installation. For cloud services, check the service provider's version information or patch notes. Compare the last update date to 2026-02-03.Affected if The deployed version predates 2026-02-03 or the patch released on that date is not applied.
-
Verify file upload feature accessibilityConfirm the file upload feature is enabled and accessible to users in your Foxit PDF Editor Cloud environment. Check if users can upload documents and see other users' names in the upload list.Affected if The file upload feature is enabled and users can view the upload file list showing usernames.
-
Test for XSS in username displayCreate or use a test account with a malicious username containing script tags (e.g., <script>alert(1)</script>), upload a file, and view the file list to see if the username is rendered without escaping.Affected if The username is displayed in plain text without HTML encoding, allowing script execution.
You are affected if your Foxit PDF Editor Cloud version is earlier than the 2026-02-03 patch and the file upload feature is accessible, allowing stored XSS via unsanitized usernames in the upload list.
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 · scoped2026-02-03
Ensure the patch released before 2026-02-03 is applied. Additionally, implement proper output encoding/escaping for all user-supplied content when rendering usernames in the file upload list to prevent XSS.
Pdf Editor Cloud version dated 2026-02-03 or later
- Confirm current version of Pdf Editor Cloud in use by checking the pdfonline.foxit.com interface or contacting Foxit support
- If version is dated before 2026-02-03, wait for Foxit to deploy the fix or contact support to request access to the patched version
- After the fix date (2026-02-03), verify the XSS vulnerability is remediated by testing file upload with a safe test payload in the username field
- Confirm with Foxit technical support that the patch has been applied to your tenant
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1591 — 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-2026-1591 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