dbcve.org
OfbizApplication · Apache

CVE-2013-2250

HIGH · 10.0 CVSS v2.0 Published 2013-08-15
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
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
Apache Open For Business Project (aka OFBiz) 10.04.01 through 10.04.05, 11.04.01 through 11.04.02, and 12.04.01 allows remote attackers to execute arbitrary Unified Expression Language (UEL) functions via JUEL metacharacters in unspecified parameters, related to nested expressions.

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 versions 10.04.01-10.04.05, 11.04.01-11.04.02, and 12.04.01 contains an Expression Language (EL) injection vulnerability (CWE-917) where attackers can inject arbitrary Unified Expression Language (UEL) functions via JUEL metacharacters in unspecified parameters. The vulnerability leverages nested expressions to achieve remote code execution.

MitigationUpgrade to a patched OFBiz version (post-12.04.01) or apply input validation/sanitization to prevent JUEL metacharacter injection in all user-supplied parameters processed by the EL evaluator.

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:= 10.04.01= 10.04.02= 10.04.03= 10.04.04= 10.04.05= 11.04.01= 11.04.02= 12.04.01

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 file or manifest. Common locations include the root directory containing 'build.gradle', 'framework/', or 'applications/' folders. Look for a VERSION file or check the build.properties for the ofbiz.version property.
    Affected if The installed version matches 10.04.01 through 10.04.05, 11.04.01 through 11.04.02, or 12.04.01 exactly.
  2. Verify web interface is exposed
    Check if the OFBiz web server is running and accessible. Look for the 'web' or 'specialpurpose' directory containing JSP or controller.xml files that handle incoming requests. Confirm the port (default 8443 for HTTPS or 8080 for HTTP) is listening.
    Affected if The OFBiz web interface is exposed and accessible to network users.
  3. Identify EL-evaluated request parameters
    Review the controller.xml files in applications and the webapp directories for 'service' or 'method' calls that use the 'entity-name' or 'service' attributes with parameter interpolation. Look for parameters passed to the evaluate conditions in the control servlet.
    Affected if User-supplied request parameters are processed through the JUEL expression evaluator without sanitization.
  4. Check for injection attempt indicators in logs
    Examine OFBiz logs (typically in runtime/logs/ or the console output) for unusual patterns in request parameters. Search for JUEL metacharacters like '${', '#{', or nested expression patterns in access logs.
    Affected if Logs contain requests with '${', '#{', or similar EL metacharacters in parameter values.

The environment is affected if Apache OFBiz versions 10.04.01-10.04.05, 11.04.01-11.04.02, or 12.04.01 is installed and the web interface processes user-supplied parameters through the Unified Expression Language (UEL) evaluator.

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
Patch available Apply the vendor patch
Vendor patch ofbiz.apache.org →
Interim mitigation

Upgrade to a patched OFBiz version (post-12.04.01) or apply input validation/sanitization to prevent JUEL metacharacter injection in all user-supplied parameters processed by the EL evaluator.

Recommended fix High confidence

12.04.02 or later (or 10.04.06/11.04.03 if maintaining older branch)

  1. 1. Back up your current OFBiz installation and database before proceeding with any upgrade.
  2. 2. Download the fixed OFBiz version from the official Apache OFBiz download page: https://ofbiz.apache.org/download.html
  3. 3. For version 10.04.x, upgrade to at least version 10.04.06 or migrate to a newer stable release (11.04.03 or 12.04.02+)
  4. 4. For version 11.04.x, upgrade to at least version 11.04.03 or migrate to 12.04.02+
  5. 5. For version 12.04.01, upgrade to version 12.04.02 or later
  6. 6. Deploy the new version and test critical business workflows
  7. 7. Verify the vulnerability is no longer present by testing for JUEL metacharacter injection in parameters
Caveat Major version upgrades may include API changes; review release notes for backward compatibility concerns

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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