dbcve.org
OfbizApplication · Apache

CVE-2016-6800

MEDIUM · 6.1 CVSS v3.0 Published 2017-08-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The default configuration of the Apache OFBiz framework offers a blog functionality. Different users are able to operate blogs which are related to specific parties. In the form field for the creation of new blog articles the user input of the summary field as well as the article field is not properly sanitized. It is possible to inject arbitrary JavaScript code in these form fields. This code gets executed from the browser of every user who is visiting this article. Mitigation: Upgrade to Apache OFBiz 16.11.01.

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 confidence

Apache OFBiz's default blog functionality contains a stored XSS vulnerability where the summary and article form fields do not properly sanitize user input, allowing authenticated users to inject arbitrary JavaScript that executes in the browsers of any user viewing the affected blog articles.

MitigationUpgrade Apache OFBiz to version 16.11.01 or later to remediate the input sanitization gap in the blog module.

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
OfbizApplication
Affected:= 11.04= 11.04.01= 11.04.02= 11.04.03= 11.04.04= 11.04.05= 11.04.06= 12.04= 12.04.01= 12.04.02= 12.04.03= 12.04.04

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache OFBiz installation and version
    Check the OFBiz version by looking at the build.gradle file, framework/base/build.gradle, or the ofbiz.jar MANIFEST.MF file in the installation directory. Alternatively, access the OFBiz administrative interface and check the version information.
    Affected if The installed version matches one of: 11.04, 11.04.01, 11.04.02, 11.04.03, 11.04.04, 11.04.05, 11.04.06, 12.04, 12.04.01, 12.04.02, 12.04.03, or 12.04.04
  2. Confirm blog functionality is in use
    Navigate to the blog application within OFBiz (typically at /bizapp/control/main?blog=main or check for BlogManager in the available applications). Inspect the database for blog-related tables such as BlogContent, BlogPost, or similar naming patterns.
    Affected if The blog functionality is enabled or deployed in the OFBiz instance
  3. Identify stored blog content for review
    Query the database for records in blog content tables, specifically examining fields named 'summary', 'article', 'content', or 'body within BlogContent or related tables. Use a database client connected to the OFBiz underlying database.
    Affected if Blog entries exist in the database with unsanitized HTML or script tags in summary or article fields
  4. Check for XSS patterns in blog data
    Search the blog content tables for common XSS vectors such as <script>, javascript:, onerror=, onload=, <img src=x, or other HTML/script tags that could indicate injected code.
    Affected if Any blog records contain script tags or event handler attributes that were not intentionally authored as plain text

You are affected if you are running any of the listed OFBiz versions (11.04 through 12.04.04) and have the blog functionality enabled with stored content containing unsanitized script tags or HTML in summary or article fields.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache OFBiz to version 16.11.01 or later to remediate the input sanitization gap in the blog module.

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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 locally
dbcve dependency scanner

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