dbcve.org
Joomla\!Application · Joomla

CVE-2026-21632

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 5.4.4 / 6.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Lack of output escaping for article titles leads to XSS vectors in various locations.

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

Cross-site scripting (XSS) vulnerability in article titles due to insufficient output escaping. User-supplied article title content is rendered without proper encoding, allowing injection of malicious scripts that execute in victim browsers.

MitigationImplement context-appropriate output encoding/escaping for all article title display locations across the application, and validate input on submission.

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:>= 3.0.0, < 5.4.4>= 6.0.0, < 6.0.4

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Joomla version
    Locate the version information in your Joomla installation (typically found in the administrator dashboard under System > System Information, or in a version.php file within the installation directory)
    Affected if The version is 3.0.0 through 5.4.3, or 6.0.0 through 6.0.3 (versions below the fixed releases 5.4.4 and 6.0.4)
  2. Confirm article component is active
    Access the Joomla administrator panel and verify that the Articles component is enabled and accessible (Components > Articles)
    Affected if The Articles component is present and functional in your installation
  3. Determine if custom article titles can be created
    Create a new test article or inspect existing articles to confirm that custom title text can be entered by users with content creation privileges
    Affected if Users with article creation or editing permissions can input custom title content
  4. Inspect article title display locations
    View published articles on your site (including category blog layouts, featured articles views, and article detail pages) to observe how article titles are rendered in the browser
    Affected if Article titles are displayed on the site frontend without visible HTML entity encoding (e.g., script tags appear as literal text when injected in the title rather than being rendered as HTML)

You are affected if your Joomla version falls within 3.0.0 to 5.4.3 or 6.0.0 to 6.0.3 and article titles are displayed on your site without proper HTML escaping of user-supplied content.

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 5.4.4 / 6.0.4 or later
Fixed in 5.4.46.0.4
Interim mitigation

Implement context-appropriate output encoding/escaping for all article title display locations across the application, and validate input on submission.

Recommended fix High confidence

Joomla! 5.4.4 or Joomla! 6.0.4 depending on your current branch

  1. 1. Back up your Joomla! database and files before proceeding with any upgrade.
  2. 2. For Joomla! 5.x sites: Navigate to Components > Joomla! Update in the admin dashboard and update to version 5.4.4.
  3. 3. For Joomla! 6.x sites: Navigate to Components > Joomla! Update in the admin dashboard and update to version 6.0.4.
  4. 4. For Joomla! 3.x sites: Plan migration to Joomla! 5.x or 6.x as Joomla 3.x is end-of-life; there is no official patch for Joomla 3.x.
  5. 5. After upgrading, verify that article titles render correctly and the XSS vulnerability is remediated by testing with a harmless script tag in an article title.
  6. 6. Clear any Joomla! caches (System > Clear Cache) to ensure the fix takes effect.
Caveat Joomla! 5.x to 5.4.4 is a patch update with minimal breaking changes; Joomla! 6.0.4 may have minor changes - review release notes before upgrading

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21632 — 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-2026-21632 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