dbcve.org
OfbizApplication · Apache

CVE-2025-59118

HIGH · 7.3 CVSS v3.1 Published 2025-11-12
Fix available
A fix is available. Upgrade to 24.09.03 or later.
See remediation →
82/100
Remediation priority · High
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
Unrestricted Upload of File with Dangerous Type vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 24.09.03. Users are recommended to upgrade to version 24.09.03, 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

Apache OFBiz contains an unrestricted file upload vulnerability allowing attackers to upload files with dangerous types (e.g., executable scripts) before version 24.09.03. This could enable remote code execution if uploaded malicious files are subsequently accessed.

MitigationUpgrade Apache OFBiz to version 24.09.03 or later. If immediate upgrade is not feasible, restrict file upload functionality and implement server-side file type validation as a temporary measure.

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:< 24.09.03

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
Low
Integrity
Low
Availability
Low

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

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 Apache OFBiz version
    Locate the OFBiz installation and check the version file or build artifact. Typical locations include a version.properties file, the build.xml, or the manifest within the OFBiz jar files. Compare the installed version to 24.09.03.
    Affected if The installed version is less than 24.09.03 (e.g., 24.09.02, older releases).
  2. Verify file upload functionality is accessible
    Identify if the OFBiz web interface or API endpoints that handle file uploads are exposed and accessible. Common upload paths include /webtools/control/upload, /partymgr/control/upload, or similar /webtools/ or /partymgr/ endpoints that accept file uploads.
    Affected if File upload endpoints are accessible without additional authentication or restrictions.
  3. Check server-side file type validation configuration
    Inspect the OFBiz configuration files (such as web.xml, server.conf, or upload handler configurations) to determine whether server-side file type validation is implemented for uploaded files.
    Affected if No server-side file type validation is configured, or the validation allows executable file types (such as .jsp, .php, .sh, .exe).
  4. Identify uploaded file storage location
    Determine the directory where uploaded files are stored within the OFBiz deployment (commonly in the hot-deploy, runtime, or temporary directories). Check if these files are served directly by the application server.
    Affected if Uploaded files are stored in a web-accessible directory and can be executed or accessed directly.

You are affected if Apache OFBiz version is below 24.09.03 AND file upload functionality is accessible without restrictive server-side validation.

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 24.09.03 or later
Fixed in 24.09.03
Interim mitigation

Upgrade Apache OFBiz to version 24.09.03 or later. If immediate upgrade is not feasible, restrict file upload functionality and implement server-side file type validation as a temporary measure.

Recommended fix High confidence

24.09.03

  1. 1. Back up your current Apache OFBiz installation and database
  2. 2. Download Apache OFBiz version 24.09.03 from the official Apache OFBiz download page (ofbiz.apache.org)
  3. 3. Stop the currently running OFBiz service
  4. 4. Replace the existing OFBiz installation files with the new version 24.09.03 files
  5. 5. Migrate any custom configurations from your backup to the new installation
  6. 6. Start the OFBiz service and verify the application is running correctly
  7. 7. Test that file upload functionality works as expected after the upgrade

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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