CVE-2025-7363VulnerabilityPublished 8 Jul 2025Updated 10 Jul 2025

CVE-2025-7363: Wikimedia Foundation Mediawiki – TitleIcon extension · XSS or 'Cross-site Scripting'

Affects Wikimedia Foundation Mediawiki – TitleIcon extensionSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium · fixed in 1.44.0 : update Wikimedia Foundation Mediawiki – TitleIcon extension when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.44.0, 1.43.2, 1.43.0 +3

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Wikimedia Foundation Mediawiki - TitleIcon extension	Affected >=1.39.0 <1.40.0 >=1.42.0 <1.43.0 >=1.43.0 <1.44.0 <1.39.13 <1.42.7 <1.43.2 =1.39.0 =1.39.1 =1.39.2 =1.39.3 =1.39.4 =1.39.5 =1.39.6 =1.39.7 =1.39.8 =1.39.9 =1.39.10 =1.39.11 =1.39.12 =1.42.0 =1.42.1 =1.42.2 =1.42.3 =1.42.4 =1.42.5 =1.42.6 =1.43.0 =1.43.1	Fixed in 1.40.0 1.43.0 1.44.0 1.39.13 1.42.7 1.43.2

AI-suggested

1. Immediate patching: Organizations should upgrade the TitleIcon extension to the fixed versions 1.39.13, 1.42.7, or 1.43.2 or later as soon as possible to eliminate the vulnerability. 2. Input validation and sanitization: Until patches are applied, implement additional input validation and sanitization on user inputs passed to the #titleicon_unicode parser function, potentially using Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting this function. 3. Restrict privileges: Limit the ability to use the #titleicon_unicode parser function to trusted users only, reducing the risk of malicious input injection. 4. Content Security Policy (CSP): Deploy strict CSP headers to restrict the execution of unauthorized scripts and mitigate the impact of potential XSS exploitation. 5. Monitoring and logging: Enable detailed logging of parser function usage and monitor for unusual activities or injection attempts. 6. User awareness: Educate users about the risks of interacting with untrusted links or content within the MediaWiki environment. 7. Incident response readiness: Prepare to respond to potential XSS exploitation incidents, including session invalidation and forensic analysis. These measures, combined with prompt patching, will reduce the risk and impact of exploitation.

Description

The TitleIcon extension for MediaWiki is vulnerable to stored XSS through the #titleicon_unicode parser function. User input passed to this function is wrapped in an HtmlArmor object without sanitization and rendered directly into the page header, allowing attackers to inject arbitrary JavaScript. This issue affects Mediawiki - TitleIcon extension: from 1.39.X before 1.39.13, from 1.42.X before 1.42.7, from 1.43.X before 1.43.2.

Impact

For European organizations using MediaWiki with the TitleIcon extension, this vulnerability poses a risk of client-side attacks that can compromise user sessions and data confidentiality. Organizations that rely on MediaWiki for internal documentation, knowledge bases, or public-facing wikis may face risks of unauthorized script execution leading to phishing, data leakage, or manipulation of displayed content. The requirement for attacker privileges and user interaction somewhat limits the attack surface; however, insider threats or compromised user accounts could exploit this vulnerability to escalate impact. The changed scope indicates that the vulnerability could affect other components or users beyond the initial target, increasing potential damage. Given MediaWiki's widespread use in academic institutions, government agencies, and enterprises across Europe, exploitation could disrupt operations or damage reputations. Additionally, since the vulnerability affects the page header, it could be used to inject scripts that affect all users visiting the affected pages, amplifying the impact. Although no known exploits are reported yet, the presence of stored XSS vulnerabilities historically attracts attackers due to their persistence and broad impact. Therefore, European organizations should consider this a significant risk, especially those with publicly accessible or widely used MediaWiki installations.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jul 2025, 21:39 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats