CataBlog <= 1.7.0 - Authenticated (Editor+) Arbitrary File Deletion
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- CataBlog
- Affected Version
<= 1.7.0- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2023-47843
At a glance
CVE-2023-47843 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the CataBlog WordPress plugin, affecting versions <= 1.7.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2023, reported by Rafie Muhammad.
Vulnerability Overview
The CataBlog plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 1.7.0. This makes it possible for authenticated attackers, with editor access or higher to delete arbitrary files on the affected site's server which may make site takeovers possible.
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, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in CataBlog <= 1.7.0 takes an account at Editor 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 CataBlog yet, so installs running <= 1.7.0 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 Editor 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
Related records
Other vulnerabilities in CataBlog
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C