Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-47913: n/a

0
Medium
VulnerabilityCVE-2024-47913cvecve-2024-47913
Published: Fri Oct 04 2024 (10/04/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

An issue was discovered in the AbuseFilter extension for MediaWiki before 1.39.9, 1.40.x and 1.41.x before 1.41.3, and 1.42.x before 1.42.2. An API caller can match a filter condition against AbuseFilter logs even if the caller is not authorized to view the log details for the filter.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 07:35:24 UTC

Technical Analysis

CVE-2024-47913 is a vulnerability affecting the AbuseFilter extension of MediaWiki, a widely used open-source wiki platform. The flaw exists in versions before 1.39.9, 1.40.x, 1.41.x before 1.41.3, and 1.42.x before 1.42.2. AbuseFilter is designed to detect and prevent abusive edits by applying filter conditions and logging related events. The vulnerability allows an API caller to query and match filter conditions against AbuseFilter logs without proper authorization to view the log details. This means that an attacker can remotely access metadata or partial information from AbuseFilter logs that should be restricted, potentially revealing sensitive operational details about abuse detection rules and their triggers. The vulnerability is classified under CWE-532 (Information Exposure Through Log Files), indicating that sensitive information is leaked via logs. The CVSS v3.1 base score is 5.3 (medium), reflecting that the attack vector is network-based, requires no privileges or user interaction, and impacts confidentiality only. No integrity or availability impacts are reported. No patches or exploit code links were provided at the time of disclosure, and no known exploits in the wild have been reported. The issue highlights the importance of strict access control on log data in security extensions to prevent information leakage that could aid attackers in circumventing abuse detection mechanisms.

Potential Impact

The primary impact of CVE-2024-47913 is unauthorized disclosure of AbuseFilter log information, which could reveal details about filter conditions and abuse detection activities. This information leakage can assist attackers in understanding how abuse is detected and potentially crafting edits or actions to evade detection. While the vulnerability does not allow modification or disruption of the MediaWiki system, the confidentiality breach can undermine the effectiveness of abuse prevention measures. Organizations relying on MediaWiki for collaborative content management, especially those with sensitive or high-profile content, may face increased risk of targeted abuse or vandalism if attackers leverage leaked log information. The scope is limited to MediaWiki instances using the vulnerable AbuseFilter versions, but given MediaWiki’s widespread use in public and private wikis worldwide, the potential exposure is significant. The lack of authentication requirement and remote exploitability increase the risk, although no active exploitation has been reported. Overall, the impact is moderate but relevant for organizations prioritizing information confidentiality and abuse prevention integrity.

Mitigation Recommendations

To mitigate CVE-2024-47913, organizations should upgrade the AbuseFilter extension to the fixed versions: 1.39.9 or later, 1.41.3 or later, and 1.42.2 or later, depending on their MediaWiki version branch. If immediate patching is not possible, administrators should restrict API access to trusted users only, implementing strict access controls and network-level restrictions to limit exposure. Reviewing and tightening permissions related to AbuseFilter logs and API endpoints can reduce unauthorized access risk. Monitoring API usage logs for unusual or unauthorized queries targeting AbuseFilter logs is recommended to detect potential exploitation attempts. Additionally, consider disabling or limiting AbuseFilter logging if not essential, to minimize sensitive information exposure. Regularly auditing MediaWiki extensions and applying security updates promptly will help prevent similar vulnerabilities. Finally, educating administrators about the sensitivity of log data and enforcing the principle of least privilege on API access are critical best practices.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-10-04T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6d09b7ef31ef0b56d64f

Added to database: 2/25/2026, 9:43:37 PM

Last enriched: 2/28/2026, 7:35:24 AM

Last updated: 4/12/2026, 3:46:03 PM

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses