CVE-2016-6847
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 · uneditedAn issue was discovered in Open-Xchange OX App Suite before 7.8.2-rev8. SVG files can be used as mp3 album covers. In case their XML structure contains script code, that code may get executed when calling the related cover URL. Malicious script code can be executed within a user's context. This can lead to session hijacking or triggering unwanted actions via the web interface (sending mail, deleting data etc.).
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 confidenceOpen-Xchange OX App Suite before 7.8.2-rev8 allows SVG files with embedded script code to be used as MP3 album covers. When the cover URL is accessed, the JavaScript within the SVG executes in the user's browser context, enabling session hijacking and unauthorized actions.
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.8.2CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Determine OX App Suite versionLog into the admin dashboard and navigate to the 'Packages' or 'Software Version' section, or run the command: rpm -q ox-appsuite or dpkg -l ox-appsuiteAffected if The installed version is 7.8.2-rev8 or lower (any version <= 7.8.2)
-
Verify media gallery or photo feature is activeCheck the user-facing interface for the 'My Photos' or 'Media Gallery' module access, or query the configuration database for enabled packages containing 'media' or 'photo'Affected if Users have access to upload or manage album artwork/photos in the web interface
-
Confirm custom image uploads are permittedReview the configuration file /opt/open-xchange/etc/settings/media.properties (or similar path) for uploadAllowCustomImages=true, or test by attempting to upload an SVG as profile photo or contact imageAffected if The system allows users to upload custom images as album art or contact photos
-
Inspect for SVG content-type filteringExamine the web server configuration or OX proxy settings for SVG MIME type handling, or test uploading an SVG file as album art and check if it is served with correct Content-Type headerAffected if SVG files are accepted and served without sanitization or content-type restrictions
You are affected if running OX App Suite version 7.8.2 or lower AND the media/photo feature allowing custom album art uploads is enabled, allowing SVG files to be uploaded and served as image 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.
From vendor dataSanitize or reject SVG files containing script content when used as album art, or implement Content Security Policy headers to prevent script execution in SVG resources.
- 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-2016-6847 — 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-2016-6847 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