dbcve.org
OfbizApplication · Apache

CVE-2026-31910

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 or later.
See remediation →
84/100
Remediation priority · High
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
Server-Side Request Forgery (SSRF) 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

This is a Server-Side Request Forgery (SSRF) vulnerability in Apache OFBiz, an open-source enterprise resource planning platform. The vulnerability allows attackers to make the OFBiz server perform unintended requests to internal or external resources, potentially exposing internal services, cloud metadata endpoints, or bypassing network segmentation.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict outbound network access from the OFBiz server and disable unnecessary external request capabilities.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 installed Apache OFBiz version
    Locate the version file in the OFBiz installation directory - typically in a gradle.properties file, or access the /webtools/control/about page if webtools is enabled. Run: grep -r 'version' or look for version.info in the root directory.
    Affected if The installed version is anything less than 24.09.06 (e.g., 24.09.05, 18.12.x, older releases)
  2. Confirm OFBiz web components are accessible
    Verify the OFBiz web application is running and accessible. Check if the webtools or similar controller endpoints respond to HTTP requests.
    Affected if The OFBiz web interface is exposed and responds to requests on configured ports (typically 8443 for HTTPS or 8080 for HTTP)
  3. Check for external request handling functionality
    Review the OFBiz controller XML files (controller.xml) in the webapp directories for external request handlers or URL-fetching components. These are typically in framework/webapp/webtools/widget/ControllerEvents.xml or similar paths under each webapp.
    Affected if The controller contains event handlers or services that process incoming URLs or make outbound HTTP requests based on user input
  4. Verify network accessibility to internal services
    Determine if the OFBiz server can reach internal network resources, cloud metadata endpoints (169.254.169.254), or internal services by reviewing firewall rules and network configuration.
    Affected if The OFBiz server has outbound network access to internal IPs, localhost, or cloud metadata services without strict filtering

A user is affected if their installed Apache OFBiz version is below 24.09.06 AND the web interface is accessible AND external request handling features are in use, enabling potential SSRF attacks.

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. If immediate upgrade is not possible, restrict outbound network access from the OFBiz server and disable unnecessary external request capabilities.

Recommended fix High confidence

24.09.06

  1. Backup your current Apache OFBiz installation and database before proceeding with the upgrade
  2. Stop the running OFBiz service
  3. Download Apache OFBiz version 24.09.06 from the official Apache download repository (https://ofbiz.apache.org/download.html)
  4. Extract the new version to a temporary location
  5. Replace the existing OFBiz installation directory with the new version, or perform a fresh installation and migrate configurations
  6. Copy custom configurations, plugins, and data from the backup to the new installation
  7. Start the OFBiz service and verify it initializes correctly
  8. Test that the application functions normally after the upgrade
Caveat Review the release notes for 24.09.06 to check for any configuration or API 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-31910 — 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-31910 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