dbcve.org
OfbizApplication · Apache

CVE-2019-10074

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-11
Fix available
A fix is available. Upgrade to after 16.11.05 or later.
See remediation →
100/100
Remediation priority · Urgent
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
An RCE is possible by entering Freemarker markup in an Apache OFBiz Form Widget textarea field when encoding has been disabled on such a field. This was the case for the Customer Request "story" input in the Order Manager application. Encoding should not be disabled without good reason and never within a field that accepts user input. Mitigation: Upgrade to 16.11.06 or manually apply the following commit on branch 16.11: r1858533

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 Remote Code Execution vulnerability via Freemarker template injection. Attackers can execute arbitrary code by submitting Freemarker markup in textarea fields where output encoding has been disabled. The Customer Request 'story' field in the Order Manager application is explicitly vulnerable.

MitigationUpgrade Apache OFBiz to version 16.11.06 or later. Alternatively, manually apply commit r1858533 to branch 16.11. Review all form widget configurations to ensure encoding is enabled for any field accepting user input.

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:>= 16.11.01, <= 16.11.05

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. Verify Apache OFBiz version
    Check the OFBiz installation by locating the ofbiz.jar or build.gradle file, or run: grep -r 'version' build.gradle 2>/dev/null | head -5. Compare the reported version against the affected range 16.11.01 to 16.11.05.
    Affected if The installed version is 16.11.01, 16.11.02, 16.11.03, 16.11.04, or 16.11.05.
  2. Confirm Order Manager application is deployed
    Check if the Order Manager component is present in the OFBiz installation under plugins or applications directory. Look for the ordermgr folder.
    Affected if Order Manager application is deployed and accessible.
  3. Inspect Customer Request form widget configuration
    Locate the Customer Request form definition file (typically in hot-deploy/ordermgr/webapp/ordermgr/customerRequest/ or similar path). Search for the 'story' field definition within the form widget. Inspect the field definition for the encoding attribute.
    Affected if The story field has encoding="false" or encoding="off" explicitly set, or lacks any encoding attribute.
  4. Check for disabled output encoding in form widgets
    Review all form widget XML files in the Order Manager application for textarea fields that may have encoding disabled. Search for: <field name="story"...> or similar textarea definitions with encoding="false".
    Affected if Any textarea field accepting user input has output encoding disabled.

The environment is affected if OFBiz version 16.11.01 through 16.11.05 is installed AND the Order Manager application is deployed with the Customer Request story field configured without output encoding 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 a release after 16.11.05
Interim mitigation

Upgrade Apache OFBiz to version 16.11.06 or later. Alternatively, manually apply commit r1858533 to branch 16.11. Review all form widget configurations to ensure encoding is enabled for any field accepting user input.

Recommended fix High confidence

16.11.06

  1. Backup the current OFBiz installation and database
  2. Upgrade Apache OFBiz from version 16.11.01-16.11.05 to version 16.11.06
  3. Verify the upgrade was successful by checking the OFBiz version
  4. Test the Order Manager application, specifically the Customer Request functionality, to confirm the vulnerability is resolved

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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