Strategic Overview
- Status
- Patched in 1.5.1
- Affected Plugin
- CSS JS Files
- Affected Version
<= 1.5.0- CVSS
- 4.9Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-9146
At a glance
CVE-2024-9146 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the CSS JS Files WordPress plugin, affecting versions <= 1.5.0. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Admin level or above. The issue is fixed in version 1.5.1; sites on affected versions should update now. Disclosed September 2024, reported by jsjp.
Vulnerability Overview
The CSS JS Files plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.5.0 via the editor_page() function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CSS JS Files <= 1.5.0 carries this weakness at editor_page(), and reaching it takes an account at Admin level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For CSS JS Files the fix is 1.5.1: builds <= 1.5.0 are affected, anything from 1.5.1 onward is not.
Remediation
Update to version 1.5.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Admin access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CSS JS Files 1.5.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C