dbcve.org
Joomla\!Application · Joomla

CVE-2026-48950

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-07
Fix available
A fix is available. Upgrade to 5.4.7 / 6.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 escaping leads to an XSS vulnerability in the file management view of com_templates.

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 stored Cross-Site Scripting (XSS) vulnerability exists in Joomla's com_templates component file management view due to improper input escaping. User-supplied data in the template file management interface is rendered without proper HTML encoding, allowing injection of malicious scripts that execute in the context of other users' browsers.

MitigationApply proper output escaping using Joomla's JHtml::_('string.escape') or equivalent encoding functions to all user-supplied data rendered in the template file management view before display.

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.7>= 6.0.0, < 6.1.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 Joomla version
    Locate and read the version.php file in your Joomla installation (typically in /libraries/src/Version.php or check the administrator manifest.xml). Compare the version number against the affected ranges: < 5.4.7 (for 4.x/5.x branches) or < 6.1.2 (for 6.x branch).
    Affected if Installed version falls within 4.0.0 to 5.4.6, or 6.0.0 to 6.1.1
  2. Verify com_templates component is accessible
    Log into the Joomla administrator panel and navigate to System > Site Templates (or access index.php?option=com_templates). Confirm the component loads without errors.
    Affected if com_templates component is enabled and accessible to users with template management permissions
  3. Inspect template file management view for unescaped output
    Examine the PHP files in the com_templates view responsible for file management (typically in /components/com_templates/tmpl/ or /administrator/components/com_templates/tmpl/). Look for instances where user-supplied data such as file names, paths, or template parameters are rendered using echo or print statements without passing through HTML escaping functions like htmlspecialchars(), JHtml::_('string.escape'), or similar encoding methods.
    Affected if User-supplied data in the template file management view is rendered without HTML encoding (e.g., no htmlspecialchars, JHtml::_('string.escape'), or equivalent escaping function is applied to file names, paths, or user inputs before display)
  4. Test for stored XSS in template file naming
    Create or rename a template file using the file management interface with a filename containing a script tag payload (e.g., <filename>test<img src=x onerror=alert(1)>.png</filename>). Save and then view the file list in the template manager to see if the script executes or renders as raw HTML.
    Affected if The injected script tag or HTML markup renders unescaped in the browser when viewing the template file list

Your environment is affected if you run Joomla versions 4.0.0-5.4.6 or 6.0.0-6.1.1 AND the com_templates file management view renders user-supplied template filenames or paths without proper HTML encoding.

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.7 / 6.1.2 or later
Fixed in 5.4.76.1.2
Interim mitigation

Apply proper output escaping using Joomla's JHtml::_('string.escape') or equivalent encoding functions to all user-supplied data rendered in the template file management view before display.

Recommended fix High confidence

Joomla! 5.4.7 or Joomla! 6.1.2 (depending on your current major version branch)

  1. 1. Create a complete backup of the Joomla! site including database and files
  2. 2. Identify the current Joomla! version (either 5.x or 6.x branch)
  3. 3. If using Joomla! 5.x (version >= 4.0.0 and < 5.4.7), upgrade to Joomla! 5.4.7
  4. 4. If using Joomla! 6.x (version >= 6.0.0 and < 6.1.2), upgrade to Joomla! 6.1.2
  5. 5. Perform the upgrade using Joomla!'s built-in update component or manual upgrade package
  6. 6. Clear any caching systems (Joomla cache, CDN cache, browser cache)
  7. 7. Verify the upgrade was successful by checking the admin panel footer shows the new version
  8. 8. Test the Templates component (com_templates) file management view to confirm the XSS vulnerability is resolved
Caveat Joomla! 6.x may have breaking changes compared to 5.x; review Joomla upgrade documentation for extension compatibility 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
  • 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-48950 — 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-48950 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