MediaWiki up to 1.35.8/1.38.4/1.39.0 SpecialMobileHistory denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in MediaWiki up to 1.35.8/1.38.4/1.39.0. This affects an unknown part of the file SpecialMobileHistory. The manipulation leads to denial of service. This vulnerability is traded as CVE-2023-22909. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in MediaWiki up to 1.35.8/1.38.4/1.39.0 (Content Management System) and classified as problematic. This issue affects some unknown processing of the file SpecialMobileHistory. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
An issue was discovered in MediaWiki before 1.35.9, 1.36.x through 1.38.x before 1.38.5, and 1.39.x before 1.39.1. SpecialMobileHistory allows remote attackers to cause a denial of service because database queries are slow.
The weakness was shared 01/10/2023. The advisory is shared at phabricator.wikimedia.org. The identification of this vulnerability is CVE-2023-22909 since 01/10/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 1.35.9, 1.38.5 or 1.39.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-27011). 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.32
- 1.33
- 1.34
- 1.35
- 1.35.0
- 1.35.1
- 1.35.2
- 1.35.3
- 1.35.4
- 1.35.5
- 1.35.6
- 1.35.7
- 1.35.8
- 1.36
- 1.37
- 1.38
- 1.38.0
- 1.38.1
- 1.38.2
- 1.38.3
- 1.38.4
- 1.39.0
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: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
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: Denial of serviceCWE: CWE-404
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.35.9/1.38.5/1.39.1
Timeline
01/10/2023 🔍01/10/2023 🔍
01/10/2023 🔍
10/04/2025 🔍
Sources
Product: mediawiki.orgAdvisory: FEDORA-2023-30a7a812f0
Status: Confirmed
CVE: CVE-2023-22909 (🔍)
GCVE (CVE): GCVE-0-2023-22909
GCVE (VulDB): GCVE-100-217769
EUVD: 🔍
Entry
Created: 01/10/2023 14:30Updated: 10/04/2025 23:54
Changes: 01/10/2023 14:30 (40), 01/31/2023 07:48 (1), 01/31/2023 07:53 (11), 04/07/2025 21:52 (16), 10/04/2025 23:54 (1)
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.