Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker authenticates with high-privilege Joomla! admin account
-
DeliveryInject malicious script into MFA management view field
-
ExploitPayload stored server-side without sanitization
-
ExecutionVictim administrator passively views MFA management page
-
PersistStored XSS executes in victim browser context
-
ImpactSession token or credentials exfiltrated to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must hold a high-privileged Joomla! account (Super User or Administrator level), as confirmed by PR:H in the CVSS 4.0 vector - unauthenticated or low-privilege users cannot directly inject payloads into MFA management views. The Joomla! back-end MFA management interface must be accessible, which is the default configuration for affected versions (4.2.0-5.4.6, 6.0.0-6.1.1) with MFA enabled. A second administrator must passively load the compromised MFA management page for the XSS payload to execute (UI:P in CVSS 4.0). Exploitation is bounded by the requirement for a pre-existing high-privilege account; this rules out entirely external unauthenticated attackers and limits realistic threat actors to malicious insiders, compromised admin credentials, or multi-stage attack chains that first achieve admin-level access. No non-default configuration beyond standard Joomla! MFA being in use is required. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:L/E:U) presents a moderate risk profile with a decisive limiting factor: PR:H confirms that the attacker must already hold high-level administrative privileges to inject the malicious payload. This substantially constrains the realistic attacker population to insiders, compromised administrator accounts, or privilege-escalation chains. The supplemental E:U metric explicitly indicates no known exploitation, consistent with the absence of a CISA KEV listing and the lack of any identified POC. Despite the low CVSS 4.0 score of 5.9 reflecting these constraints, the impact metrics VC:H and VI:H are significant - once triggered via passive victim interaction (UI:P), the XSS can fully compromise the victim administrator's browser session, enabling session hijacking and unauthorized back-end actions. No EPSS data was provided in the available intelligence, so probability-based exploitation likelihood cannot be independently assessed. The net assessment is: this is a real but bounded risk, prioritized for organizations where Joomla! administrator account hygiene is uncertain or where insider-threat scenarios are a concern. |
| Exploit ScenarioDerived | An attacker who already holds a Super User or Administrator account on a Joomla! instance navigates to the MFA method management interface and injects a malicious JavaScript payload into an inadequately validated field - such as a method label or configuration parameter. The payload is persisted server-side. When a second administrator subsequently opens the MFA management view in the normal course of site administration, the stored script executes in their browser, silently exfiltrating their session cookie to an attacker-controlled endpoint and granting the attacker full back-end access as the victim. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 07, 2026
Cross-site scripting in Joomla! CMS multi-factor authentication management views allows a high-privileged attacker to inject persistent malicious scripts that execute in the browser of any administrator who subsequently views the MFA management interface. Affected versions span two major release lines: 4.2.0-5.4.6 and 6.0.0-6.1.1, representing a broad surface across both legacy and current deployments. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, successful exploitation yields high confidentiality and integrity impact against the victim administrator's browser session.
RemediationAI
Upgrade Joomla! CMS to the patched release identified in the vendor security advisory at https://developer.joomla.org/security-centre/1057-20260703-core-xss-in-mfa-method-management.html - the exact fixed version number is not specified in the available intelligence and must be confirmed directly from that advisory before deploying. As an interim compensating control, restrict back-end access to the MFA method management interface to only the minimum set of trusted Super User accounts using Joomla!'s Access Control List (ACL); note that ACL misconfiguration carries a risk of locking out legitimate administrators, so changes should be tested in a non-production environment first. Additionally, enforcing multi-factor authentication on all Joomla! administrator accounts reduces the risk that a stolen session token from this XSS can be reused without a second factor.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected product is Joomla! CMS (CPE: cpe:2.3:a:joomla!_project:joomla!_cms), a widely-deployed PHP-based open-source content management system. The vulnerable component is the MFA (multi-factor authentication) method management interface in the Joomla! administrator back-end, introduced with Joomla! 4.2.0. CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting) identifies the root cause: user-supplied input submitted through MFA management views is insufficiently validated and/or not properly output-encoded before being rendered into HTML, allowing injected script content to be stored and later executed in other users' browser sessions. Because the MFA subsystem handles sensitive configuration data (second-factor method settings, labels, parameters), attacker-controlled values in this surface can persist and execute in privileged administrative contexts.
Know when Joomla Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:U
PR:H reflects required high-privilege injection; S:C because XSS executes in victim's browser context; C:L/I:L for session theft and page manipulation; no availability impact.
Primary rating from Vendor (Joomla).
CVSS VectorVendor: Joomla
DescriptionCVE.org
Lack of validation leads to an XSS vulnerability in the MFA management views.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Joomla Cms
View allImproper access control in Joomla! CMS webservice endpoints allows unauthorized attackers to bypass authentication and a
Transport encryption downgrade in Joomla! CMS password and username reset workflows causes reset links to be generated w
Unrestricted SHTML file upload in Joomla! CMS affects all versions from 1.0.0 through 5.4.7 and 6.0.0 through 6.1.2, imp
Server-side request forgery (SSRF) in Joomla CMS versions 4.0.0-5.4.8 and 6.0.0-6.1.3 allows an authenticated, high-priv
Path traversal (Zip Slip) in Joomla 6.1.1's com_joomlaupdate component enables persistent remote code execution when a S
Arbitrary file deletion in Joomla! CMS com_joomlaupdate component via the autoupdate server mechanism allows remote atta
Authorization bypass in Joomla CMS com_config webservice endpoints allows authenticated attackers with high privileges t
Inconsistent access control enforcement in Joomla! CMS REST API webservice endpoints allows authenticated users with ins
MFA bypass in Joomla! CMS 4.0.0 through 5.4.8 and 6.0.0 through 6.1.3 allows an attacker who can drive the login flow to
Multi-factor authentication bypass in Joomla! CMS versions 4.0.0 through 5.4.7 and 6.0.0 through 6.1.2 allows remote att
Authentication bypass in Joomla! CMS 4.0.0-5.4.5 and 6.0.0-6.1.0 allows remote attackers to circumvent multi-factor auth
Two-factor authentication bypass in Joomla! CMS versions 4.0.0-5.4.5 and 6.0.0-6.1.0 allows remote attackers to circumve
EUVD-2026-42060
GHSA-7vw9-q236-92vj
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB