Vulnerability

CVE-2026-5513

High· 7.2CVSS7.2

.rules3/5

The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'bookly-customer-full-name' cookie in versions up to, and including, 27.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires 'Remember personal information in cookies' setting to be enabled (disabled by default).

Threat signal

75/100

High

Severity

high

CVSS

7.2

EPSS

—

Active

CVSS

v3.1via NVDOpen in FIRST calculator →

7.2/ 10HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeChangedImpact extends beyond the vulnerable component (e.g. sandbox escape).
Confidentiality ImpactLowSome data disclosure; attacker doesn't fully control what.
Integrity ImpactLowSome data modification; attacker doesn't fully control extent.
Availability ImpactNoneNo availability impact.

EPSS

No EPSS data

FIRST.org publishes EPSS daily. Coverage isn't universal — pre-disclosure CVEs and reserved IDs don't carry an EPSS score until at least one exploitation signal lands. Score will appear within 24 hours of the next EPSS pull.

Vendor VEX

No VEX statements published for CVE-2026-5513. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCTrack

Total impact on non-trivial mission systems

exploitation: none
automatable: no
impact: total
mission: support

Lifecycle

2026-06-13Published
2026-06-13Last modified1 source

References

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.