Is CVE-2026-121784 exploited in the wild?

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

How severe is CVE-2026-121784?

Medium severity, with a CVSS score of 6.5, published 7 November 2026.

Which products and versions are affected?

MagePeople WpBookingly through 1.4.3.

Is there a fix for CVE-2026-121784?

Yes: fixed in 1.4.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-121784 attacked?

It is attacked over the network.

Am I affected by CVE-2026-121784?

Check whether you run MagePeople WpBookingly 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-121784: Magepeople WpBookingly stored cross-site scripting

CVE-2026-121784 · Severity: medium · CVSS 6.5 · Published 2026-11-07

WpBookingly is a WordPress plugin that manages service bookings on websites. A stored cross-site scripting (XSS) vulnerability in this plugin allows attackers with contributor-level privileges to inject malicious scripts that execute in the browsers of visitors and other administrators, potentially stealing session cookies or account credentials. The vulnerability affects versions up to 1.4.3.

Technologies: MagePeople WpBookingly. Vendors: MagePeople.

Quick answers

Is CVE-2026-121784 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-121784 being exploited in the wild.
How severe is CVE-2026-121784?: Medium severity, with a CVSS score of 6.5, published 7 November 2026.
Which products and versions are affected?: MagePeople WpBookingly through 1.4.3.
Is there a fix for CVE-2026-121784?: Yes: fixed in 1.4.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-121784 attacked?: It is attacked over the network.
Am I affected by CVE-2026-121784?: Check whether you run MagePeople WpBookingly 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.

How to fix

Fixed in: 1.4.4

Technical details

A stored XSS vulnerability exists in WpBookingly due to improper neutralization of user input during web page generation. The vulnerability requires a privileged user (contributor or above) to perform an action such as clicking a malicious link or submitting a form. An attacker can inject arbitrary JavaScript that is stored in the database and executed in the context of other users' browsers, compromising their sessions and data. The vulnerability is fixed in version 1.4.4.

Affected products

Magepeople WpBookingly through 1.4.3

Timeline

2026-11-07: disclosed
2026-11-07: patched

References

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