dbcve.org
OfbizApplication · Apache

CVE-2020-13923

MEDIUM · 5.3 CVSS v3.1 Published 2020-07-15
Fix available
A fix is available. Upgrade to 17.12.04 or later.
See remediation →
62/100
Remediation priority · Elevated
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
IDOR vulnerability in the order processing feature from ecommerce component of Apache OFBiz before 17.12.04

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 · moderate confidence

An Insecure Direct Object Reference (IDOR) vulnerability in the order processing feature of Apache OFBiz's ecommerce component allows authenticated users to potentially access or modify orders belonging to other users by manipulating object references (order IDs). This is an access control weakness in the order processing functionality.

MitigationUpgrade Apache OFBiz to version 17.12.04 or later to obtain the patch. If immediate upgrade is not feasible, implement explicit ownership verification checks on all order processing endpoints to ensure users can only access their own orders.

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

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

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

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. Determine the installed Apache OFBiz version
    Locate the OFBiz installation directory and check the version. In the root directory, look for a VERSION file or check build.gradle for the version number. Alternatively, access the admin console and find the version information under 'System' or 'About' sections.
    Affected if The installed version is any version prior to 17.12.04 (for example, 17.12.00 through 17.12.03, or earlier releases).
  2. Verify the ecommerce component is deployed
    Check if the 'ecommerce' webapp is deployed in your OFBiz installation. Look for an 'ecommerce' directory under the 'hot-deploy' or 'applications' folder, and verify the component is listed in the 'ofbiz-component.xml' file.
    Affected if The ecommerce component is deployed and accessible to users.
  3. Confirm user authentication is required for order access
    Test the order processing endpoints by logging into the ecommerce portal as a regular (non-admin) user. Verify that authentication is enforced before accessing order-related URLs.
    Affected if The system allows authenticated users to access order processing functionality.
  4. Test for IDOR on order IDs
    As an authenticated user with an order, capture your own order ID from the order history page. Then attempt to access or modify that order using a different user's order ID (obtained from another account or by manipulating the order ID parameter in the request URL). Observe if the system returns order details for a different user's order without proper authorization checks.
    Affected if The system returns order details or allows modifications to orders belonging to other users when providing a different user's order ID, indicating missing ownership verification.

You are affected if your OFBiz installation is version 17.12.03 or earlier AND the ecommerce component is deployed, allowing authenticated users to access or modify orders belonging to other users via direct order ID manipulation.

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.

From vendor data
Upgrade available Upgrade to 17.12.04 or later
Fixed in 17.12.04
Interim mitigation

Upgrade Apache OFBiz to version 17.12.04 or later to obtain the patch. If immediate upgrade is not feasible, implement explicit ownership verification checks on all order processing endpoints to ensure users can only access their own orders.

Fix this in Ofbiz Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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