dbcve.org
OfbizApplication · Apache

CVE-2025-54466

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-15
Fix available
A fix is available. Upgrade to 24.09.02 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Improper Control of Generation of Code ('Code Injection') vulnerability leading to a possible RCE in Apache OFBiz scrum plugin. This issue affects Apache OFBiz: before 24.09.02 only when the scrum plugin is used. Even unauthenticated attackers can exploit this vulnerability. Users are recommended to upgrade to version 24.09.02, 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 code injection vulnerability in Apache OFBiz's scrum plugin allows unauthenticated attackers to inject and execute arbitrary code, leading to full remote code execution. The vulnerability stems from improper control of code generation within the scrum component.

MitigationUpgrade Apache OFBiz to version 24.09.02 or later. If the scrum plugin is not needed, consider disabling it until the upgrade can be performed.

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

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

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

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 OFBiz installation and version
    Locate the OFBiz installation directory and check the version. Common locations include the version.properties file or build.gradle in the root directory. Look for a version marker such as 'ofbiz.version' or check the release notes included with the installation.
    Affected if The installed version is earlier than 24.09.02 (e.g., 24.03.x, 18.12.x, or earlier releases).
  2. Confirm the scrum plugin is present
    Check if the scrum plugin directory exists within the OFBiz installation. The scrum component is typically found under the plugins/ or framework/ directory structure. Look for a folder named 'scrum' or similar scrum-related components.
    Affected if The scrum plugin directory exists in the OFBiz installation.
  3. Verify the OFBiz release is vulnerable
    Compare the identified OFBiz version number against the affected version range. Versions below 24.09.02 are considered affected by this CVE.
    Affected if The installed OFBiz version is any version prior to 24.09.02 and the scrum plugin is present.

A system is affected if it runs any version of Apache OFBiz prior to 24.09.02 with the scrum plugin installed and enabled.

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.02 or later
Fixed in 24.09.02
Vendor patch issues.apache.org →
Interim mitigation

Upgrade Apache OFBiz to version 24.09.02 or later. If the scrum plugin is not needed, consider disabling it until the upgrade can be performed.

Recommended fix High confidence

24.09.02

  1. 1. Back up your current Apache OFBiz installation and database before proceeding with any upgrade.
  2. 2. Download Apache OFBiz version 24.09.02 from the official Apache OFBiz download page (ofbiz.apache.org).
  3. 3. Stop the currently running OFBiz instance if it's active.
  4. 4. If you have custom configurations or data, migrate them to the new installation - review the upgrade notes in the release documentation.
  5. 5. Deploy the new version 24.09.02 and start the OFBiz services.
  6. 6. Verify that the scrum plugin is functioning correctly after the upgrade.
  7. 7. Test that the code injection vulnerability is no longer exploitable - the RCE via the scrum plugin should be patched.
Caveat Review release notes for any breaking changes between your current version and 24.09.02; test thoroughly in a staging environment before production deployment

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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