dbcve.org
OfbizApplication · Apache

CVE-2024-48962

HIGH · 8.8 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 18.12.17 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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'), Cross-Site Request Forgery (CSRF), : Improper Neutralization of Special Elements Used in a Template Engine vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 18.12.17. Users are recommended to upgrade to version 18.12.17, 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 · moderate confidence

Apache OFBiz before version 18.12.17 contains multiple vulnerabilities including code injection, CSRF, and template injection in its template engine. The template engine vulnerability allows attackers to inject malicious code through unsanitized template inputs, potentially leading to remote code execution. The CSRF vulnerability could allow attackers to trick authenticated users into performing unintended actions.

MitigationUpgrade Apache OFBiz to version 18.12.17 or later to address all three vulnerabilities. Since this involves code injection with CVSS 8.8, prioritize patching immediately and review for any signs of compromise.

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

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 and version
    Locate the OFBiz installation directory and check the version. Typically found in a build file (like 'build.gradle' or 'pom.xml') in the root directory, or in a VERSION or RELEASE_NOTES file. Run: cat /path/to/ofbiz/VERSION or grep -r 'version' build.gradle | head -5
    Affected if The installed version is lower than 18.12.17 (for example, 18.12.16, 18.12.15, earlier releases, or any nightly build)
  2. Verify the OFBiz server is running and accessible
    Confirm the OFBiz web application is active. Check if the default ports (8443 for https or 8080 for http) are listening. Run: netstat -tlnp | grep -E '8080|8443' or curl -k https://localhost:8443/
    Affected if The OFBiz server is exposed and running an affected version
  3. Review template engine configuration
    Inspect the template engine configuration files in the OFBiz framework. Look for FreeMarker or Velocity template settings in the 'framework' directory under 'webapp' or 'widget' configurations. Check for any custom template files in the 'applications' or 'specialpurpose' directories.
    Affected if Custom or third-party templates are present and the OFBiz version is below 18.12.17
  4. Check for CSRF token configuration
    Review the security configuration files to verify if CSRF protection is properly enforced. Examine 'security.properties' or 'csrf.conf' files in the OFBiz configuration directories.
    Affected if CSRF protection is disabled or misconfigured and the OFBiz version is below 18.12.17

If Apache OFBiz is running and the installed version is any release lower than 18.12.17, the environment is vulnerable to the template injection and CSRF bypass described in this CVE.

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 18.12.17 or later
Fixed in 18.12.17
Interim mitigation

Upgrade Apache OFBiz to version 18.12.17 or later to address all three vulnerabilities. Since this involves code injection with CVSS 8.8, prioritize patching immediately and review for any signs of compromise.

Recommended fix High confidence

18.12.17

  1. Back up the current OFBiz installation and database
  2. Download Apache OFBiz version 18.12.17 from the official Apache OFBiz website (ofbiz.apache.org)
  3. Stop all running OFBiz services
  4. Replace the existing OFBiz installation files with the new version 18.12.17
  5. Review and update any custom configurations or plugins for compatibility with version 18.12.17
  6. Start the OFBiz services
  7. Verify the upgrade was successful by confirming services are running properly and the vulnerability is addressed
Caveat No explicit breaking changes mentioned in the advisory; standard upgrade precautions apply

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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