recorded together · two weakness classes
SQL Injection and Command and Code Injection
16 CVEs
16 CVEs name a weakness of both SQL Injection and Command and Code Injection, too few to compare with chance. The pairing most often behind it is CWE-89 (SQL Injection) with CWE-94 (Code Injection), in 7 CVEs.
Every dot is a CVE whose record names a weakness from both classes, neither being the other's parent in the CWE hierarchy. The named ones come first: exploited in the wild, then those with a public check, then the likeliest to be.
- CVEs that carry a weakness of both
- 16
- Chance alone would give
- about 14
- So they are recorded together
- too few CVEs to say
A CVE counts when its record names a weakness from each class, neither being the other's parent. It says the two kinds of flaw are recorded together in one vulnerability more or less often than chance: not that one causes the other, and it follows how the people who file CVEs choose CWEs.
How this is weighed, and the sources
Chance is what the two classes' shares of all CVEs that carry weaknesses of two or more classes would give if weaknesses paired at random. A line is drawn on the dial from 25 CVEs and 1.15 times chance. Weaknesses are the CWEs the CVE List and NVD record; exploitation is CISA KEV, likelihood is EPSS.
Every one of the 16 is a mark on the map. Named now: 1 to 16, most at risk first.
- CryptoLog Unauthenticated RCE via SQL Injection and Command Injection
- Riverbed SteelCentral NetProfiler / NetExpress 10.8.7 RCE
- SQL injection vulnerability in the Help Desk application in Wave EMBASSY Remote Administration Server (ERAS) allows remote authenticated users to execute arbitrary SQL commands vi…
- DIRAC: RCE in FileCatalog DatasetManager via SQL injection + eval
- SQLBot: RCE via SQL Injection in Excel Upload Endpoint
- n8n has Potential Remote Code Execution via Merge Node
- Saurus CMS Community Edition 4.7.1 contains a vulnerability in the custom DB::prepare() function, which uses preg_replace() with the deprecated /e (eval) modifier to interpolate S…
- pgAdmin 4: AI Assistant read-only transaction bypass allows unauthorised writes and remote code execution
- Orval: RCE via schema property name -> computed-property-key injection in the MSW mock generator
- Orval: Import-time RCE via schema property name -> computed-property-key injection in the zod client
- Pimcore: Remote Code Execution via DataObject Class-Definition Field Name
- Langroid has Prompt to SQL Injection, Leading to RCE
- WeGIA: Pre-auth Installer Injection Chain Enables Command Execution and Arbitrary PHP Code Injection
- Twenty: SQL Injection via the timeZone field
- baserCMS < 5.3.0 SQL Injection and Code Injection via BcDatabaseService.php
- Elo: Code injection in Elo backends via unvalidated emission of programmatic AST fields
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.