CVE-2026-13766
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 · uneditedDBIx::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.
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 confidenceDBIx::QuickORM versions before 0.000026 use a SQL::Abstract subclass that sets bindtype but omits quote_char, causing the SQL builder to emit identifiers (order_by, where-clause keys, field lists, join aliases, upsert columns) verbatim without escaping. Values are safely placeholder-bound, but untrusted input passed to identifier positions allows attackers to manipulate SQL structure, potentially disclosing data or tampering via sub-selects in ordering or where clauses.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed DBIx::QuickORM versionRun 'perl -MDBIx::QuickORM -e "print $DBIx::QuickORM::VERSION"' or check via cpanm/cpan listing, or inspect your project's dependency file (cpanfile, cpanfile.snapshot, or Makefile.PL)Affected if Version is lower than 0.000026 (e.g., 0.000025 or earlier)
-
Identify order_by with external inputSearch codebase for calls to methods that accept order_by parameters (e.g., quick_find, find, select) and trace whether user-supplied data (request parameters, API input, user variables) flows into the order_by argumentAffected if Untrusted input is passed to order_by without sanitization or allowlist filtering
-
Identify where-clause keys with external inputSearch for where clause construction where hash keys (the field names in where conditions) come from user input, such as dynamic column filtering implementationsAffected if User-controlled values are used as hash keys in where clause construction
-
Identify field list with external inputSearch for code that dynamically builds field lists (columns to select) from request parameters or other external sourcesAffected if User input directly determines which fields are requested in queries
-
Identify join aliases with external inputSearch for code that constructs joins where table aliases or join conditions derive from user inputAffected if User input flows into join alias names or join ON conditions
-
Identify upsert column usage with external inputSearch for upsert/insert operations (quick_insert, quick_upsert) where column names are determined by external inputAffected if User-supplied values are used as column names in upsert operations
You are affected if DBIx::QuickORM version is before 0.000026 AND untrusted input flows to any identifier positions (order_by, where clause keys, field lists, join aliases, or upsert columns).
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to DBIx::QuickORM version 0.000026 or later which properly configures quote_char in the SQL builder constructor to enforce identifier escaping.
0.000026
- Upgrade DBIx::QuickORM to version 0.000026 or later using your Perl module installer (e.g., cpanm DBIx::QuickORM or cpan DBIx::QuickORM)
- Verify the installed version matches or exceeds 0.000026 by running perl -MDBIx::QuickORM -e 'print $DBIx::QuickORM::VERSION'
- If applying the patch instead of upgrading, review the changes at https://github.com/exodist/DBIx-QuickORM/commit/43d7684682050780f056f25e1879191fb0a3265e and ensure quote_char is properly set in the SQL builder constructor
- After upgrade or patch, audit any code passing user-supplied input to identifier positions (order_by, where clause keys, field lists, returning lists, upsert columns, join aliases) and ensure proper input validation or allowlisting
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13766 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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