CVE-2026-86837

Bookly < 28.3 - Unauthenticated Customer PII Update via Verification Bypass

MEDIUM
5.3
CVSS Score
Published: September 25, 2026 at 08:30 AM UTC
Updated: September 25, 2026 at 01:37 PM UTC
1 product affected across 1 vendorBookly

Using Bookly by Unknown?

Get instant alerts when new vulnerabilities affect Bookly - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Bookly· Booklywordpress-plugin
60%
v < 28.3
Affected range stops below 28.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

ExploitVDB EntryTechnical Description
Source: cverecord
https://wpscan.com/vulnerability/5bfed7cf-5bf3-4a3b-a2b6-9f9d48f52fd5/

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMWPScan
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-639

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card