MediaWiki up to 1.31.10/1.32.x/1.34.3 Message Content mw.message.parse Parameter cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MediaWiki up to 1.31.10/1.32.x/1.34.3. It has been classified as problematic. Affected by this vulnerability is the function mw.message.parse of the component Message Content Handler. The manipulation as part of Parameter leads to cross site scripting.
This vulnerability is documented as CVE-2020-25828. The attack can be initiated remotely. There is not any exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability was found in MediaWiki up to 1.31.10/1.32.x/1.34.3 (Content Management System) and classified as problematic. This issue affects the function mw.message.parse of the component Message Content Handler. The manipulation as part of a Parameter leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. Impacted is integrity. The summary by CVE is:
An issue was discovered in MediaWiki before 1.31.10 and 1.32.x through 1.34.x before 1.34.4. The non-jqueryMsg version of mw.message().parse() doesn't escape HTML. This affects both message contents (which are generally safe) and the parameters (which can be based on user input). (When jqueryMsg is loaded, it correctly accepts only whitelisted tags in message contents, and escapes all parameters. Situations with an unloaded jqueryMsg are rare in practice, but can for example occur for Special:SpecialPages on a wiki with no extensions installed.)
The weakness was released 09/27/2020 (Website). The advisory is shared at lists.wikimedia.org. The identification of this vulnerability is CVE-2020-25828 since 09/23/2020. The attack may be initiated remotely. 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.
Upgrading to version 1.31.11 or 1.34.4 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-162036, VDB-162037, VDB-162038 and VDB-162039. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 1.0
- 1.1
- 1.2
- 1.3
- 1.4
- 1.5
- 1.6
- 1.7
- 1.8
- 1.9
- 1.10
- 1.11
- 1.12
- 1.13
- 1.14
- 1.15
- 1.16
- 1.17
- 1.18
- 1.19
- 1.20
- 1.21
- 1.22
- 1.23
- 1.24
- 1.25
- 1.26
- 1.27
- 1.28
- 1.29
- 1.30
- 1.31
- 1.31.0
- 1.31.1
- 1.31.2
- 1.31.3
- 1.31.4
- 1.31.5
- 1.31.6
- 1.31.7
- 1.31.8
- 1.31.9
- 1.31.10
- 1.32
- 1.34.0
- 1.34.1
- 1.34.2
- 1.34.3
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-80 / CWE-74 / CWE-707
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: MediaWiki 1.31.11/1.34.4
Timeline
09/23/2020 🔍09/27/2020 🔍
09/28/2020 🔍
11/14/2020 🔍
Sources
Product: mediawiki.orgAdvisory: lists.wikimedia.org
Status: Not defined
Confirmation: 🔍
CVE: CVE-2020-25828 (🔍)
GCVE (CVE): GCVE-0-2020-25828
GCVE (VulDB): GCVE-100-162041
See also: 🔍
Entry
Created: 09/28/2020 07:22Updated: 11/14/2020 18:08
Changes: 09/28/2020 07:22 (40), 09/28/2020 07:27 (4), 11/13/2020 07:58 (3), 11/14/2020 18:06 (1), 11/14/2020 18:08 (8)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.