Loading vulnerability…
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 this cookie, and the payload may be stored and later rendered in application pages, resulting in execution in the victim's browser when an injected page is accessed.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Python exploit utility and a README. The main file, CVE-2026-5513.py, is a standalone multithreaded scanner/injector for CVE-2026-5513, a stored XSS issue in the WordPress Bookly plugin up to version 27.2. The exploit targets the bookly-customer-full-name cookie and is designed to work without authentication when Bookly's 'Remember personal information in cookies' feature is enabled. The script appears operational rather than a simple proof-of-concept: it supports single-target and bulk scanning, thread-based concurrency, optional proxying, verbose output, automatic dependency installation, result tracking, and auto-saving of vulnerable targets. Based on the visible code and README, its workflow is: normalize/probe target URLs or bare IPs, try common ports and WordPress subdirectories, identify Bookly-related pages, check plugin/version indicators, test whether the cookie value is reflected, and optionally inject either a default or user-supplied XSS payload. Primary exploit capability: cookie-based stored XSS injection into Bookly booking forms. The canary payload is used to confirm reflection, while the default/custom payload is intended to execute JavaScript in the victim browser context when the vulnerable form renders the cookie value. The exploit is web-delivered and browser-executed, but the tool itself interacts with targets over HTTP(S). Repository structure is minimal: one Python script as the entry point and one README documenting vulnerability details, usage, options, attack flow, and remediation. No evidence suggests it belongs to a larger exploit framework.
12 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.
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.