Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-27886 Scanner

CVE-2026-27886 Scanner - User Enumeration vulnerability in Strapi

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
5
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
9.2
CVSScritical
Exploitable remotely over the internet · no authentication required.
Description

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
strapiby strapi
>= 4.0.0, < 5.37.0
Updated Nov 6, 2026View on NVD →
Detail

Strapi is widely utilized by developers and organizations as an open-source headless CMS, helping them speed up the process of content management with flexible APIs. It allows users to create, manage, and expose content using both RESTful and GraphQL endpoints. Strapi is popular for its full customization capability, allowing users to define their data structures. Its usage is prominent in startups and enterprises looking to leverage modern technology with easy modifications. The platform can be utilized for both small-scale applications and robust projects due to its adaptability. Strapi combines the ease of management with extensibility to cater to diverse development needs.

User Enumeration vulnerabilities occur when an application divulges information about which usernames or other identifiers are valid. If not identified and resolved, this can lead to unauthorized access and other security implications. Attackers exploit these vulnerabilities to enumerate users and subsequently launch more severe attacks. Understanding these vulnerabilities is crucial for preventing data breaches. The CVE-2026-27886 vulnerability involves a boolean-oracle attack that can enable attackers to recover private fields from administrative tables without authentication. This could allow malicious entities to gain unauthorized access and exploit the compromised system.

The specific vulnerability in Strapi versions <=5.36.x involves the insufficient sanitization of query parameters when filtering content via relational fields. The attack targets the `where` query parameter accessible on publicly-viewable content-types with `updatedBy` fields. Without proper sanitization, attackers could perform a boolean-oracle attack against private fields in the admin_users table, such as the resetPasswordToken. This allows attackers to ascertain sensitive information like email addresses and reset tokens, facilitating unauthorized account takeovers. The vulnerability resides in the way relational field queries are processed and how it interacts with insufficiently protected data.

Exploiting this vulnerability can lead to severe consequences, enabling attackers to gain administrative account control. This poses risks of unauthorized content manipulation, exposure of sensitive data, and potential service disruptions. Once attackers obtain admin credentials, they can alter configurations, access sensitive data, and perform other malicious activities without detection. It can also lead to degraded integrity of the system and a significant reputational impact if sensitive information is leaked. Mitigating this vulnerability is crucial to maintaining operational security and institutional trust.

REFERENCES

Solution Advice
  • Upgrade Strapi to version 5.37.0 or later to benefit from query-parameter sanitization improvements.
  • Ensure the application has adequate input validation for all user inputs, especially those used in queries.
  • Regularly audit and update access controls to ensure only necessary exposure of relational fields.
  • Implement monitoring and alerting capabilities to detect potential exploitation attempts.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

12,000+ scanners. Free to start. No credit card required.