OfbizApplication · Apache
CVE-2019-10073
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 · uneditedThe "Blog", "Forum", "Contact Us" screens of the template "ecommerce" application bundled in Apache OFBiz are weak to Stored XSS attacks. Mitigation: Upgrade to 16.11.06 or manually apply the following commits on branch 16.11: 1858438, 1858543, 1860595 and 1860616
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 confidenceStored XSS vulnerability in Apache OFBiz's ecommerce template affecting the Blog, Forum, and Contact Us screens. Attackers can inject malicious JavaScript that executes when users view these pages, allowing session hijacking or data theft.
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.05CVSS 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 installed Apache OFBiz versionLocate the OFBiz version file or build metadata in the installation directory (commonly found in build.gradle, version.properties, or the WAR file manifest) and note the exact version numberAffected if The installed version falls within >= 16.11.01 and <= 16.11.05
-
Confirm ecommerce application is enabledVerify that the OFBiz ecommerce component is deployed and accessible in your environment - check the application list or the presence of ecommerce-related configuration and web resourcesAffected if The ecommerce application is running and accessible to users
-
Check if Blog screen is in useInspect whether the Blog functionality within the ecommerce portal is active - this includes checking if blog-related content, templates, or screens are accessible to end usersAffected if The Blog screen is accessible and used in your OFBiz ecommerce instance
-
Check if Forum screen is in useInspect whether the Forum functionality within the ecommerce portal is active - verify if forum-related screens, posts, or user discussion features are accessibleAffected if The Forum screen is accessible and used in your OFBiz ecommerce instance
-
Check if Contact Us screen is in useInspect whether the Contact Us functionality within the ecommerce portal is active - verify if the contact form or contact-related templates are deployed and accessible to usersAffected if The Contact Us screen is accessible and used in your OFBiz ecommerce instance
Your environment is affected if you are running Apache OFBiz version 16.11.01 through 16.11.05 with the ecommerce application enabled and any of the Blog, Forum, or Contact Us screens accessible to users.
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 16.11.06 or manually apply commits 1858438, 1858543, 1860595, and 1860616 to branch 16.11 to remediate the XSS vulnerability.
Fix this in Ofbiz
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10073 — 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-2019-10073 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