Stored XSS in Bookly WordPress plugin via bookly-customer-full-name cookie
CVE-2026-5513 is a stored cross-site scripting vulnerability in the Online Scheduling and Appointment Booking System – Bookly plugin for WordPress. Affected versions are up to and including 27.2. The issue is caused by insufficient input sanitization and output escaping of data from the 'bookly-customer-full-name' cookie. An unauthenticated attacker can supply malicious script content through that cookie, and the payload may later be rendered in application pages without proper neutralization, resulting in stored JavaScript execution in victims' browsers when they access the affected page.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.