dbcve.org
OfbizApplication · Apache

CVE-2026-31380

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 Special Elements used in an Expression Language Statement ('Expression Language 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

Expression Language Injection vulnerability in Apache OFBiz allows attackers to potentially execute arbitrary code or access sensitive data by injecting malicious expressions through user-supplied input that is not properly sanitized before being evaluated by the expression language interpreter.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to remediate this vulnerability.

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installed Apache OFBiz version
    Locate the version file (typically at 'framework/base/build.gradle' or check the release notes file in the root directory), or run: grep -r 'version' build.gradle | head -5
    Affected if The version shown is earlier than 24.09.06 (e.g., 24.09.05, 24.09.04, 18.12.x, etc.)
  2. Check framework/base/build.gradle for version
    Open the file framework/base/build.gradle and look for the 'version' property near the top of the file
    Affected if The version line reads something like 'version = "24.09.05"' or lower
  3. Verify startup logs for version output
    Review recent OFBiz startup logs (often in logs/console.log or logs/ofbiz.log) for a line containing 'Apache OFBiz' and a version number
    Affected if The logged version is less than 24.09.06
  4. Inspect web controller configurations for user input handling
    Examine controller.xml files in the webapp directories (especially webtools, ecommerce, or custom applications) for any 'request' or 'field' parameters passed to service or entity operations without proper input validation
    Affected if Custom or unmodified controllers accept user parameters that flow directly into service calls or entity queries without sanitization

You are affected if your installed Apache OFBiz version is any release earlier than 24.09.06 and you have web endpoints that pass unsanitized user input to expression language evaluation contexts.

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 remediate this vulnerability.

Recommended fix High confidence

24.09.06

  1. 1. Backup your current Apache OFBiz installation including database and configuration files.
  2. 2. Download Apache OFBiz version 24.09.06 from the official Apache repository (https://ofbiz.apache.org/download.html).
  3. 3. Stop the currently running OFBiz services.
  4. 4. Replace the existing OFBiz installation files with the new version 24.09.06 files.
  5. 5. Migrate any custom configurations, plugins, and data from the old version to the new installation.
  6. 6. Review and apply any necessary changes to configuration files based on the release notes for 24.09.06.
  7. 7. Start the OFBiz services and verify the application is running correctly.
  8. 8. Test critical functionalities to ensure the upgrade did not break existing features.
Caveat Review the 24.09.06 release notes for any breaking changes or deprecations before upgrading

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-31380 — 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-31380 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