CVERadar
HIGH · CVSS 3.1 7.5CISA KEV · added 2025-02-04EPSS 99.98% (p100)Threat level 82

CVE-2024-45195: Apache OFBiz Forced Browsing Vulnerability

Apache · OFBiz · NVD published 2024-09-04 · posted 2026-10-21 · last modified 2026-06-17

What it is

Direct Request ('Forced Browsing') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 18.12.16. Users are recommended to upgrade to version 18.12.16, which fixes the issue.

WeaknessCWE-425
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (source: [email protected])
CISA due date2025-02-25 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsInitial Access → Persistence → Execution → Impact

Exploitation evidence

First exploit evidence seen: 2025-02-04 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2025-02-04. Source

Public exploit code

GitHub proof-of-concept repositories below quality bar

1 public repositories from 1 accounts, first seen 2025-07-23.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

Defend the Chain

The attack chain for CVE-2024-45195 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 82/100
Defender level 1 · 0 XP
Chain links broken: 0/4

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1133 External Remote Services CTID: exploitation technique

Insufficient authorization checks in affected Apache OFBiz versions (before 18.12.16) allow an attacker running their own server to send POST requests that instruct the OFBiz server to fetch malicious files from the attacker's server. The attacker can then send another request that triggers the malicious files to run arbitrary code.

How to fix it

CISA required action

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

  • apache ofbiz: upgrade to 18.12.16 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1021 Restrict Web-Based Content (for T1133, T1059) : Restrict all traffic to and from public Tor nodes.
  • M1030 Network Segmentation (for T1133) : Deny direct remote access to internal systems through the use of network proxies, gateways, and firewalls.
  • M1042 Disable or Remove Feature or Program (for T1133, T1059) : Disable or block remotely available services that may be unnecessary.
  • M1035 Limit Access to Resource Over Network (for T1133) : Limit access to remote services through centrally managed concentrators such as VPNs and other managed remote access systems.
  • M1032 Multi-factor Authentication (for T1133) : Use strong two-factor or multi-factor authentication for remote service accounts to mitigate an adversary's ability to leverage stolen credentials, but be aware of [Multi-Factor Authentication Interception](https://attack.mitre.org/techniques/T1111) techniques for some two-factor authentication implementations.
  • M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
  • M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
  • M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.
  • M1033 Limit Software Installation (for T1059) : Prevent user installation of unrequired command and scripting interpreters.
  • M1045 Code Signing (for T1059) : Where possible, only permit execution of signed scripts.

Detection Generic guidance

  • Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
  • Persistence: Look for new files in web roots, new scheduled tasks/services, and new accounts created after the exposure window.
  • Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.
  • Impact: Monitor service availability, unexpected encryption activity and mass file changes.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources