dbcve.org
OfbizApplication · Apache

CVE-2026-31379

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'), Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Improper Control of Generation of Code ('Code Injection') 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

Apache OFBiz before version 24.09.06 contains three distinct vulnerabilities: Cross-site Scripting (XSS) allowing injection of malicious scripts into web pages, Path Traversal permitting unauthorized access to restricted directories, and Code Injection enabling execution of attacker-controlled code. These vulnerabilities could allow authenticated or unauthenticated attackers to compromise the OFBiz application, steal session data, or execute arbitrary commands on the underlying system.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to address all three vulnerabilities. Prior to upgrade, review custom configurations and test thoroughly in a staging environment to ensure compatibility with existing workflows.

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. Confirm Apache OFBiz installation
    Look for OFBiz directories (typically 'ofbiz' or 'apache-ofbiz' in installation paths), check for 'ofbiz.jar' or 'ofbiz.war' files, or query running processes for 'ofbiz' named Java processes
    Affected if Apache OFBiz is installed on the system
  2. Identify installed OFBiz version
    Check the version file in the OFBiz installation directory (often 'VERSION' or 'build.gradle' file), or inspect the startup logs for the version number displayed during OFBiz startup
    Affected if The version is less than 24.09.06 (for example, 24.09.05, older releases, or nightly builds)
  3. Verify OFBiz web interface is accessible
    Attempt to access the OFBiz web interface via HTTP/HTTPS on common ports (typically 8080, 8443) at paths like '/ofbiz/','/webtools/','/catalog/','/ordermgr/'
    Affected if The OFBiz web application is exposed and reachable (required for XSS, path traversal, and code injection to be exploitable)
  4. Check authentication requirements for exposed endpoints
    Review which OFBiz applications are accessible without authentication by attempting to access web pages without logging in
    Affected if Unauthenticated access to OFBiz web endpoints is possible (some attacks may work without authentication, others require valid credentials)

The environment is affected if Apache OFBiz is installed with a version lower than 24.09.06 and has its web interface accessible, regardless of authentication status.

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 to address all three vulnerabilities. Prior to upgrade, review custom configurations and test thoroughly in a staging environment to ensure compatibility with existing workflows.

Recommended fix High confidence

24.09.06

  1. 1. Back up your current Apache OFBiz installation, including all configuration files and the database
  2. 2. Download Apache OFBiz version 24.09.06 from the official Apache download mirrors or the OFBiz website
  3. 3. Stop all running OFBiz services and application servers
  4. 4. Replace the existing OFBiz installation with the new 24.09.06 version, preserving custom configurations and data
  5. 5. Review and apply any necessary migration steps documented in the 24.09.06 release notes
  6. 6. Start the OFBiz services and verify the application functions correctly
  7. 7. Test that the previously vulnerable paths are now properly sanitized
Caveat Review 24.09.06 release notes for any deprecations or configuration changes that may affect custom components

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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