Skip to main content
VulnerabilityPublished

CVE-2026-119515: Radius Booking (WordPress plugin) · Missing Authorization

Affects Radius Booking (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.0.21 when convenient.

Data as of 9 Nov 2026, 11:38 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.16.5
Patch
Available – fixed in 1.0.21
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Radius Booking (WordPress plugin) to 1.0.21.

Affected software

ProductAffectedFixed in
Radius Booking — Booking Calendar for Appointments & Servicesradius-bookingAffected
  • <1.0.21
Fixed in
  • 1.0.21

AI-suggested

Upgrade Radius Booking — Booking Calendar for Appointments & Services to version 1.0.21 or later, where this missing authorization vulnerability has been fixed. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-119515 is a Missing Authorization vulnerability in Mamunur Rashid's Radius Booking — Booking Calendar for Appointments & Services. It affects versions from the initial release up to 1.0.20. The flaw allows attackers to exploit incorrectly configured access control security levels, potentially leading to unauthorized information disclosure or modification. A fix is available in version 1.0.21.

References

Community reviews

Loading reviews…