CVE-2024-47913VulnerabilityPublished 4 Oct 2024Updated 6 Dec 2024

CVE-2024-47913: AbuseFilter · n/a

Affects AbuseFilterSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 1.41.3 : update AbuseFilter when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.41.3, 1.41.0, 1.39.9

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mediawiki/extensions/AbuseFilter to 1.41.3, 1.41.0 or 1.39.9.

Affected software

Product	Affected	Fixed in
GitHubmediawiki/extensions/AbuseFilter`pkg:github/mediawiki/extensions/AbuseFilter`Other threats	Affected <1.39.9 >=1.40.0 <1.41.0 <1.41.3	Fixed in 1.39.9 1.41.0 1.41.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

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.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 07:35 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats