dbcve.org
OfbizApplication · Apache

CVE-2026-31387

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
See remediation →
62/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 Authentication 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 · moderate confidence

Apache OFBiz versions prior to 24.09.06 contain an improper authentication vulnerability that allows attackers to potentially bypass authentication mechanisms and gain unauthorized access to the system. The medium severity (CVSS 5.3) indicates the attack can be carried out with low complexity, requiring no privileges or user interaction.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to resolve the improper authentication vulnerability. This is a direct version upgrade rather than a configuration change.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Locate the Apache OFBiz installation
    Identify the directory where Apache OFBiz is installed. Check common locations such as /opt/ofbiz, /usr/local/ofbiz, or a custom installation path. Look for the main OFBiz directory containing subfolders like framework, applications, and specialpurpose.
    Affected if OFBiz is not installed in the searched locations.
  2. Find the version file or build artifact
    Within the OFBiz installation directory, locate the file that contains version information. This may be a build.gradle, build.xml, gradle.properties, or a version.txt file in the root of the OFBiz installation. Open this file to read the declared version number.
    Affected if No version file is found within the OFBiz installation directory.
  3. Extract the installed version number
    Read the version number from the identified version file. Common keys to look for include 'version', 'ofbizVersion', or a version number directly in the filename such as 'OFBiz-24.09.x'. Note the full version string exactly as it appears.
    Affected if The version file exists but does not contain a readable version number.
  4. Compare version against the affected range
    Compare the extracted version to 24.09.06. The vulnerability affects all versions prior to 24.09.06. Determine if your version number is lower than 24.09.06, or if the version is unspecified and the installation predates this release.
    Affected if The installed version is less than 24.09.06, indicating the improper authentication bypass vulnerability is present.

If Apache OFBiz is installed with a version lower than 24.09.06, the environment is affected by CVE-2026-31387 and the authentication bypass vulnerability can be exploited.

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 resolve the improper authentication vulnerability. This is a direct version upgrade rather than a configuration change.

Recommended fix High confidence

24.09.06

  1. Download Apache OFBiz version 24.09.06 from the official Apache OFBiz releases page (https://ofbiz.apache.org/download.html)
  2. Back up all existing data, configurations, and custom configurations before proceeding
  3. Stop any running OFBiz services
  4. Replace the existing OFBiz installation with the new version 24.09.06
  5. Review and reapply any custom configurations or extensions to the new version
  6. Start the OFBiz service and verify the application functions correctly

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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