Skip to main content
← Vulnerabilities

SQL::Abstract versions from 1.90_01 before 2.000001_04 for Perl allow SQL injection via the where values of a nested statement in an…

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

—Not rated
Exploited
No known exploitation
Fix
Fixed in 2.000001_04
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 2.000001_04.

0Pcve.now Index 0 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure?/25Exposure: unknown (data gap). No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity?/10Severity: unknown (data gap). No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 55 if added to CISA KEV
  • Would score about 50 if CISA's SSVC rates exploitation active
  • Would score about 22 if advisories confirm default setups are exposed

CVE-2026-121007 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects SQL-Abstract; fixed in 2.000001_04.

Published
Last modified
Published
Not listed in CISA KEV
0/100 · provisional
Fix
Fixed in 2.000001_04
None on Exploit-DB, Metasploit or GitHub

Summary

Older releases of the SQL::Abstract Perl module let an attacker inject SQL code when an application passes untrusted input as the WHERE values of a nested statement in an identifier position, such as the select list, ORDER BY, or GROUP BY. Those values are placed unescaped into the SQL text instead of being bound as parameters, unless the quote_char setting is used.

Read the original description

SQL::Abstract versions from 1.90_01 before 2.000001_04 for Perl allow SQL injection via the where values of a nested statement in an identifier position. A nested statement such as { -select => ... } in a position where plain scalars are identifiers treats its own plain scalars as identifiers too. These positions are the select list, ORDER BY, GROUP BY, RETURNING, and with the ExtraClauses plugin FROM (-as) and JOIN (to). The values of the statement's where, having and set clauses, and the rows of a -values, go into the SQL text instead of the bind list, unescaped unless quote_char is set. Subselects in a WHERE condition are not affected. An application that passes untrusted input as a where value of such a nested statement, expecting it to be bound, allows SQL injection.

What to do

  • Upgrade to a fixed version: 2.000001_04.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • SQL-Abstract

    From 1.90_01 · fixed in 2.000001_04

Evidence 2

  1. Patch
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121007

Is CVE-2026-121007 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-121007?

SQL-Abstract: from 1.90_01 before 2.000001_04.Source: cve.now feed data

How do I fix CVE-2026-121007?

Upgrade to a fixed version: 2.000001_04.Source: cve.now feed data