dbcve.org
OfbizApplication · Apache

CVE-2026-31906

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 24.09.06. Users are recommended to upgrade to version 24.09.06, which fixes the issue.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in Apache OFBiz's web page generation component. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets stored and rendered in web pages, potentially compromising other users who view the affected content.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later, which includes proper input validation/sanitization to prevent XSS attacks.

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:< 24.09.06

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

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

  1. Determine installed Apache OFBiz version
    Locate the OFBiz installation and check for version files such as VERSION, build.gradle, or gradle.properties in the root directory; alternatively check framework/base/src/main/java/org/apache/ofbiz/base/util/UtilProperties.java for version constants
    Affected if The installed version is Apache OFBiz below 24.09.06
  2. Confirm web interface is accessible
    Check if OFBiz web ports (typically 8080 for HTTP, 8443 for HTTPS) are listening and the /admin, /webtools, or /ecommerce endpoints are reachable
    Affected if The OFBiz web application is network-accessible to users or attackers
  3. Identify user input fields in web pages
    Review custom screen definitions (XML files in applications/*/widget/ or hot-deploy/*/widget directories) that render user-provided content without explicit sanitization
    Affected if Custom forms, fields, or data entry points that accept user input and display it back in web pages are configured
  4. Audit stored data for XSS indicators
    Query the database or review application logs for suspicious patterns in stored content: <script>, javascript:, onerror=, onload=, or other HTML/JavaScript event handlers
    Affected if Malicious script payloads are found in database fields or application logs indicating exploitation attempts

You are affected if running Apache OFBiz version below 24.09.06 with accessible web interfaces that accept user input which gets rendered in web pages without sanitization

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.

dbcve · scoped
Upgrade available Upgrade to 24.09.06 or later
Fixed in 24.09.06
Interim mitigation

Upgrade Apache OFBiz to version 24.09.06 or later, which includes proper input validation/sanitization to prevent XSS attacks.

Recommended fix High confidence

24.09.06

  1. Create a complete backup of your current Apache OFBiz installation including database, configuration files, and any custom code or data
  2. Download Apache OFBiz version 24.09.06 from the official Apache OFBiz repository (https://ofbiz.apache.org/download.html)
  3. Review the official upgrade documentation at https://ofbiz.apache.org/upgrade.html for your specific version upgrade path
  4. Stop the running OFBiz services
  5. Deploy the new version following the standard upgrade procedure
  6. Start the upgraded OFBiz services
  7. Verify the installation by logging into the administration interface and testing key functionality
  8. Confirm the OFBiz version displays as 24.09.06
Caveat Review release notes for 24.09.06 for any breaking changes; major version upgrades may require configuration or code adjustments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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