CVE-2020-12646
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 · uneditedOX App Suite 7.10.3 and earlier allows XSS via text/x-javascript, text/rdf, or a PDF document.
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 confidenceOX App Suite 7.10.3 and earlier contains a stored XSS vulnerability where malicious scripts can be injected via text/x-javascript, text/rdf, or PDF document content types. The application improperly handles these content types, allowing injected JavaScript to execute in the context of other users viewing the content.
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<= 7.10.3CVSS 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.
-
Check the installed OX App Suite versionAccess the admin interface or run the version check command provided by OpenXchange (typically via 'oxversion' or through the UI at Settings > About). Compare the version number to 7.10.3.Affected if The installed version is 7.10.3 or lower.
-
Verify if file uploads accept vulnerable content typesUpload a test file with content type text/x-javascript, text/rdf, or application/pdf through the OX App Suite file upload functionality and confirm the upload succeeds.Affected if The application accepts and stores files with these content types without blocking them.
-
Inspect Content-Disposition headers for stored filesRetrieve a stored file (previously uploaded with text/x-javascript, text/rdf, or PDF content type) via the web interface or API, then inspect the HTTP response headers, specifically the Content-Disposition header.Affected if The Content-Disposition header is set to 'inline' or is missing for these content types instead of 'attachment'.
-
Check for existing malicious files in the systemSearch the document storage backend (database or file system where OX App Suite stores uploads) for files with content types text/x-javascript or text/rdf, or PDF files with suspicious filenames or embedded JavaScript within their content.Affected if Files with these content types exist and contain JavaScript code or suspicious content that could execute in a user's browser.
You are affected if you are running OX App Suite version 7.10.3 or earlier and your system serves files with content types text/x-javascript, text/rdf, or PDF using 'Content-Disposition: inline' (or without any Content-Disposition header), allowing stored scripts to execute in user browsers.
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.
From vendor dataImplement strict content-type validation and ensure potentially executable content types (text/x-javascript, text/rdf, PDF) are served with Content-Disposition: attachment headers rather than rendered inline, or sanitize/render such content in sandboxed contexts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12646 — 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-2020-12646 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