VulnerabilityPublished 8 May 2024Updated 21 Oct 2025

CVE-2024-32113: Apache OFBiz · Path Traversal

Affects Apache OFBizSource CVE Database V5

Exploited in the wild · KEV due 28 Aug 2024 · public exploit available (Metasploit, Exploit-DB) · 99% EPSS : upgrade to 18.12.13 now.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 28 Aug 2024 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
EPSS: 99.9% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.12.13

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 8 May 2024
Detectable: evidence found.
nuclei template: Apache OFBiz Directory Traversal - Remote Code Execution
Weaponised: evidence found.
1 Metasploit module · 1 Exploit-DB entry, 11 days after disclosure
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 91 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by Apache Software Foundation
11 Apr 202406:42 UTC, 27 days before disclosure
CVE published
on cve.org
8 May 202414:50 UTC, t = 0
First Exploit-DB entry (opens in a new tab)
Apache OFBiz 18.12.12 - Directory Traversal
19 May 2024, 11 days after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed
7 Aug 2024, 91 days after disclosure
KEV remediation due
US federal deadline
28 Aug 2024, 112 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.apache.ofbiz/ofbiz to 18.12.13.

Affected software

Product	Affected	Fixed in
Mavenorg.apache.ofbiz/ofbiz`pkg:maven/org.apache.ofbiz/ofbiz`Other threats	Affected <18.12.13	Fixed in 18.12.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

Impact

The impact of CVE-2024-32113 on organizations worldwide is significant. Successful exploitation can lead to unauthorized disclosure of sensitive business data, including configuration files, credentials, or proprietary information, severely compromising confidentiality. Additionally, attackers can alter files, potentially injecting malicious code or corrupting data, thus impacting data integrity. Since the vulnerability does not affect availability directly, denial-of-service is less likely, but the overall trustworthiness and security posture of affected systems are undermined. Enterprises relying on Apache OFBiz for critical business functions such as supply chain management, order processing, and customer data management face increased risk of data breaches and operational disruption. The lack of authentication requirement broadens the attack surface, enabling external threat actors to target vulnerable installations without insider access. This can facilitate further lateral movement or persistent footholds within organizational networks. The vulnerability also poses compliance risks, especially for organizations subject to data protection regulations, potentially resulting in legal and financial penalties.

Mitigation

To mitigate CVE-2024-32113, organizations should immediately upgrade Apache OFBiz to version 18.12.13 or later, where the vulnerability is patched. Beyond patching, it is critical to implement strict input validation and sanitization on all file path parameters to prevent directory traversal attempts. Deploy web application firewalls (WAFs) with rules designed to detect and block path traversal patterns such as '../' sequences. Conduct thorough code reviews and security testing focused on file handling functions within custom OFBiz extensions or integrations. Limit the privileges of the OFBiz application user account to the minimum necessary, restricting file system access to only required directories. Monitor logs for suspicious access patterns indicative of traversal attempts. Network segmentation can reduce exposure by isolating OFBiz servers from untrusted networks. Finally, maintain an incident response plan to quickly address any exploitation attempts and regularly audit deployed versions to ensure timely patch application.

Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:09 UTC

Public exploits and detection1 Metasploit module, 1 Exploit-DB entry, a Nuclei detection template

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats