dbcve.org
Joomla\!Application · Joomla

CVE-2022-23800

MEDIUM · 6.1 CVSS v3.1 Published 2022-03-30
Fix available
A fix is available. Upgrade to after 4.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
An issue was discovered in Joomla! 4.0.0 through 4.1.0. Inadequate content filtering leads to XSS vulnerabilities in various components.

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 confidence

Inadequate content filtering in Joomla! CMS versions 4.0.0 through 4.1.0 allows cross-site scripting (XSS) attacks in various components due to improper sanitization of user-supplied content.

MitigationUpgrade Joomla! to version 4.1.1 or later which contains the patched content filtering. If immediate patching is not possible, disable or restrict user-generated content features as a temporary workaround.

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
Affected:>= 4.0.0, <= 4.1.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Joomla installation and version
    Locate the version.php file in the Joomla root directory (typically /libraries/src/Version.php or check the administrator/about.php page). Alternatively, access the Joomla administrator dashboard and navigate to System > Information to view the installed version.
    Affected if The installed version is 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.0.8, 4.0.9, 4.0.10, 4.1.0 (any version from 4.0.0 through 4.1.0 inclusive).
  2. Verify user-generated content components are enabled
    In the Joomla administrator panel, go to Content > Site Templates or System > Install > Discover to list all installed components. Check if components that accept user input such as contact forms (com_contact), user registration (com_users), comments, or third-party content submission extensions are installed and published.
    Affected if Any component that accepts and displays user-supplied content is enabled and accessible to site visitors or registered users.
  3. Inspect content filtering configuration
    Access the global configuration settings in Joomla administrator (System > Global Configuration). Review the text filter settings under the Text Filters tab for each user group. Examine whether strict filtering is applied or if HTML tags are permitted that could enable XSS payloads.
    Affected if Text filters are set to permit HTML tags or are set to 'No Filtering' for user groups that can submit content, allowing injection of malicious scripts.

A user is affected if Joomla CMS version 4.0.0 through 4.1.0 is installed AND any component accepting user-generated content (contact forms, user registration, comments, etc.) is enabled on the site.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 4.1.0
Interim mitigation

Upgrade Joomla! to version 4.1.1 or later which contains the patched content filtering. If immediate patching is not possible, disable or restrict user-generated content features as a temporary workaround.

Recommended fix High confidence

Joomla! 4.1.1

  1. Backup your Joomla! 4.x website before performing any upgrade
  2. Download Joomla! 4.1.1 from the official Joomla! Downloads page (https://downloads.joomla.org)
  3. Extract the upgrade package to your local system
  4. Upload the files to your server, overwriting existing Joomla core files, or use the Joomla! Update component within the administrator panel
  5. Navigate to System > Global Configuration > Clear Cache to ensure cached content is refreshed
  6. Verify that the frontend and backend are functioning correctly
Caveat Review the Joomla! 4.1.1 release notes for any breaking changes to third-party extensions or templates that may need updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Joomla\! Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23800 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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