OfbizApplication · Apache
CVE-2020-1943
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 · uneditedData sent with contentId to /control/stream is not sanitized, allowing XSS attacks in Apache OFBiz 16.11.01 to 16.11.07.
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 confidenceApache OFBiz 16.11.01 through 16.11.07 fails to sanitize user-supplied input passed via the contentId parameter to the /control/stream endpoint. This allows attackers to inject malicious JavaScript or HTML into the response, which executes in the context of victim's browser during subsequent page renders.
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
>= 16.11.01, <= 16.11.07CVSS 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.1/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.
-
Identify the installed Apache OFBiz versionLocate the version file or check the OFBiz administration interface (typically under 'System' > 'Server Information') or examine the build.gradle/framework/common/data/VersionData.xml file for the version numberAffected if The installed version is between 16.11.01 and 16.11.07 inclusive
-
Verify the /control/stream endpoint is accessibleAttempt to access the /control/stream endpoint on your OFBiz server (for example, by visiting a URL like https://yourserver:8443/stream?contentId=test)Affected if The endpoint responds and accepts the contentId parameter
-
Test for XSS vulnerability in the contentId parameterSubmit a benign XSS test payload (such as contentId=<script>alert(1)</script>) to the /control/stream endpoint and observe whether the script tags are reflected unescaped in the responseAffected if The malicious payload is rendered directly in the page output without encoding or sanitization
You are affected if your OFBiz version falls within 16.11.01 to 16.11.07 AND the /control/stream endpoint is accessible with the contentId parameter reflecting unsanitized input.
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 dataUpgrade to Apache OFBiz version 16.12.01 or later, which contains the fix for this XSS vulnerability. As an interim measure, implement input validation and output encoding for the contentId parameter on the /control/stream endpoint.
Fix this in Ofbiz
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1943 — 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-1943 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