Unauthenticated stored XSS via customer-name cookie
Published Jun 13, 2026 · Updated Jun 13, 2026
Stored XSS in Bookly 27.2 and earlier allows remote attackers to execute scripts through a crafted customer-name cookie. Bookly reads the bookly-customer-full-name cookie as remembered customer data and later renders it without sufficient input sanitization or output escaping. The default-disabled “Remember personal information in cookies” setting must be enabled, and the injected script runs when a user opens the affected page.
Summary
What happened
Stored XSS in Bookly 27.2 and earlier allows remote attackers to execute scripts through a crafted customer-name cookie. Bookly reads the bookly-customer-full-name cookie as remembered customer data and later renders it without sufficient input sanitization or output escaping. The default-disabled “Remember personal information in cookies” setting must be enabled, and the injected script runs when a user opens the affected page.
The record
- CVE
- CVE-2026-5513
- Published
- Jun 13, 2026
- Updated
- Jun 13, 2026
- Vendor
- Ladela Interactive
- Product
- Bookly
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2026CVE publishedPublication date reported by the CVE source.
- Jun 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=27.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo