dbcve.org
OfbizApplication · Apache

CVE-2026-50223

HIGH · 8.8 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 24.09.07 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper Control of Generation of Code ('Code Injection') vulnerability in Apache OFBiz allows a low-privileged authenticated user with Content/DataResource editing privileges to perform template injection attacks that could lead to Remote Code Execution. This issue affects Apache OFBiz: before 24.09.07. Users are recommended to upgrade to version 24.09.07, 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 a code injection vulnerability in its Content/DataResource management components. An authenticated user with Content/DataResource editing privileges can inject malicious code through templates, achieving remote code execution. The vulnerability stems from improper control of code generation in the templating system.

MitigationUpgrade Apache OFBiz to version 24.09.07 or later to remediate this vulnerability. If immediate upgrade is not feasible, restrict or disable Content/DataResource editing privileges for low-privileged users as a temporary workaround.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Apache OFBiz installation version
    Locate the OFBiz version file (build.gradle, version.properties in the OFBiz home directory) or access the OFBiz administration interface at /admin and check the system information page
    Affected if The installed version is any release prior to 24.09.07 (e.g., 24.09.00-24.09.06, 18.12.x, earlier releases)
  2. Confirm Content/DataResource component is accessible
    Access the OFBiz web interface and navigate to the Content Manager (typically under eCommerce or portal apps), then locate the DataResource section. Verify the component is loaded by checking the ofbiz-component.xml file for the content component in the runtime/framework/content directory
    Affected if The Content/DataResource component is installed and loaded in the OFBiz instance
  3. Audit user roles with Content editing privileges
    Log into OFBiz as an administrator, then navigate to Security > Party > Party Manager or the User Management section. Review all user accounts and their assigned roles, specifically looking for roles that grant Content/DataResource create/edit permissions such as 'CONTENT_MGR' or 'DATARESOURCE_MGR'
    Affected if Any user account is assigned editing privileges (create, update) on Content or DataResource entities
  4. Inspect templates in Content/DataResource for malicious code
    In the OFBiz Content Manager interface, browse through all stored templates, Minilang scripts, and FTL (FreeMarker) templates. For each DataResource of type 'FTL' or 'SCREEN', examine the source code for suspicious patterns such as shell command execution (exec, Runtime.getRuntime()), file system operations, or encoded/obfuscated payloads
    Affected if Any template in the Content/DataResource repository contains code capable of executing system commands or performing unauthorized file operations

A user is affected if their OFBiz version is below 24.09.07 AND the Content/DataResource component is active AND at least one user account possesses editing privileges on that component, particularly in an environment where untrusted users can access those privileges.

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.07 or later
Fixed in 24.09.07
Interim mitigation

Upgrade Apache OFBiz to version 24.09.07 or later to remediate this vulnerability. If immediate upgrade is not feasible, restrict or disable Content/DataResource editing privileges for low-privileged users as a temporary workaround.

Recommended fix High confidence

24.09.07

  1. 1. Back up your existing Apache OFBiz installation directory and database before proceeding with the upgrade.
  2. 2. Download Apache OFBiz version 24.09.07 from the official Apache distribution repository (https://ofbiz.apache.org/download.html).
  3. 3. Stop the currently running OFBiz service to prevent data corruption during upgrade.
  4. 4. Replace the existing OFBiz installation files with the new version 24.09.07 files, preserving any custom configurations, scripts, or data files as needed.
  5. 5. Review and update any custom configuration files, plugins, or extensions to ensure compatibility with version 24.09.07.
  6. 6. Start the OFBiz service and verify it initializes without errors.
  7. 7. Log in and verify that the Content/DataResource functionality works correctly and that the code injection vulnerability is no longer present.

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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