CVE-2026-63316GHSA-PJ7X-6WPF-PGVP
SQL Injection in Payload CMS
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.90.0, 4.0.0-canary.34, 3.73.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A SQL injection vulnerability has been identified in Payload CMS. Improper neutralization of input provided by user into "in" and "not_in" query paramethers allows an authenticated attacker to perform SQL Injection attacks. This issue was fixed in version 3.90.0 and 4.0.0-canary.34.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Payload Payload CMS
fixed in 3.90.0; From 4.0.0-canary.0 · fixed in 4.0.0-canary.34
- @payloadcms/db-sqlitenpm
From 3.0.0 · fixed in 3.90.0
- @payloadcms/db-d1-sqlitenpm
From 3.0.0 · fixed in 3.90.0
- @payloadcms/db-postgresnpm
From 3.0.0 · fixed in 3.73.0
- @payloadcms/db-vercel-postgresnpm
From 3.0.0 · fixed in 3.73.0
- @payloadcms/db-sqlitenpm
From 4.0.0-canary.0 · fixed in 4.0.0-canary.34
- @payloadcms/db-d1-sqlitenpm
From 4.0.0-canary.0 · fixed in 4.0.0-canary.34