CVE-2026-108114

Strapi 5.47.0 through 5.57.0 Improper Authorization via Admin API Token Field Permissions

Published Oct 10, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Strapi 5.47.0 through 5.57.0 contains an improper authorization vulnerability that allows admin API tokens to retain all-field Content Manager access after the owner's role is field-restricted. Because reconcileTokenPermissionsToUserCeiling ignores token permissions with omitted or null fields, token holders can keep reading content fields an administrator removed from the role.

Analysis

AI-generated

Technical impact

Strapi versions 5.47.0 through 5.57.0 contain an authorization flaw that allows an admin API token to retain access to all content fields even after the owning role has had those fields revoked. The bug stems from the token permission reconciliation logic that ignores omitted or null field entries, enabling the token holder to read fields an administrator has explicitly removed from their role. This exposes sensitive data, potentially leading to confidentiality violations without the need for elevated privileges.

Affected Systems

The affected product is Strapi, specifically the open‑source CMS released under the Strapi brand. All installations running any release from 5.47.0 up to and including 5.57.0 are vulnerable. Versions prior to 5.47.0 and post‑5.57.0 are not affected according to the CNA data.

Risk and Exploitability

The CVSS score of 5.3 indicates a moderate impact, and the vulnerability is not listed in the CISA KEV catalog. EPSS data is not currently available, so the likelihood of exploitation remains unknown. The likely attack vector is that a user who already possesses or can acquire an admin API token (for example, through credential compromise or misuse of existing tokens) can exploit the flaw to read data fields that should be blocked by role restrictions. Because the flaw operates entirely within the authenticated token scope, no additional privileges are required beyond the pre‑existing token rights.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Strapi to a version released after 557.0 that addresses the token field permission flaw.
  • If upgrading immediately is not feasible, revoke all existing admin API tokens and issue new ones only for roles that require full field access, ensuring field restrictions are enforced.
  • Review and tighten CMS content‑manager role permissions, removing any accidental field allowances that could be leveraged by compromised tokens.

Generated by OpenCVE AI on October 10, 2026 at 15:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Strapi
Strapi strapi
Vendors & Products Strapi
Strapi strapi
Type Values Removed Values Added
Description Strapi 5.47.0 through 5.57.0 contains an improper authorization vulnerability that allows admin API tokens to retain all-field Content Manager access after the owner's role is field-restricted. Because reconcileTokenPermissionsToUserCeiling ignores token permissions with omitted or null fields, token holders can keep reading content fields an administrator removed from the role.
Title Strapi 5.47.0 through 5.57.0 Improper Authorization via Admin API Token Field Permissions
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 14, 2026, 2:18 AM
Reserved
Oct 9, 2026, 1:44 PM
Status
Awaiting Analysis
Published
Oct 10, 2026, 3:16 PM
Modified
Oct 16, 2026, 7:15 PM