dbcve.org
OfbizApplication · Apache

CVE-2026-31388

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 Access Control vulnerability in Apache OFBiz in multi-tenant deployments. 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

Improper Access Control vulnerability in Apache OFBiz affecting multi-tenant deployments. In multi-tenant setups, the vulnerability likely allows tenant A to access resources or data belonging to tenant B due to insufficient authorization checks. The issue is resolved in version 24.09.06.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later. In the meantime, restrict network access to the OFBiz instance and review tenant isolation configurations in multi-tenant deployments.

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. Identify Apache OFBiz installation
    Locate the OFBiz installation directory and check for the presence of Apache OFBiz components such as the 'framework' directory, 'applications' directory, or the OFBiz startup scripts (ofbiz.jar or startofbiz.bat/sh).
    Affected if Apache OFBiz is present on the system.
  2. Determine installed OFBiz version
    Check the version by reviewing the build.gradle or gradle.properties file in the OFBiz root directory for the 'version' property, or look for a VERSION file if present.
    Affected if The installed version is less than 24.09.06.
  3. Confirm multi-tenant deployment mode
    Review the entityengine.xml file in the framework/entity/config directory and check for tenant-specific configurations. Also check the 'delegator' configuration in the OFBiz startup logs or configuration files for multi-tenant delegator definitions.
    Affected if Multi-tenant mode is enabled through tenant delegator configurations in entityengine.xml or related configuration files.
  4. Inspect tenant isolation settings
    Examine the tenant configuration in the 'tenant' directory or database tables related to tenant setup (such as TenantDataSource or Tenant records in the OFBiz database). Verify if tenant-specific security constraints are properly defined.
    Affected if Multi-tenant isolation configurations exist but may lack proper authorization enforcement for cross-tenant access.

You are affected if Apache OFBiz version is below 24.09.06 AND multi-tenant deployment mode is enabled in your environment.

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. In the meantime, restrict network access to the OFBiz instance and review tenant isolation configurations in multi-tenant deployments.

Recommended fix High confidence

24.09.06

  1. 1. Back up your existing Apache OFBiz installation and database before proceeding with the upgrade.
  2. 2. Download Apache OFBiz version 24.09.06 from the official Apache OFBiz download page (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, or data from the old installation to the new version.
  6. 6. Review and update any deprecated configurations or settings that may have changed in the new version.
  7. 7. Start the OFBiz services and verify the application is running correctly.
  8. 8. Test the multi-tenant functionality to confirm the access control vulnerability is resolved.

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