# CVE-2024-13926: WP-Syntax <= 1.2 - Author+ Potential ReDoS

> An attacker can cause a denial of service by submitting posts with many tags, exploiting regex backtracking in the WP-Syntax plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2025
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-p6jq-9gcc-mcvx

## What is CVE-2024-13926?

CVE-2024-13926 is a high-severity denial of service vulnerability in Unknown WP-Syntax, published on 19 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP-Syntax WordPress plugin through 1.2 does not properly handle input, allowing an attacker to create a post containing a large number of tags, thereby exploiting a catastrophic backtracking issue in the regular expression processing to cause a DoS.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2024-13926?

It affects 1 product.


Products: Connections-Pro Wp-Syntax.

## How do I fix CVE-2024-13926?

No fix has been published for CVE-2024-13926 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-13926 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13926 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13926 and fix it if it is affected.

What it is: CVE-2024-13926 is a high-severity denial of service vulnerability in Unknown WP-Syntax, published on 19 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13926 exists.

Affected product: Unknown WP-Syntax. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13926/ (Markdown: https://insights.sbomify.com/CVE-2024-13926/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13926
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13926
- OSV: https://osv.dev/vulnerability/CVE-2024-13926

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13926/
Summaries are generated and may contain mistakes; the official description above is the record.