# CVE-2026-14321: Divi Dash < 1.0.7 - Unauthenticated Denial of Service via IP Address Spoofing

> Unauthenticated attackers can spoof IP addresses to bypass rate limits and exhaust resources, causing denial of service in Divi Dash.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-v73c-8gwm-q3w7

## What is CVE-2026-14321?

CVE-2026-14321 is a high-severity denial of service vulnerability in Unknown divi-dash, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The divi-dash WordPress plugin before 1.0.7 does not validate the source of the client IP address it uses for rate limiting and banning, allowing unauthenticated attackers to spoof arbitrary IP addresses in order to bypass rate limiting, ban chosen addresses from the feature, and grow a stored option without bound, resulting in denial of service.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-14321?


## How do I fix CVE-2026-14321?

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

## Is CVE-2026-14321 being exploited?

There is no known exploitation of CVE-2026-14321 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14321 and fix it if it is affected.

What it is: CVE-2026-14321 is a high-severity denial of service vulnerability in Unknown divi-dash, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14321 in the wild and no public exploit code.

Affected product: Unknown divi-dash. 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-2026-14321/ (Markdown: https://insights.sbomify.com/CVE-2026-14321/index.md)
```

## Sources

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

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