WP-Syntax <= 1.2 - Authenticated (Author+) Regex Denial of Service
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP-Syntax
- Affected Version
<= 1.2- CVSS
- 4.3Medium
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE-2024-13926
At a glance
CVE-2024-13926 is a medium-severity Uncontrolled Resource Consumption vulnerability in the WP-Syntax WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Author level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed March 2025, reported by Pierre Rudloff.
Vulnerability Overview
The WP-Syntax plugin for WordPress is vulnerable to Regex Denial of Service in all versions up to, and including, 1.2. This is due to plugin not properly validating a regex before running it. This makes it possible for authenticated attackers, with Author-level access and above, to cause a limited denial of service based on a faulty regex.
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.
CWE-400: Uncontrolled Resource Consumption
Reaching this weakness in WP-Syntax <= 1.2 takes an account at Author level or above. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. No fixed build of this plugin is recorded for WP-Syntax yet, so installs running <= 1.2 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 Author 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 WP-Syntax
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C