Joomla\!Application · Joomla
CVE-2022-23801
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 · uneditedAn issue was discovered in Joomla! 4.0.0 through 4.1.0. Possible XSS atack vector through SVG embedding in com_media.
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 confidenceCross-site scripting (XSS) vulnerability in Joomla! 4.0.0 through 4.1.0 allows attackers to inject malicious scripts via SVG file uploads in the com_media component. SVG files can contain embedded JavaScript that executes when rendered in a user's browser.
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
Joomla\!Application
>= 4.0.0, <= 4.1.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.
-
Check Joomla versionNavigate to System > Information > Joomla! Information in the admin panel, or check the libraries/cms.php file for the VERSION constantAffected if Version is 4.0.0 through 4.1.0 (inclusive)
-
Verify com_media component is accessibleAccess /administrator/index.php?option=com_media in the browser or check the #__extensions table for com_media entry with enabled=1Affected if com_media component exists and is enabled
-
Check if media upload permissions allow SVGNavigate to Content > Media > Options in admin panel, or inspect the media configuration XML at /administrator/components/com_media/config.xmlAffected if SVG file extension or image/svg+xml MIME type is allowed in the accepted file types configuration
-
Identify users with media upload privilegesCheck Users > Manage in admin panel for users with core.create or plugin.edit.assigned permissions on the media category, or query the #__user_usergroup_map table joined with #__assets for media permissionsAffected if Any user account has permission to upload files to the media manager
Environment is affected if Joomla version is between 4.0.0 and 4.1.0 inclusive, the com_media component is enabled, and any user has upload permissions that permit SVG file 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 · scopedUpgrade Joomla! to version 4.1.1 or later, which contains the security fix for this vulnerability.
Joomla! 4.1.1 or later (latest stable 4.x release)
- 1. Back up your Joomla! database and files before making any changes.
- 2. Download Joomla! 4.1.1 or later from the official Joomla! download page (https://downloads.joomla.org/).
- 3. Use Joomla!'s built-in Joomla! Update component to install the update, or manually replace core files with the new version.
- 4. After upgrading, verify that the com_media component is functioning correctly and the SVG upload vector is now sanitized.
- 5. Clear any caching systems (Joomla cache, CDN cache, browser cache) to ensure the patched version is served.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23801 — 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-2022-23801 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