CVE-2026-108114 — Strapi 5.47.0 through 5.57.0 Improper Authorization via Admin API Token Field Permissions
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
- Technical severity (medium)+3
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Strapi Strapi).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.3 | CVSS 4.0 | Medium | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 5.3 | CVSS 4.0 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 4.3 | CVSS 3.1 | Medium | 2.8 | 1.4 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 4.3 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
| 4.3 | CVSS 3.1 | Medium | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 16, 2026 · 4 reading(s) · max 0.20%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Awaiting Analysis
- SSVC assessment updated
- Affected products added · strapi/strapi
- Record published
- CVSS changed · 4.3
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
6 on the record
- www.vulncheck.com/advisories/strapi-5.47.0-through-5.57.0-improper-authorization-via-ad
- github.com/strapi/strapi
- github.com/advisories/GHSA-wmch-qg2f-grh3
- github.com/strapi/strapi/blob/v5.57.0/packages/core/admin/server/src/services/ap
- nvd.nist.gov/vuln/detail/CVE-2026-108114
- hackmd.io/@haind/strapi-admin-token-field-ceiling
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-90561 Strapi 4.x through 4.26.2 and 5.x before 5.48.1 Stored XSS via WYSIWYG Sep 13, 2026
- Medium CVE-2026-57997 Strapi users-permissions - JWT Algorithm Confusion via Missing Algorithm Configuration Jun 29, 2026
- High CVE-2026-27886 Strapi may leak sensitive data via relational filtering due to lack of query sanitization May 14, 2026
- Medium CVE-2026-22706 Strapi: Password Reset Does Not Revoke Existing Refresh Sessions May 14, 2026
- Medium CVE-2026-22707 Strapi Upload Plugin MIME Validation Bypass via Content API May 14, 2026
- Medium CVE-2025-64526 Strapi has a rate limit bypass on users-permissions plugin via attacker-controlled email keying May 14, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-108114 is "Strapi 5.47.0 through 5.57.0 Improper Authorization via Admin API Token Field Permissions", rated Medium. It affects Strapi (Strapi); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 0.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.