dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 28 Aug 2024.
OfbizApplication · Apache

CVE-2024-32113

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-08
Fix available
A fix is available. Upgrade to 18.12.13 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OFBiz.This issue affects Apache OFBiz: before 18.12.13. Users are recommended to upgrade to version 18.12.13, 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 before version 18.12.13 contains a path traversal vulnerability (CWE-22) that allows attackers to access files outside the restricted directory by manipulating pathname inputs. The improper limitation of pathname to a restricted directory enables attackers to read sensitive files or potentially write to unauthorized locations.

MitigationUpgrade Apache OFBiz to version 18.12.13 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict web server access to only trusted networks and disable unnecessary file-serving functionality.

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:< 18.12.13

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the installed Apache OFBiz version
    Locate the version file or build metadata in the OFBiz installation directory. Common locations include a version properties file, build.gradle version field, or a RELEASE_NOTES file in the root installation folder. Alternatively, access the OFBiz administration interface /webtools/control/about and locate the version display.
    Affected if The discovered version number is lower than 18.12.13 (for example, 18.12.12, 18.12.10, or earlier releases).
  2. Confirm OFBiz web interfaces are network-accessible
    Test connectivity to common OFBiz endpoints such as /webtools, /catalog, /order, /accounting, or the root URL of the OFBiz installation using a web browser or curl command.
    Affected if The OFBiz web application is reachable over the network (especially the internet) without requiring authentication, as this vulnerability is exploitable remotely without credentials.
  3. Verify file-serving endpoints are exposed
    Identify if the webtools control or any file-related controller endpoints are accessible. These typically include path parameters used for file download or display operations.
    Affected if File-related endpoints accepting path parameters are exposed without additional authentication layers beyond the OFBiz authentication.

The environment is affected if the installed OFBiz version is below 18.12.13 AND the OFBiz web application is accessible over the network, since the path traversal can be exploited remotely without authentication.

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 18.12.13 or later
Fixed in 18.12.13
Vendor patch ofbiz.apache.org →
Interim mitigation

Upgrade Apache OFBiz to version 18.12.13 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict web server access to only trusted networks and disable unnecessary file-serving functionality.

Recommended fix High confidence

18.12.13

  1. 1. Backup your current Apache OFBiz installation and database
  2. 2. Download Apache OFBiz version 18.12.13 or later from the official Apache OFBiz distribution
  3. 3. Stop the running OFBiz services
  4. 4. Replace the existing OFBiz installation files with the new version
  5. 5. Review and update any custom configurations or plugins for compatibility
  6. 6. Start the OFBiz services
  7. 7. Verify the application is functioning correctly

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

Fix this in Ofbiz Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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