GHSA-92hp-j24w-3jvw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach performFind endpoint unauthenticated
-
DeliverySubmit ignore-case find with backslash payload
-
ExploitBreak out of inlined SQL string literal
-
ExecutionTurn WHERE clause into tautology
-
ImpactDisclose arbitrary entity rows
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the OFBiz deployment to use a MySQL or MariaDB datasource, because the flaw depends on those dialects honoring backslash escapes; the default Derby datasource and PostgreSQL are explicitly not affected and cannot be exploited this way. The attacker must reach the entity engine's generic performFind service and submit an ignore-case find request (e.g. _ic=Y) with a backslash-terminated crafted value so that SqlJdbcUtil.addValueSingle inlines the EntityFunction-wrapped value using ANSI single-quote doubling only. Limiting factors: only OFBiz 24.09 before 24.09.08 is affected, and the database backend must be MySQL/MariaDB - a non-universal (though common) configuration - while no authentication or user interaction is required (PR:N/UI:N) once those conditions hold. |
| Impact | Signals diverge sharply. The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) and 9.8 score describe a network-reachable, unauthenticated, low-complexity flaw, and the vuln.today Decision label is act_now - all pointing to high urgency. However, the described impact is limited to disclosure of arbitrary rows from the queried entity (a read/tautology primitive), so the input's C:H/I:H/A:H is not fully supported by the mechanism described, which establishes confidentiality impact but not integrity or availability. Exploitation is further gated to MySQL/MariaDB-backed deployments; default Derby and PostgreSQL installations are explicitly not affected, which materially narrows the real-world population. EPSS is low (0.28%, 20th percentile) and the CVE is not in CISA KEV with no public exploit identified, indicating no evidence of widespread or automated exploitation yet. Net: treat as a genuine, patch-now priority for OFBiz 24.09 instances running on MySQL/MariaDB, but the headline 9.8 overstates both the impact breadth (disclosure-only per the description) and the deployment breadth (MySQL/MariaDB only); low EPSS and absence of KEV/PoC argue against imminent mass exploitation. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends an ignore-case find request (e.g. with _ic=Y) to the generic performFind service on an OFBiz 24.09 instance backed by MySQL or MariaDB, supplying a backslash-terminated value that escapes the inlined single-quoted string literal and converts the WHERE clause into a tautology, returning arbitrary rows of the queried entity. No public exploit is identified at the time of analysis, and the attack only succeeds against MySQL/MariaDB deployments, not the default Derby or PostgreSQL datasources. Low attack complexity (AC:L) and no authentication (PR:N) make the request itself trivial to craft once a vulnerable backend is present. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Nov 10, 2026
Unauthenticated SQL injection in Apache OFBiz 24.09 (before 24.09.08) allows a remote attacker to disclose arbitrary rows from the queried entity when the deployment is backed by MySQL or MariaDB. The flaw lives in the entity engine's generic performFind service: an ignore-case find request (_ic=Y) with a crafted value causes SqlJdbcUtil.addValueSingle to inline the EntityFunction-wrapped value into the SQL text using ANSI-only single-quote doubling, which backslash-terminated payloads defeat on MySQL/MariaDB because those dialects also honor backslash escapes, turning the WHERE clause into a tautology. Only confidentiality is impacted per the assessed vector; the default Derby datasource and PostgreSQL are explicitly not affected, EPSS is low at 0.28% (20th percentile), and no public exploit has been identified at time of analysis, although the vendor has released 24.09.08 and the issue carries an act_now priority decision.
Earlier versions of this analysis (1)
SQL injection in Apache OFBiz (all releases prior to 24.09.08) allows an attacker who can reach the entity engine's generic performFind search service with a controllable ignore-case value to inject into the SQL generated for case-insensitive searches, with high confidentiality and integrity impact on deployments backed by MySQL or MariaDB. The flaw is one of 46 CVEs published together in a single oss-security advisory and fixed by the 24.09.08 release, alongside far more severe siblings such as pre-authentication RCE and authentication bypasses, which will likely dominate triage. No CISA KEV listing, EPSS score or public exploit code was identified at time of analysis, and the vuln.today decision label is 'awaiting_data', so no quantitative priority ranking is currently available.
RemediationAI
Vendor-released patch: Apache OFBiz 24.09.08, which the advisory recommends all users upgrade to; the fix removes the inlining path that produced the insufficient ANSI-only quoting. Because the advisory explicitly states that the default Derby datasource and PostgreSQL are not affected, organizations that cannot immediately upgrade a MySQL/MariaDB-backed 24.09 deployment can reduce exposure by moving the datasource to a non-affected backend, recognizing that this is an architectural and data-migration change rather than a drop-in switch. The authoritative upgrade guidance is in the oss-security advisory at https://seclists.org/oss-sec/2026/q4/516 and the project page at https://ofbiz.apache.org/, with the Apache mailing-list thread at https://lists.apache.org/thread.html/7b2syzksp7klt9fvhdg0olldvs2g83lz; no public exploit has been identified at time of analysis, but the act_now priority decision and the unauthenticated network vector argue for treating the upgrade as time-sensitive on any MySQL/MariaDB-backed instance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache OFBiz's entity engine exposes a generic performFind service that builds SQL for entity queries; when a request sets ignore-case (_ic=Y), the value is wrapped in an EntityFunction and passed through SqlJdbcUtil.addValueSingle, which in this code path concatenates the value into the SQL string rather than binding it as a JDBC parameter. The escaping applied is ANSI single-quote doubling only, so a backslash-terminated payload breaks out of the string literal on MySQL and MariaDB, which interpret backslash as an escape character inside literals - the classic CWE-89 precondition where a non-parameterized value reaches the database with dialect-inappropriate quoting. The result is a tautological WHERE clause that lets the attacker read rows from the queried entity. The default Derby datasource and PostgreSQL do not treat backslash as an escape in this context and are therefore not exploitable through this path; note that the supplied reference tags mention PostgreSQL, but the advisory explicitly exempts both PostgreSQL and Derby. The assessed impact is confidentiality-only (C:H/I:N/A:N) over AV:N/AC:L/PR:N/UI:N, and exploitation is conditional on the deployment using a MySQL or MariaDB datasource plus the ability to reach the performFind service and submit an ignore-case request.
Know when MySQL gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network, unauthenticated, low-complexity request on MySQL/MariaDB backends; the described primitive discloses arbitrary rows, so C:H but I:N/A:N as no write or availability impact is established.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
4Description PRE-NVD
Articles & Coverage 1
Executive ViewAI
A critical unauthenticated SQL injection vulnerability in Apache OFBiz 24.09 (before 24.09.08) could allow remote attackers to read arbitrary data from MySQL/MariaDB-backed deployments, directly threatening customer or operational data confidentiality. Organizations running affected OFBiz installations should treat this as a high-priority exposure requiring immediate remediation to prevent potential data breach and compliance ramifications.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.2
MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the
Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Rated high severity
sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x befor
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16,
Heap-based buffer overflow in Oracle MySQL 5.5.19 and other versions through 5.5.28, and MariaDB 5.5.28a and possibly ot
Stack-based buffer overflow in the acl_get function in Oracle MySQL 5.5.19 and other versions through 5.5.28, and 5.1.53
Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due
mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB; Percona Server befo
Oracle MySQL before 5.7.3, Oracle MySQL Connector/C (aka libmysqlclient) before 6.1.3, and MariaDB before 5.5.44 use the
HUSTOJ online judge has a path traversal vulnerability enabling arbitrary file access on the competition server.
Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2
EUVD-2026-117483
NVD
CVE.org
EPSS
Exploit-DB