TitleIcon Extension up to 1.39.12/1.42.6/1.43.1 on MediaWiki titleicon_unicode Parser cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TitleIcon Extension up to 1.39.12/1.42.6/1.43.1 on MediaWiki. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component titleicon_unicode Parser. Performing a manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2025-7363. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, was found in TitleIcon Extension up to 1.39.12/1.42.6/1.43.1 on MediaWiki. This affects an unknown code block of the component titleicon_unicode Parser. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. 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. This is going to have an impact on integrity. The summary by CVE is:
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.
It is possible to read the advisory at phabricator.wikimedia.org. This vulnerability is uniquely identified as CVE-2025-7363 since 07/08/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
Upgrading to version 1.39.13, 1.42.7 or 1.43.2 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: TitleIcon Extension 1.39.13/1.42.7/1.43.2
Timeline
07/08/2025 Advisory disclosed07/08/2025 CVE reserved
07/08/2025 VulDB entry created
07/08/2025 VulDB entry last update
Sources
Advisory: phabricator.wikimedia.orgStatus: Confirmed
CVE: CVE-2025-7363 (🔒)
GCVE (CVE): GCVE-0-2025-7363
GCVE (VulDB): GCVE-100-315579
Entry
Created: 07/08/2025 21:47Changes: 07/08/2025 21:47 (55)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.