CVE-2026-13766: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in EXODIST DBIx::QuickORM
DBIx::QuickORM versions before 0.000026 for Perl allow SQL injection via unquoted SQL identifiers. The default SQL builder, a SQL::Abstract subclass, sets bindtype in its constructor but never quote_char, so SQL::Abstract emits identifiers verbatim. Caller-supplied identifiers (order_by, where-clause column keys, field and returning lists, upsert columns, and join aliases) reach the SQL string raw, while values are placeholder-bound and unaffected. A caller that forwards untrusted input to an affected identifier position, such as a user-controlled order_by value, enables SQL injection: the row order can be made to depend on a sub-select over columns the query never selected, and the where and update identifier positions permit further data disclosure and tampering.
AI Analysis
Technical Summary
DBIx::QuickORM versions prior to 0.000026 use a SQL::Abstract subclass as the default SQL builder that sets bindtype but does not set quote_char. As a result, SQL identifiers provided by the caller (including order_by, where-clause column keys, field lists, returning lists, upsert columns, and join aliases) are inserted verbatim into SQL statements without quoting. While values are safely placeholder-bound, untrusted input in identifier positions can lead to SQL injection. This vulnerability allows attackers to manipulate query order, disclose data, and tamper with queries by injecting malicious SQL through unquoted identifiers.
Potential Impact
An attacker who can supply input to identifier positions in SQL queries (such as order_by or where-clause columns) can perform SQL injection attacks. This can result in unauthorized data disclosure, modification, or tampering with database queries. The vulnerability affects the integrity and confidentiality of the database operations performed by DBIx::QuickORM.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid passing untrusted input to SQL identifier positions such as order_by, where-clause columns, field lists, returning lists, upsert columns, and join aliases. Implement input validation or sanitization to ensure identifiers are safe or use alternative query-building methods that properly quote identifiers.
CVE-2026-13766: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in EXODIST DBIx::QuickORM
Description
DBIx::QuickORM versions before 0.000026 for Perl allow SQL injection via unquoted SQL identifiers. The default SQL builder, a SQL::Abstract subclass, sets bindtype in its constructor but never quote_char, so SQL::Abstract emits identifiers verbatim. Caller-supplied identifiers (order_by, where-clause column keys, field and returning lists, upsert columns, and join aliases) reach the SQL string raw, while values are placeholder-bound and unaffected. A caller that forwards untrusted input to an affected identifier position, such as a user-controlled order_by value, enables SQL injection: the row order can be made to depend on a sub-select over columns the query never selected, and the where and update identifier positions permit further data disclosure and tampering.
CVSS v3.1
Score 9.8critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
DBIx::QuickORM versions prior to 0.000026 use a SQL::Abstract subclass as the default SQL builder that sets bindtype but does not set quote_char. As a result, SQL identifiers provided by the caller (including order_by, where-clause column keys, field lists, returning lists, upsert columns, and join aliases) are inserted verbatim into SQL statements without quoting. While values are safely placeholder-bound, untrusted input in identifier positions can lead to SQL injection. This vulnerability allows attackers to manipulate query order, disclose data, and tamper with queries by injecting malicious SQL through unquoted identifiers.
Potential Impact
An attacker who can supply input to identifier positions in SQL queries (such as order_by or where-clause columns) can perform SQL injection attacks. This can result in unauthorized data disclosure, modification, or tampering with database queries. The vulnerability affects the integrity and confidentiality of the database operations performed by DBIx::QuickORM.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid passing untrusted input to SQL identifier positions such as order_by, where-clause columns, field lists, returning lists, upsert columns, and join aliases. Implement input validation or sanitization to ensure identifiers are safe or use alternative query-building methods that properly quote identifiers.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-06-29T19:58:43.298Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a43addd27e9c79719af4960
Added to database: 06/30/2026, 11:51:57 UTC
Last enriched: 06/30/2026, 12:07:07 UTC
Last updated: 06/30/2026, 23:49:34 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.