Skip to content

CVE-2026-108114: Strapi Improper Authorization via Admin API Token Field Permissions

Density:
HERMES

HERMES THREAT SCORE & HEADLESS CMS INFRASTRUCTURE EVALUATION

Target: Strapi Headless CMS โ€” Admin Content-Manager API Token RBAC Engine
Confidence: 98%
92 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 17 / 20
Weaponization 19 / 20
Exposure 18 / 20
Prevalence 18 / 20
Impact 19 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

CVSS v3.1 scores this vulnerability at 9.1 (CRITICAL) despite requiring low privileges (PR:L) because administrative read/write API tokens are widely distributed to microservices, CI/CD runners, and headless web frontend builders. The Hermes Threat Score confirms 92 (CRITICAL). In modern headless CMS architectures, frontends consume API tokens that are presumed to be strictly confined to public fields. Bypassing field permissions enables complete exposure of internal credentials and confidential tenant columns across corporate digital experience platforms.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-108114: Strapi Improper Authorization via Admin API Token Field PermissionsVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTStrapi Headless CMS
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Strapi Headless CMS documented in Hermes dossier.”

Supporting Verified Evidence:

Strapi powers thousands of corporate websites, mobile backend services, and multi-tenant content hubs, serving content over automated GraphQL and REST endpoints.

ParameterTechnical SpecificationOperational Details
CVE IdentifierCVE-2026-108114Canonical vulnerability tracking identifier
Affected ProductStrapi Headless CMSNode.js enterprise content platform
Vulnerable Componentpackages/core/admin/server/services/api-token.jsContent-Manager field-level RBAC resolver
Impacted Versions5.47.0 through 5.57.0Production Strapi v5 installations
Corrective Release5.57.1Recursive attribute authorization enforcement
Vulnerability ClassImproper Authorization (CWE-285, CWE-863)Broken Object Property Level Authorization (BOPLA)
Runtime EnvironmentNode.js v18 / v20 / v22 on Linux & Cloud ContainersDistributed CMS and microservice data layer

When an incoming request is authenticated via an Admin API token, Strapi resolves the tokenโ€™s granted permissions and passes them to the content sanitizer. In vulnerable releases, relational fields and batch endpoints circumvent this filter:

packages/core/content-manager/server/services/permission-checker.js
const sanitizeOutput = async (data, { action, model }) => {
const permissions = await getApiTokenPermissions(token);
const allowedFields = getAllowedFields(permissions, action, model);
// FLAW: If allowedFields is defined, only shallow properties of the root entity are pruned
if (Array.isArray(allowedFields) && allowedFields.length > 0) {
const sanitized = _.pick(data, allowedFields);
// Nested relations and batch children are passed through WITHOUT recursive filtering!
if (data.relations) {
sanitized.relations = data.relations; // Sensitive related entity fields leak here!
}
return sanitized;
}
return data;
};
Restricted API Token Strapi Content-Manager Route Nested Serializer
+---------------------+ +---------------------+ +---------------------+
| GET /api/articles | | Top-level fields: | | Nested relation |
| ?populate[author] | ---------> | "title", "content" | ------------> | "author.password", |
| [*] | | (Allowed) | | "author.mfa_secret" |
+---------------------+ +---------------------+ +---------------------+
|
v
+---------------------+
| Data Leak: Token |
| Extracts Restricted |
| Credentials! |
+---------------------+

  1. Low-Privilege API Token Acquisition: An adversary compromises a read-only or microservice API token (often hardcoded in static site generators, mobile apps, or frontend CI pipelines).
  2. Deep Relational Query Forgery: The attacker submits requests using deep relation population patterns:
    GET /api/content-manager/collection-types/api::article.article?populate[created_by][fields]=* HTTP/1.1
    Host: strapi.enterprise.internal
    Authorization: Bearer <restricted_api_token>
  3. Extraction of Administrative Secrets: The response returns sensitive administrator accounts, password hashes, and security reset tokens that were intended to be masked by field permissions, enabling lateral takeover of the CMS administrative console.

title: Strapi Admin API Token Field Restriction Bypass Attempt
id: b925c410-681a-4d92-bb8a-1f81023a9104
status: experimental
description: Detects HTTP requests targeting Strapi content-manager endpoints attempting to populate restricted sensitive attributes using API tokens.
references:
- https://vulncheck.com/advisories/strapi-5.47.0-through-5.57.0-improper-authorization-via-admin-api-token-field-permissions
author: Hermes Codex CTI Team
date: 2026/10/11
logsource:
category: webserver
product: strapi
detection:
selection_path:
cs-method:
- 'GET'
- 'POST'
cs-uri-stem|contains:
- '/api/content-manager/'
- '/content-manager/collection-types/'
selection_query:
cs-uri-query|contains:
- 'populate[created_by]'
- 'populate[updated_by]'
- 'populate=*'
- 'fields=password'
- 'fields=resetToken'
condition: selection_path and selection_query
fields:
- c-ip
- cs-username
- cs-uri-stem
- cs-uri-query
falsepositives:
- Internal administrative dashboard operations performing legitimate full audit logging
level: high
tags:
- attack.initial_access
- attack.t1190

Upgrade Strapi dependencies in package.json to release 5.57.1:

{
"dependencies": {
"@strapi/strapi": "5.57.1"
}
}

Then rebuild and deploy:

Terminal window
npm install
npm run build
npm run start

The fix introduces recursive attribute evaluation across all relation trees:

// PATCHED LOGIC in Strapi 5.57.1
const sanitizeOutput = async (data, { action, model }) => {
const permissions = await getApiTokenPermissions(token);
return recursiveFieldSanitizer(data, model, permissions, action);
};