Joomla\!Application · Joomla
CVE-2022-23794
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! 3.0.0 through 3.10.6 & 4.0.0 through 4.1.0. Uploading a file name of an excess length causes the error. This error brings up the screen with the path of the source code of the web application.
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 confidenceA path disclosure vulnerability in Joomla! versions 3.0.0-3.10.6 and 4.0.0-4.1.0 allows attackers to discover the web application's internal source code path by uploading files with excessively long filenames, which triggers an error exposing the server's path structure.
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
>= 3.0.0, <= 3.10.6>= 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Identify Joomla! versionLog into the Joomla! administrator dashboard and navigate to System > System Information, or check the libraries/cms.php file for the VERSION constant.Affected if The installed version is 3.0.0-3.10.6 or 4.0.0-4.1.0
-
Verify file upload capability is accessibleCheck if the Media Manager component or any third-party extension with file upload functionality is accessible to users (logged in or anonymous).Affected if File upload functionality is enabled and accessible to the attacker.
-
Test for path disclosure via long filenameAttempt to upload a file through the Media Manager with a filename exceeding 256 characters (for example, a file named with a very long string plus extension). Observe the error message returned by the server.Affected if The error response displays the full server file system path (such as /var/www/html/ or C:\inetpub\).
You are affected if your Joomla! version falls within 3.0.0-3.10.6 or 4.0.0-4.1.0 AND file upload functionality is accessible and responds with full server path information when processing excessively long filenames.
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 3.10.7 or 4.1.1 or later to patch this vulnerability. As a temporary measure, implement input validation to restrict filename lengths on file upload functionality.
Joomla! 3.10.7+ or Joomla! 4.1.1+ (latest stable 4.x recommended)
- Upgrade Joomla! 3.x installations from version 3.10.6 to version 3.10.7 or later
- Upgrade Joomla! 4.x installations from version 4.1.0 to version 4.1.1 or later
- After upgrading, verify that error messages no longer expose source code file paths
- Ensure that the new version is properly installed and the Joomla! administration panel is accessible
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23794 — 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-23794 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