PoC Monitor
← All CVEs
CVE-2026-27886published 14 May 2026 18:43 UTCData: JSON · API

Strapi

Strapi may leak sensitive data via relational filtering due to lack of query sanitization

Strapi is an open source headless content management system. Strapi versions starting in 4.0.0 and prior to 5.37.0 did not sufficiently sanitize query parameters when filtering content via relational fields. An unauthenticated attacker could use the `where` query parameter on any publicly-accessible content-type with an `updatedBy` (or other admin-relation) field to perform a boolean-oracle attack against private fields on the joined `admin_users` table, including the `resetPasswordToken` field. Extracting an admin reset token via this oracle made full administrative account takeover possible without authentication. When a filter such as `where[updatedBy][resetPasswordToken][$startsWith]=a` was applied to a public Content API endpoint, the underlying query generation performed a `LEFT JOIN` against the `admin_users` table and emitted a `WHERE` clause referencing the joined column. The query parameter sanitization layer did not block operator chains that traversed into relational target schemas the caller had no read permission on, allowing the response count to be used as a one-bit oracle on any admin-table field. The patch in version 5.37.0 introduces explicit query-parameter sanitization at the controller and service boundary via three new primitives: `strictParam`, `addQueryParams`, and `addBodyParams`. Operator chains that traverse into restricted relational targets are now rejected before reaching the database.

First public PoC 18 daysafter publication · 1 Jun 2026
Public PoCs32 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS9.2critical · scored by CNA · CWE-22
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

strapi strapi
  • >= 4.0.0, < 5.37.0

Fixed in 5.37.0

Mitigation

Upgrade strapi to 5.37.0 or later.

References

Timeline

Days relative to CVE publication
-3t=0+3+6+9+12+15+18CVE published14 May 2026 · t = 0First public PoC1 Jun 2026 · t+18d

First public PoC 18 days after publication; not in CISA KEV. First PoC: EvtDanya/CVE-2026-27886 (created 1 Jun 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

2 PoCs · 1 pending

PoCs 2
RepositoryCreatedStarsAssessment
EvtDanya/CVE-2026-27886 1 Jun 2026 +18 d 0 PoC
thesw0rd/CVE-2026-27886-PoC-Account-Takeover 8 Jun 2026 +25 d 2 PoC
Pending 1
RepositoryCreatedStarsAssessment
BishopFox/CVE-2026-27886-check 22 May 2026 +8 d 1 Pending · mkdir /quarantine/BishopFox__CVE-2026-27886-check-bc436351af74: permission denied

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
nuclei templatenuclei template: Strapi <=5.36.x - Admin Credential Enumeration22 Sep 202614 Nov 2026