CVE-2024-47913: Improper permissions handling in MediaWiki AbuseFilter
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.
Other sources
Improper permissions handling in MediaWiki AbuseFilter
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/mediawiki/abuse-filterto a version that resolves this vulnerability.Fixed in 1.42.2 - Upgrade
Upgrade
composer/mediawiki/abuse-filterto a version that resolves this vulnerability.Fixed in 1.41.3 - Upgrade
Upgrade
composer/mediawiki/abuse-filterto a version that resolves this vulnerability.Fixed in 1.39.9 - Upgrade
Upgrade
debian/mediawikito a version that resolves this vulnerability.Fixed in 1:1.39.10-1~deb12u1 - Upgrade
Upgrade
debian/mediawikito a version that resolves this vulnerability.Fixed in 1:1.39.10-1 - Upgrade
Upgrade
debian/mediawikito a version that resolves this vulnerability.Fixed in 1:1.39.17-1+deb12u2Fixed in 1:1.43.9+dfsg-1~deb13u1Fixed in 1:1.43.11+dfsg-3
Event History
Frequently Asked Questions
What is the severity of CVE-2024-47913?
CVE-2024-47913 is categorized as a moderate severity vulnerability affecting specific versions of the AbuseFilter extension for MediaWiki.
How do I fix CVE-2024-47913?
To fix CVE-2024-47913, upgrade the AbuseFilter extension to version 1.42.2 or later, or to 1.41.3, or to 1.39.9.
What versions of MediaWiki are affected by CVE-2024-47913?
CVE-2024-47913 affects MediaWiki versions before 1.39.9, 1.41.x before 1.41.3, and 1.42.x before 1.42.2.
What does CVE-2024-47913 allow an attacker to do?
CVE-2024-47913 allows an unauthorized API caller to match a filter condition against AbuseFilter logs.
Is there a known exploitation method for CVE-2024-47913?
Currently, no specific exploitation method for CVE-2024-47913 has been detailed, but it poses a risk of unauthorized data exposure.