CVE-2026-22707
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStrapi is an open source headless content management system. 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 in version 5.33.3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Strapi Upload plugin's Content API endpoints (uploadFiles, replaceFile) bypassed the configured MIME type restrictions (allowedTypes/deniedTypes) and magic-byte detection that were correctly enforced in the admin panel. The Content API controllers directly called the upload service without invoking the enforceUploadSecurity check, allowing authenticated users with upload permissions to upload disallowed file types like HTML and SVG that could execute JavaScript in the admin's origin.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.33.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Strapi versionCheck the package.json file in your Strapi project for the @strapi/strapi version, or run 'npm list @strapi/strapi' in your project directoryAffected if The version is lower than 5.33.3 (e.g., 5.0.0 through 5.33.2)
-
Confirm Content API upload endpoints are exposedVerify that your Strapi instance has the Upload plugin enabled and that Content API endpoints (/api/upload-files, /api/upload-files/:id) are accessible to authenticated users with upload permissionsAffected if The Content API upload endpoints are accessible and the Strapi version is below 5.33.3
-
Check upload MIME type restrictions configurationExamine your Strapi configuration (typically in config/plugins.js or config/upload.js) for allowedTypes or deniedTypes settings that restrict file uploadsAffected if MIME type restrictions (allowedTypes/deniedTypes) are configured but the Strapi version is below 5.33.3, indicating the bypass may be exploitable
-
Verify enforceUploadSecurity is invoked on Content API uploadsReview the source code of your Content API upload controller (typically in node_modules/@strapi/plugin-upload/strapi-server.js or the compiled controller) to confirm whether the enforceUploadSecurity check is called before processing uploadsAffected if The enforceUploadSecurity function is NOT called in the Content API upload handler and the version is below 5.33.3
You are affected if your Strapi version is below 5.33.3, the Content API upload endpoints are enabled, and the enforceUploadSecurity check is not being invoked by those endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.33.3
Upgrade Strapi to version 5.33.3 or later, which introduces a shared prepareUploadRequest helper ensuring consistent MIME type enforcement across all upload entry points.
5.33.3
- Upgrade Strapi to version 5.33.3 or later by updating the package.json dependency to "@strapi/strapi": "^5.33.3" and running the package manager install command (e.g., npm install or yarn install)
- Verify the upgrade was successful by checking that the Strapi server starts without errors
- Test that the Content API upload endpoints now correctly enforce the MIME type restrictions configured via plugin.upload.security.allowedTypes and plugin.upload.security.deniedTypes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22707 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22707 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data