SC filechecker <= 0.6 - Authenticated (Admin+) Arbitrary File Deletion
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- SC filechecker
- Affected Version
<= 0.6- CVSS
- 4.9Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2024-35743
At a glance
CVE-2024-35743 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the SC filechecker WordPress plugin, affecting versions <= 0.6. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires an authenticated account at Admin level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed June 2024, reported by YC_Infosec.
Vulnerability Overview
The SC filechecker plugin for WordPress is vulnerable to Arbitrary File Deletion in all versions up to, and including, 0.6. This makes it possible for authenticated attackers, with administrator-level access and above, to delete arbitrary files on the server which can lead to remote code execution.
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 integrity.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in SC filechecker <= 0.6 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. No fixed build of this plugin is recorded for SC filechecker yet, so installs running <= 0.6 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C