sales@hackhalt.com

Home / Threats / CVE-2026-14321

Divi Dash - Security Vulnerability (CVE-2026-14321)

CVE-2026-14321

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.

CVE-2026-14321

HIGH CVSS 8.2 Published 2026-09-23 Updated 2026-09-23
AI Risk High (88/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Affected Components 1
Reference Links 1
AI Risk Engine High (88/100)
Exploitability Very High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-23 CVE published and first recorded in the threat feed.
  2. 2026-09-23 Record updated with latest vulnerability metadata.
  3. 2026-10-04 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 3 days ago

AI enriched 3 days ago (2026-10-04 10:38 UTC)

Technical Summary

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.

Potential Impact

Severity is HIGH (CVSS 8.2). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Very High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 88/100 (High, Very High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Divi Dash PLUGIN · divi-dash Affected: < 1.0.7 Fixed in: 1.0.7

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Divi Dash to 1.0.7 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Inbound firewall policies in Hack Halt Pro blocks this class of attack before WordPress processes the request.

Turn the inbound firewall to enforcing. In Observe mode requests are logged but never blocked, so the protection is reporting only.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Divi Dash, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Divi Dash. Versions below 1.0.7 are vulnerable; that release and later are not. No account is needed to exploit this, so a public site is reachable by anyone.

How do I fix it?

Update Divi Dash to version 1.0.7 or later. That is the complete fix. Until you can update, Inbound firewall policies in Hack Halt Pro contains this class of attack at the request layer.

What can an attacker actually do?

This is a Denial of Service flaw. An attacker who exploits it can exhaust the server's resources and take the site offline.