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 25 Feb 2025.
OfbizApplication · Apache

CVE-2024-45195

HIGH · 7.5 CVSS v3.1 Published 2024-09-04
Fix available
A fix is available. Upgrade to 18.12.16 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

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

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 · high confidence

A Direct Request ('Forced Browsing') vulnerability in Apache OFBiz allows attackers to directly access URLs that may not be properly protected or linked from within the application, potentially bypassing access controls and reaching sensitive functionality.

MitigationUpgrade Apache OFBiz to version 18.12.16 or later to resolve this forced browsing vulnerability.

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.16

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

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

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 installed Apache OFBiz version
    Check the OFBiz version file, build.properties, or the initial startup logs for the version number. Common locations include the root directory's gradle.properties or the war file manifest.
    Affected if The installed version is lower than 18.12.16 (e.g., 18.12.15, 18.12.14, or any version prior to 18.12.16)
  2. Verify authentication enforcement on endpoints
    Attempt to access a known protected OFBiz endpoint (such as /webapp/partymgr/control/main or /webapp/ordermgr/control/main) using a fresh browser session or curl command WITHOUT providing any login credentials.
    Affected if The protected page or dashboard loads successfully without any authentication prompt or login redirect, indicating the forced browsing vulnerability is present
  3. Check for anonymous access to sensitive functions
    Try accessing administrative or data-related endpoints directly (such as /webapp/control/ServiceList or /webapp/control/FindParty) without authentication credentials.
    Affected if Sensitive administrative interfaces or data查询 pages are accessible without authentication, confirming bypass of authorization controls
  4. Review web.xml security constraints
    Inspect the WEB-INF/web.xml file in the OFBiz web applications (located in framework/webapp/war/*/WEB-INF/) to verify that security constraints are properly defined and enforced for protected resources.
    Affected if No security constraints are defined, or constraints are missing for sensitive endpoint paths, indicating the application may be vulnerable to forced browsing

You are affected if your Apache OFBiz version is below 18.12.16 AND protected endpoints are accessible without authentication credentials, confirming the forced browsing vulnerability exists.

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.16 or later
Fixed in 18.12.16
Interim mitigation

Upgrade Apache OFBiz to version 18.12.16 or later to resolve this forced browsing vulnerability.

Recommended fix High confidence

18.12.16

  1. 1. Create a complete backup of your current Apache OFBiz installation including the database, configuration files, and data directories
  2. 2. Stop all running OFBiz services and processes
  3. 3. Download Apache OFBiz version 18.12.16 from the official Apache OFBiz distribution (https://ofbiz.apache.org/download.html)
  4. 4. Extract the new version to a clean directory
  5. 5. Migrate your custom configurations, extensions, and data from the backup to the new installation
  6. 6. Review and apply any database migration scripts provided in the release notes
  7. 7. Start the OFBiz services
  8. 8. Verify the upgrade by logging into the OFBiz administrative interface and testing core functionality
Caveat Review release notes for any configuration or API changes that may affect custom extensions or integrations

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

Fix this in Ofbiz Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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