Is CVE-2026-5513 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5513 being exploited in the wild.

How severe is CVE-2026-5513?

High severity, with a CVSS score of 7.2, published 13 June 2026.

Which products and versions are affected?

Bookly up to, and including, 27.2.

Is there a fix for CVE-2026-5513?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-5513 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-5513?

Check whether you run Bookly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5513: Bookly WordPress Plugin Stored XSS in bookly-customer-full-name cookie

CVE-2026-5513 · Severity: high · CVSS 7.2 · Published 2026-06-13

The Bookly plugin for WordPress, which manages online scheduling and appointments, contains a security flaw that allows attackers to inject malicious scripts into the website. This occurs through a specific cookie used to store customer names, potentially leading to unauthorized actions or data theft when other users visit the site. The risk is present only if the 'Remember personal information in cookies' setting is manually enabled.

Technologies: Bookly. Vendors: Bookly.

Quick answers

Is CVE-2026-5513 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5513 being exploited in the wild.
How severe is CVE-2026-5513?: High severity, with a CVSS score of 7.2, published 13 June 2026.
Which products and versions are affected?: Bookly up to, and including, 27.2.
Is there a fix for CVE-2026-5513?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-5513 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-5513?: Check whether you run Bookly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Bookly plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) due to insufficient input sanitization and output escaping of the 'bookly-customer-full-name' cookie. An unauthenticated attacker can manipulate this cookie value to include arbitrary web scripts. These scripts are then stored and executed in the browser of any user who accesses a page where the customer name is displayed. This vulnerability requires the 'Remember personal information in cookies' setting to be enabled, which is disabled by default. A fix is available in versions following 27.2.

Affected products

Bookly Bookly plugin for WordPress up to, and including, 27.2

Timeline

2026-06-13: disclosed
2026-06-13: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.