dbcve.org
Joomla\!Application · Joomla

CVE-2026-30895

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-26
Fix available
A fix is available. Upgrade to 5.4.6 / 6.1.1 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
Lack of output escaping leads to a XSS vector in the readmore links for com_content.

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

A Cross-Site Scripting (XSS) vulnerability exists in Joomla's com_content component where readmore links fail to properly escape output. This allows attackers to inject malicious scripts via the readmore link functionality, which could execute in the context of other users viewing the content.

MitigationApply the appropriate Joomla security patch for this vulnerability. Until a patch is available, implement output encoding on all user-supplied data in readmore links and consider using a WAF to filter malicious requests.

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.6>= 6.0.0, < 6.1.1

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 the installed Joomla version
    Access the Joomla administrator dashboard and navigate to System > System Information, or check the libraries/cms.php file for the VERSION constant, or inspect the libraries/src/Version.php file
    Affected if The installed version is >= 3.0.0 and < 5.4.6, OR >= 6.0.0 and < 6.1.1
  2. Confirm com_content component is present
    Check that the /components/com_content directory exists in the Joomla installation, or verify the component is listed in the #__extensions table with type=component and element=com_content
    Affected if The com_content component is installed (this is a default component in Joomla)
  3. Verify readmore link functionality is in use
    Review content articles in the administrator panel under Content > Articles, or query the #__content table for entries with the readmore flag set (typically indicated by the `attribs` or `params` fields containing readmore configuration)
    Affected if Any article or content item uses the readmore feature, which is common in Joomla content publishing

You are affected if your Joomla version falls within the vulnerable ranges AND the com_content component with readmore functionality is in use on your 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 5.4.6 / 6.1.1 or later
Fixed in 5.4.66.1.1
Interim mitigation

Apply the appropriate Joomla security patch for this vulnerability. Until a patch is available, implement output encoding on all user-supplied data in readmore links and consider using a WAF to filter malicious requests.

Recommended fix High confidence

Joomla! 5.4.6 or Joomla! 6.1.1 (depending on your current major version branch)

  1. 1. Backup your Joomla! database and files before performing any update
  2. 2. Navigate to the Joomla! official download page at joomla.org
  3. 3. Download Joomla! 5.4.6 (if running 5.x) or Joomla! 6.1.1 (if running 6.x)
  4. 4. Install the update via Components > Joomla Update in the admin panel, or manually replace core files
  5. 5. Clear any Joomla! caches after the upgrade completes
  6. 6. Verify the readmore functionality in com_content works correctly and no XSS payload executes
Caveat Upgrading within same major version (e.g., 5.3.x to 5.4.6) typically has minimal breaking changes; however, cross-major version upgrades (e.g., 3.x to 5.x) may require compatibility checks for extensions and templates

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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