dbcve.org
Joomla\!Application · Joomla

CVE-2026-25901

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 multilingual associations component.

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 the multilingual associations component due to insufficient output escaping. User-supplied data rendered in this component is not properly sanitized before display, allowing attackers to inject malicious scripts that execute in victims' browsers.

MitigationApply context-appropriate output encoding/escaping to all user-controlled data displayed in the multilingual associations component, following OWASP XSS prevention guidelines.

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. Check installed Joomla version
    Locate the version file at /libraries/src/Version.php or access the administrator dashboard under System > System Information > PHP Settings to view the Joomla version string
    Affected if The version falls within 3.0.0 to 5.4.5 or 6.0.0 to 6.1.0
  2. Verify multilingual associations component is present
    Check if the com_associations directory exists in /administrator/components/ and examine whether the component is listed in the #__extensions database table with enabled=1
    Affected if The multilingual associations component is installed and enabled in the system
  3. Inspect multilingual association data entries
    Query the #__associations table in the database to review stored association records, particularly entries involving language-specific content that may contain unsanitized input
    Affected if Association records exist that contain user-supplied content rendered without output encoding
  4. Check for rendered output in language switcher or association views
    Expose the multilingual associations component by visiting the language switcher module or the associations list view in the backend (Components > Multilingual Associations) and inspect the page source for unescaped characters
    Affected if Rendered HTML displays raw characters from association data without proper HTML entity encoding

You are affected if your Joomla version is 3.0.0-5.4.5 or 6.0.0-6.1.0 AND the multilingual associations component is enabled with association data containing content rendered without output escaping.

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 context-appropriate output encoding/escaping to all user-controlled data displayed in the multilingual associations component, following OWASP XSS prevention guidelines.

Recommended fix High confidence

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

  1. 1. Back up your Joomla website including files and database
  2. 2. For Joomla 5.x sites: upgrade to version 5.4.6 or later
  3. 3. For Joomla 6.x sites: upgrade to version 6.1.1 or later
  4. 4. Use Joomla's built-in Update component (Components > Joomla! Update) or manually upload the updated Joomla packages
  5. 5. Clear any caching systems after upgrading
  6. 6. Verify the update was successful by checking the admin panel and confirming the version number
Caveat Review Joomla release notes for breaking changes between your current version and the target version, especially if upgrading across major version branches

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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