Wikimedia mediawiki-extensions-I18nTags Unlike Parser I18nTags_body.php cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Wikimedia mediawiki-extensions-I18nTags. This affects an unknown function of the file I18nTags_body.php of the component Unlike Parser. The manipulation leads to cross site scripting. This vulnerability is referenced as CVE-2018-25065. Remote exploitation of the attack is possible. No exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Wikimedia mediawiki-extensions-I18nTags (Content Management System) (the affected version is unknown) and classified as problematic. This issue affects an unknown code of the file I18nTags_body.php of the component Unlike Parser. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity.
The weakness was published 01/05/2023 as b4bc3cbbb099eab50cf2b544cf577116f1867b94. The advisory is shared at github.com. The identification of this vulnerability is CVE-2018-25065. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
By approaching the search of inurl:I18nTags_body.php it is possible to find vulnerable targets with Google Hacking.
Applying the patch b4bc3cbbb099eab50cf2b544cf577116f1867b94 is able to eliminate this problem. The bugfix is ready for download at github.com. The advisory contains the following remark:
Unlike parser functions, tag functions' output is unescaped by default.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CNA Base Score: 3.5
CNA Vector (VulDB): 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: b4bc3cbbb099eab50cf2b544cf577116f1867b94
Timeline
01/05/2023 🔍01/05/2023 🔍
01/05/2023 🔍
01/28/2023 🔍
Sources
Product: github.comAdvisory: b4bc3cbbb099eab50cf2b544cf577116f1867b94
Status: Confirmed
CVE: CVE-2018-25065 (🔍)
GCVE (CVE): GCVE-0-2018-25065
GCVE (VulDB): GCVE-100-217445
Entry
Created: 01/05/2023 10:22Updated: 01/28/2023 15:04
Changes: 01/05/2023 10:22 (43), 01/28/2023 14:59 (2), 01/28/2023 15:04 (28)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.