CVE-2026-105856: Payload: SQL injection in SQLite/Postgres
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: payloadcms payload 3.73.0.
Low priority for now. Upgrade to payloadcms payload 3.73.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Payload is a free and open source headless content management system. Prior to 3.90.0 and 4.0.0-canary.34, an attacker with read and create or update access to a collection containing a json field or a blocks field with blocksAsJSON enabled can inject SQL through a crafted field path and operators. Collections without those fields are not affected, and richText fields are not affected. The SQLite packages are fixed in versions 3.90.0 and 4.0.0-canary.34, and the Postgres packages are fixed in version 3.73.0.
- Published
- Oct 6, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-89
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 8.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| payloadcms | payload | cpe:2.3:a:payloadcms:payload |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
@payloadcms db-d1-sqlite
- >= 3.0.0, < 3.90.0, >= 4.0.0-canary.0, < 4.0.0-canary.34affected
@payloadcms db-postgres
- >= 3.0.0 < 3.73.0affected
@payloadcms db-sqlite
- >= 3.0.0, < 3.90.0, >= 4.0.0-canary.0, < 4.0.0-canary.34affected
@payloadcms db-vercel-postgres
- >= 3.0.0 < 3.73.0affected
payloadcms payload
- >= 3.0.0, < 3.90.0, >= 4.0.0-canary.0, < 4.0.0-canary.34affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- payloadcms payloadbefore 3.90.0
- payloadcms payload4.0.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @payloadcms/db-d1-sqlite | from 3.0.0 · before 3.90.0 | 3.90.0 |
| npm | @payloadcms/db-d1-sqlite | from 4.0.0-canary.0 · before 4.0.0-canary.34 | 4.0.0-canary.34 |
| npm | @payloadcms/db-postgres | from 3.0.0 · before 3.73.0 | 3.73.0 |
| npm | @payloadcms/db-sqlite | from 3.0.0 · before 3.90.0 | 3.90.0 |
| npm | @payloadcms/db-sqlite | from 4.0.0-canary.0 · before 4.0.0-canary.34 | 4.0.0-canary.34 |
| npm | @payloadcms/db-vercel-postgres | from 3.0.0 · before 3.73.0 | 3.73.0 |
Same product
payloadcms: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-105857Payload: RCE in Payload Form Builder40Plan
- CVE-2022-27952An arbitrary file upload vulnerability in the file upload module of PayloadCMS v0.15.0 allows attackers to execute arbitrary code via a…40Plan
- CVE-2026-105859Payload: Unauthorized update to collection documents39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-105854Oct 6, 2026 · Payload: ReDoS in Multipart Content-Type Validation34Monitor
- ← EarlierCVE-2026-105855Oct 6, 2026 · Payload: Field-level password update restrictions were not enforced30Monitor
- Later →CVE-2026-105858Oct 6, 2026 · Payload: Remote Code Execution through first-register32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| payloadcms payload | 3.73.0 · description | Vendor (CNA) |
| npm:@payloadcms/db-d1-sqlite | 3.90.0 | Package registry (OSV) |
| npm:@payloadcms/db-d1-sqlite | 4.0.0-canary.34 | Package registry (OSV) |
| npm:@payloadcms/db-postgres | 3.73.0 | Package registry (OSV) |
| npm:@payloadcms/db-sqlite | 3.90.0 | Package registry (OSV) |
| npm:@payloadcms/db-sqlite | 4.0.0-canary.34 | Package registry (OSV) |
| npm:@payloadcms/db-vercel-postgres | 3.73.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+41 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1058450 days apartPayload: SQL Injection in SQLite and Postgres39Monitor
- CVE-2026-25544242 days apartPayload has an SQL Injection in JSON/RichText Queries on PostgreSQL/SQLite Adapters39Monitor
- CVE-2026-34747188 days apartPayload has an SQL Injection via Query Handling32Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-1058630 days apartPayload authentication token field handling issue36Monitor
Not on record for this CVE: researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.
The bug in code
The whole CWE-89 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = '" + owner + "'"
);Fixed
const owner = req.query.owner;
const rows = await db.query(
"SELECT * FROM files WHERE owner = $1",
[owner]
);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Expanding Control over the Operating System from the DatabaseCAPEC-470Very High
- SQL InjectionCAPEC-66likelihood: High · High
- Blind SQL InjectionCAPEC-7likelihood: High · High
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.