CVSS VectorNVD
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Lifecycle Timeline
5Blast Radius
ecosystem impact- 2 npm packages depend on @strapi/upload (1 direct, 1 indirect)
Ecosystem-wide dependent count for version 5.33.3.
DescriptionNVD
Summary of CVE-2026-22707 Vulnerability Details
- CVE: CVE-2026-22707
- CVSS v3.1 Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N(5.3 - Medium) - Affected Versions:
@strapi/upload<=5.33.2 - How to Patch: Immediately update your Strapi to >=5.33.3
Description of CVE-2026-22707
In Strapi versions prior to 5.33.3, the Upload plugin's Content API endpoints did not enforce the administrator-configured MIME type restrictions (plugin.upload.security.allowedTypes and deniedTypes). The same restrictions were correctly enforced on the Admin Panel upload path.
The upload plugin's enforceUploadSecurity security check was invoked in the admin upload controller but was missing from the Content API controller. The Content API handlers uploadFiles and replaceFile (and the upload wrapper that dispatches to them) called the underlying upload service directly, bypassing both the magic-byte MIME detection and the configured allow/deny lists.
An authenticated user with the Content API upload permission could therefore upload file types the administrator had explicitly disallowed, including HTML and SVG content. In deployments serving uploaded files from the same origin as the admin panel (default), an attacker could upload an HTML or SVG file that, when opened directly by an admin, executed JavaScript in the admin origin, enabling admin-session hijack and authenticated administrative actions against the admin API.
The patch introduces a shared prepareUploadRequest helper that wraps enforceUploadSecurity and is called from both the Content API and admin upload controllers, ensuring identical security policy enforcement on every upload entry point.
IoC's for CVE-2026-22707
Indicators that an instance running an unpatched version may have been exploited:
- Files in
/uploads/with extensions outside the configured allow-list, particularly.html,.htm,.svg,.js,.mjs,.xml, or.xhtml. Filesystem regex:\.(html?|svg|m?js|x?html|xml)$ - Successful 201 responses from
POST /api/uploadwhere the uploaded file's MIME or extension is outside the configuredallowedTypes - Server access logs showing non-administrator users uploading files with executable web content types. Content-Type regex:
text/html|application/javascript|image/svg\+xml - Admin browsing logs (X-Forwarded-For, User-Agent) opening files under
/uploads/*.htmlor/uploads/*.svgshortly before unexpected administrative actions (user creation, role changes, permission modifications)
References
- CWE-693: Protection Mechanism Failure
- CWE-434: Unrestricted Upload of File with Dangerous Type
- OWASP: Unrestricted File Upload
- Strapi 5 Documentation - Media Library
- Strapi Security Policy
Credits
Reported independently by:
- @kaminuma (initial report, 2026-01-09)
- @arkmarta (concurrent report, 2026-01-13 - originally filed as GHSA-r7hp-523c-r8wr, closed as duplicate)
AnalysisAI
Strapi Upload plugin versions 5.33.2 and earlier bypass administrator-configured MIME type restrictions on Content API upload endpoints, allowing authenticated users to upload executable file types (HTML, SVG, JavaScript) that the admin explicitly denies. When uploaded files are served from the same origin as the admin panel (default configuration), an attacker can upload malicious HTML or SVG that executes JavaScript in the admin's browser session, enabling session hijacking and unauthorized administrative actions. …
Sign in for full analysis, threat intelligence, and remediation guidance.
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30361
GHSA-pcw7-5633-82vv