Wikimedia MediaWiki up to 1.27.5/1.30.1/1.31.1/1.32.1 cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Wikimedia MediaWiki up to 1.27.5/1.30.1/1.31.1/1.32.1. Affected by this vulnerability is an unknown functionality. The manipulation results in cross site scripting. This vulnerability is identified as CVE-2019-12471. The attack can be executed remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in Wikimedia MediaWiki up to 1.27.5/1.30.1/1.31.1/1.32.1 (Content Management System). Affected is an unknown function. 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. CVE summarizes:
Wikimedia MediaWiki 1.30.0 through 1.32.1 has XSS. Loading user JavaScript from a non-existent account allows anyone to create the account, and perform XSS on users loading that script. Fixed in 1.32.2, 1.31.2, 1.30.2 and 1.27.6.
The weakness was released 07/10/2019 as not defined mailinglist post (Bugtraq). The advisory is shared for download at seclists.org. This vulnerability is traded as CVE-2019-12471 since 05/30/2019. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1059.007.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 176919 (Debian Security Update for mediawiki (DSA 4460-1)).
Upgrading to version 1.27.6, 1.30.2, 1.31.2 or 1.32.2 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-137671, VDB-137672, VDB-137673 and VDB-137674. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
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
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: MediaWiki 1.27.6/1.30.2/1.31.2/1.32.2
Timeline
05/30/2019 🔍07/10/2019 🔍
07/11/2019 🔍
07/07/2024 🔍
Sources
Advisory: seclists.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-12471 (🔍)
GCVE (CVE): GCVE-0-2019-12471
GCVE (VulDB): GCVE-100-137676
See also: 🔍
Entry
Created: 07/11/2019 11:13Updated: 07/07/2024 20:44
Changes: 07/11/2019 11:13 (41), 07/03/2020 16:53 (18), 07/07/2024 20:44 (19)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.