dbcve.org
OfbizApplication · Apache

CVE-2026-41919

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 24.09.06 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
Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 24.09.06. Users are recommended to upgrade to version 24.09.06, 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 versions before 24.09.06 contain an LDAP Injection vulnerability where unsanitized user input is used in LDAP queries. This allows attackers to manipulate LDAP statements to bypass authentication, enumerate directory contents, or extract sensitive information.

MitigationUpgrade Apache OFBiz to version 24.09.06 or later to apply the fix for this LDAP injection vulnerability.

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

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Identify installed Apache OFBiz version
    Locate the OFBiz version file or check the build configuration (typically in version.properties, build.xml, or the application's main about/page). Compare the version number to 24.09.06.
    Affected if The installed version is lower than 24.09.06 (e.g., 24.09.05, 18.12.x, earlier releases).
  2. Determine if LDAP integration is configured
    Inspect the OFBiz configuration files for LDAP settings. Look for ldap* properties in config files such as general.properties, security.xml, or within the LDAP connector configuration in the OFBiz administration interface.
    Affected if LDAP is enabled and OFBiz is configured to authenticate against or query an LDAP directory.
  3. Verify LDAP authentication or query components are in use
    Review the OFBiz web controller definitions (controller.xml files) and service definitions (service*.xml files) for LDAP-related actions, services, or authentication handlers that process user-provided input.
    Affected if The system uses LDAP-based authentication, user lookup, or group/role synchronization that processes user input.
  4. Inspect LDAP query construction for unsanitized input
    Examine the LDAP-specific Java code or Groovy scripts within OFBiz that build LDAP search filters or bind operations. Look for instances where request parameters, login credentials, or search terms are concatenated directly into LDAP filter strings without proper escaping or parameterization.
    Affected if User-supplied parameters are directly interpolated into LDAP filter strings without neutralization of special LDAP meta-characters.

You are affected if your installed Apache OFBiz version is below 24.09.06 AND the system has LDAP authentication, user synchronization, or LDAP query functionality enabled and operational.

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.06 or later
Fixed in 24.09.06
Interim mitigation

Upgrade Apache OFBiz to version 24.09.06 or later to apply the fix for this LDAP injection vulnerability.

Recommended fix High confidence

24.09.06

  1. Backup your current Apache OFBiz installation and database before upgrading
  2. Download Apache OFBiz version 24.09.06 from the official Apache OFBiz distribution (https://ofbiz.apache.org/download.html)
  3. Review the official upgrade notes and migration guide for 24.09.06
  4. Stop the currently running OFBiz services
  5. Replace the old OFBiz installation files with the new version 24.09.06 files
  6. Run any database migration scripts provided in the upgrade
  7. Start the OFBiz services and verify the application is functioning correctly
  8. Test that the LDAP injection vulnerability is no longer present
Caveat Review release notes for potential breaking changes between your current version and 24.09.06; test thoroughly in staging before production deployment

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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