Is there a public exploit for CVE-2024-36104?

Yes. Proof-of-concept code for CVE-2024-36104 has been published publicly.

Is there a proof of concept for CVE-2024-36104?

Yes — 2 proof-of-concept entries are linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2024-36104?

CVE-2024-36104 scores CVSS 9.1 (v3.1), rated critical. EPSS puts the chance of exploitation in the next 30 days at 87.88%.

What does CVE-2024-36104 affect?

CVE-2024-36104 affects Apache Software Foundation Apache OFBiz.

9.1 Critical

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OFBiz.

CVE-2024-36104

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 18.12.14. Users are recommended to upgrade to version 18.12.14, which fixes the issue.

Proof-of-concept code is published

Public PoC · Nuclei template

NucleiApache OFBiz - Directory Traversal & Remote Code Execution
Public PoCGroppoxx/CVE-2024-36104-PoC4 stars
Public PoCggfzx/CVE-2024-361042 stars

A Nuclei detection template exists for this, which means it is scanned for at internet scale rather than looked for deliberately.

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 9.1 (v3.1)
Severity: Critical
EPSS: 87.88% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Public PoC, Nuclei template
Published: 4 June 2024
Last updated: 3 November 2026
Affected: Apache Software Foundation · Apache OFBiz
Assigner: apache

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

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 5 + 1? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2024-36104