AbuseFilter Extension up to 1.39.12/1.42.6/1.43.1 on Mediawiki insufficient logging
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in AbuseFilter Extension up to 1.39.12/1.42.6/1.43.1 on Mediawiki. The affected element is an unknown function. The manipulation leads to insufficient logging. This vulnerability is listed as CVE-2025-53498. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in AbuseFilter Extension up to 1.39.12/1.42.6/1.43.1 on Mediawiki. It has been rated as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a insufficient logging vulnerability. Using CWE to declare the problem leads to CWE-778. When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it. Impacted is integrity. The summary by CVE is:
: Insufficient Logging vulnerability in Wikimedia Foundation Mediawiki - AbuseFilter Extension allows Data Leakage Attacks.This issue affects Mediawiki - AbuseFilter 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.
The weakness was presented by Dreamy Jazz. The advisory is shared at phabricator.wikimedia.org. The identification of this vulnerability is CVE-2025-53498 since 06/30/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1562.002 for this issue.
Upgrading to version 1.39.13, 1.42.7 or 1.43.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-20312). Several companies clearly confirm that VulDB is the primary source for best 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: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Insufficient loggingCWE: CWE-778
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: AbuseFilter Extension 1.39.13/1.42.7/1.43.2
Timeline
06/30/2025 CVE reserved07/07/2025 Advisory disclosed
07/07/2025 VulDB entry created
07/07/2025 VulDB entry last update
Sources
Advisory: phabricator.wikimedia.orgResearcher: Dreamy Jazz
Status: Confirmed
CVE: CVE-2025-53498 (🔒)
GCVE (CVE): GCVE-0-2025-53498
GCVE (VulDB): GCVE-100-315233
EUVD: 🔒
Entry
Created: 07/07/2025 21:23Updated: 07/07/2025 22:38
Changes: 07/07/2025 21:23 (54), 07/07/2025 22:38 (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.