sales@hackhalt.com

Home / Threats / CVE-2026-86837

Bookly - Security Vulnerability (CVE-2026-86837)

CVE-2026-86837

The Bookly WordPress plugin before 28.3 does not properly verify a customer's identity before updating their stored details, allowing unauthenticated attackers who know a customer's primary identifier to overwrite that customer's stored personal information such as name, email and address.

CVE-2026-86837

MEDIUM CVSS 5.3 Published 2026-09-25 Updated 2026-09-25
AI Risk Moderate (52/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P4 Planned
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Affected Components 1
Reference Links 1
AI Risk Engine Moderate (52/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-09-25 CVE published and first recorded in the threat feed.
  2. 2026-09-25 Record updated with latest vulnerability metadata.
  3. 2026-10-01 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 5 hours ago

AI enriched 5 hours ago (2026-10-01 08:03 UTC)

Technical Summary

The Bookly WordPress plugin before 28.3 does not properly verify a customer's identity before updating their stored details, allowing unauthenticated attackers who know a customer's primary identifier to overwrite that customer's stored personal information such as name, email and address.

Potential Impact

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

Exploitability Assessment

Exploitability is assessed as Low based on low-bar exploit prerequisites.

Primary risk drivers: 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 52/100 (Moderate, Low) with priority P4 Planned. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Bookly PLUGIN · bookly Affected: < 28.3 Fixed in: 28.3

References

What to do about this

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

Fix it

Update Bookly to 28.3 or later.

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

No Hack Halt control meaningfully contains this one — updating is the remedy. We would rather say so than sell you something that will not help.

Start free

Not sure if you are affected?

Scan your site to see whether it runs Bookly, 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 Bookly. Versions below 28.3 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 Bookly to version 28.3 or later. That is the complete fix.