Mediawiki - CSS Extension: Improper Limitation of a Pathname to a Restricted Directory
CVE-2024-47841 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Mediawiki - CSS Extension from Wikimedia Foundation, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 1.42.2, 1.41.3, 1.39.9 as the first without the flaw, so updating Mediawiki - CSS Extension to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 34.6% chance of exploitation within 30 days, which is in the top 1.55% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Mediawiki - CSS Extension to 1.42.2 or 1.41.3 or 1.39.9, whichever matches your release line, or a later version.
- Update mediawiki-extensions-css to 1.42.2 or 1.41.3 or 1.39.9, whichever matches your release line, or a later version.
- Update Wikimedia-extensions-css to 1.39.9 or 1.41.3 or 1.42.2, whichever matches your release line, or a later version.
- Read the advisory on phabricator.wikimedia.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| The Wikimedia Foundation | Mediawiki - CSS Extension | 1.42.x up to, but not including, 1.42.2; 1.41.x up to, but not including, 1.41.3; 1.39.x up to, but not including, 1.39.9 | 1.42.2, 1.41.3, 1.39.9 |
| Wikimedia | mediawiki-extensions-css | 1.42.0 up to, but not including, 1.42.2; 1.41.0 up to, but not including, 1.41.3; 1.39.0 up to, but not including, 1.39.9 | 1.42.2, 1.41.3, 1.39.9 |
| Wikimedia | Wikimedia-extensions-css | 1.39.0 up to, but not including, 1.39.9; 1.41.0 up to, but not including, 1.41.3; 1.42.0 up to, but not including, 1.42.2 | 1.39.9, 1.41.3, 1.42.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 6.9 | Medium | CNA |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in The Wikimedia Foundation Mediawiki - CSS Extension allows Path Traversal.This issue affects Mediawiki - CSS Extension: from 1.42.X before 1.42.2, from 1.41.X before 1.41.3, from 1.39.X before 1.39.9.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- phabricator.wikimedia.org/T368628Issue Tracking
- phabricator.wikimedia.org/T369486Exploit, Issue Tracking
Patches and release notes
Other vulnerabilities in Mediawiki - CSS Extension
- 7.5 High severity
- 8.2 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.6 Critical severity
- 7.5 High severity
Spotted an error? Tell us.