Skip to main content
CVE-2024-38856VulnerabilityPublished Updated

CVE-2024-38856: Apache OFBiz · Incorrect Authorization

Affects Apache OFBizSource CVE Database V5

0

Exploited in the wild · KEV due 17 Sep 2024 · public exploit available (Metasploit) · 99% EPSS : upgrade to 18.12.15 now.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS
99.4% 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.15
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

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

  1. Disclosed: evidence found.

    CVE published 5 Aug 2024

  2. Weaponised: evidence found.

    1 Metasploit module

  3. Exploited in the wild: evidence found.

    Listed in CISA KEV 22 days after disclosure

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Apache Software Foundation

    , 46 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. , 22 days after disclosure

  4. KEV remediation due

    US federal deadline

    , 43 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.

What to do

Upgrade org.apache.ofbiz/ofbiz to 18.12.15.

Affected software

ProductAffectedFixed in
Mavenorg.apache.ofbiz/ofbizpkg:maven/org.apache.ofbiz/ofbizOther threatsAffected
  • <18.12.15
Fixed in
  • 18.12.15

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

Description

Incorrect Authorization vulnerability in Apache OFBiz. This issue affects Apache OFBiz: through 18.12.14. Users are recommended to upgrade to version 18.12.15, which fixes the issue. Unauthenticated endpoints could allow execution of screen rendering code of screens if some preconditions are met (such as when the screen definitions don't explicitly check user's permissions because they rely on the configuration of their endpoints).

References

Community reviews

Loading reviews…