CVE-2023-48701
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 · uneditedStatamic CMS is a Laravel and Git powered content management system (CMS). Prior to versions 3.4.15 an 4.36.0, HTML files crafted to look like images may be uploaded regardless of mime validation. This is only applicable on front-end forms using the "Forms" feature containing an assets field, or within the control panel which requires authentication. This issue has been patched on 3.4.15 and 4.36.0.
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 · moderate confidenceIn Statamic CMS prior to versions 3.4.15 and 4.36.0, the file upload validation can be bypassed, allowing HTML files disguised as images to be uploaded. This affects front-end forms using the 'Forms' feature with asset fields and authenticated control panel uploads. The uploaded HTML could be used for cross-site scripting (XSS) or other client-side attacks.
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< 3.4.15>= 4.0.0, < 4.36.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 installed Statamic versionCheck the composer.json file in your project root for the 'statamic/cms' package version, or run 'composer show statamic/cms' in your project directoryAffected if The installed version is less than 3.4.15, or greater than or equal to 4.0.0 but less than 4.36.0
-
Identify if Forms feature with asset fields is in useLook for form blueprints in resources/blueprints/ that contain asset fields, or check the control panel for form configurations that accept file uploadsAffected if You have form blueprints or configurations that include asset fields for file uploads
-
Inspect uploaded files for HTML content disguised as imagesSearch your assets directory (typically storage/app/public or a custom assets folder) for files with image extensions (.jpg, .png, .gif, .webp) that contain HTML markup. Use a command like 'file *.jpg' or examine file contents for '<html', '<script', or '<body' tagsAffected if You find files with image extensions that contain HTML/JavaScript code
-
Check control panel upload logs if availableReview Statamic activity logs or server access logs for recent file upload requests, particularly those targeting asset fields from the control panelAffected if You see recent uploads of files with image MIME types but unexpected file contents
You are affected if your Statamic version is below 3.4.15 or between 4.0.0 and 4.35.x inclusive, AND you use the Forms feature with asset fields OR allow authenticated control panel uploads.
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 · scoped3.4.154.36.0
Upgrade Statamic CMS to version 3.4.15 or 4.36.0 or later to receive the patch that properly validates file MIME types during upload.
3.4.15 (for 3.x) or 4.36.0 (for 4.x)
- If using Statamic 3.x, upgrade to version 3.4.15 or later
- If using Statamic 4.x, upgrade to version 4.36.0 or later
- Run composer update to apply the security patch
- Clear any cached configurations if applicable (php artisan cache:clear)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48701 — 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-2023-48701 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