dbcve.org
Joomla\!Application · Joomla

CVE-2025-63082

MEDIUM · 6.1 CVSS v3.1 Published 2026-01-06
Fix available
A fix is available. Upgrade to 5.4.2 / 6.0.2 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 input filtering leads to an XSS vector in the HTML filter code related to data URLs in img tags.

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

This is a cross-site scripting (XSS) vulnerability in the HTML filter code. The filter fails to properly sanitize or validate data URLs embedded in img tags, allowing attackers to inject malicious JavaScript through crafted data URI schemes.

MitigationImplement proper input validation and sanitization for data URLs in img tags within the HTML filter, ensuring data URIs are either blocked or sanitized to prevent script execution.

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, < 5.4.2>= 6.0.0, < 6.0.2

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 your Joomla version
    Access the Joomla Administrator dashboard and navigate to System > Information, or check the libraries/cms/version.php file in your Joomla installation directory. Compare the installed version against the affected ranges: 4.0.0 to 5.4.1, or 6.0.0 to 6.0.1.
    Affected if The installed version falls within 4.0.0 <= version < 5.4.2 OR 6.0.0 <= version < 6.0.2
  2. Verify HTML filter is active
    Check if the Joomla HTML filter functionality is enabled in your content filtering settings. This is typically found in the Text Filter settings under the Article Manager or in Global Configuration under the Text Filters tab.
    Affected if The HTML filter is enabled and configured to allow img tags with data URI schemes in user-submitted content
  3. Inspect content for data URI img tags
    Review your site's published content, comments, or user-generated content areas for img tags using data URI schemes (data:image/...). Use a database query or content audit to find instances of img tags containing 'data:' in the src attribute.
    Affected if Content contains img tags with data: URI sources that could contain malicious JavaScript payloads
  4. Check input filtering configuration
    Examine the text filter configuration files or settings in Joomla that control how HTML is sanitized. Look for settings related to data URL handling in the filter pipeline.
    Affected if The filter configuration allows data URIs in img tags without proper sanitization or explicitly permits data: protocol in img src attributes

You are affected if your Joomla installation version is between 4.0.0 and 5.4.1 or between 6.0.0 and 6.0.1 AND the HTML filter is enabled with data URIs permitted in img tags.

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.2 / 6.0.2 or later
Fixed in 5.4.26.0.2
Interim mitigation

Implement proper input validation and sanitization for data URLs in img tags within the HTML filter, ensuring data URIs are either blocked or sanitized to prevent script execution.

Recommended fix High confidence

Joomla! 5.4.2 or later / Joomla! 6.0.2 or later

  1. 1. Backup your Joomla! database and files before performing any upgrade
  2. 2. Download the latest Joomla! 5.4.x or 6.0.x release from the official Joomla! downloads page (downloads.joomla.org)
  3. 3. Install the update through the Joomla! Administrator dashboard via Components > Joomla! Update, or manually extract the update package over your existing installation
  4. 4. Clear any Joomla! cache (System > Clear Cache) and any server-side caching (CDN, Varnish, etc.)
  5. 5. Verify the upgrade was successful by checking the administrator dashboard for the new version number
  6. 6. Test that the HTML filter functions correctly, particularly any components using data URLs in img tags
Caveat Major version upgrades (e.g., 5.x to 6.x) may require template/component compatibility review; review Joomla! migration guides before jumping across major versions

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

Fix this in Joomla\! Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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