Running Radius Booking on your site? Check it against CVE-2026-119516 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Radius Booking is in the affected range (≤ 1.0.20), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →A booking plugin has one job: take appointments. The Radius Booking — Booking Calendar for Appointments & Services plugin by Mamunur Rashid also, in versions up to and including 1.0.20, deserializes untrusted data — the classic PHP object-injection shape, reachable with no account at all. That is CVE-2026-119516, scoring CVSS 9.8, disclosed November 6, 2026 (CNA: Patchstack).
CVE-2026-119516 is a deserialization of untrusted data vulnerability in the Radius Booking plugin (wordpress.org slug radius-booking, 500+ active installs at disclosure time).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Network-reachable, low complexity, no privileges and no user interaction required.Check wp-admin → Plugins for Radius Booking and its version. At 1.0.20 or below, your site runs the affected code in the plugin that takes its appointments.
Our scanner checks it: run the free mini-scan, or check just this plugin at /tools/plugin-check?slug=radius-booking. The check reads the version your site announces and flags 1.0.20 and below. A version above 1.0.20 earns no "patched" claim from us, though — the CVE record names no fixed version, so the check stays silent above the affected range rather than calling any release the fix.
Niche vertical plugins — bookings, directories, dealerships — get the same attacker attention as the big names, with smaller security teams behind them. "It's only the booking calendar" is exactly backwards: the plugin that faces the public, unauthenticated, all day is the one whose input handling matters most, and unserialize() on anything a visitor controls is one of PHP's oldest ways to hand over a site. Put every public-facing plugin on the same patch cadence, whatever its install count.
Related: WordPress Hardening for AI-Built Sites — the standing version of this discipline. How to Check If Your Web App Is Hacked — the follow-up pass if the audit finds an account you do not recognize.
Running WordPress with Radius Booking? Update to the newest release today, audit your users, then run the free check at preshipit.com/free-scan — our scanner checks it, version-checking this plugin against CVE-2026-119516 from the version your site announces to the world.
Check Radius Booking on your own site — free.
Our free WordPress Plugin Vulnerability Checker pulls Radius Booking's current version from wordpress.org and lists the vulnerabilities our scanner checks for — CVE-2026-119516 included. No scan, no account.
Open the free plugin checker →The PreShipIt Brief — a short weekly email for people shipping vibe-coded apps: the week's important vulnerabilities and launch-safety checks, in plain English.
New and free. Double opt-in: we email you a confirmation link before anything else arrives. Unsubscribe any time.
Running Radius Booking on your site? Check it against CVE-2026-119516 — free.
The free mini-scan checks your live site from the outside and reads the plugin versions it exposes — if your Radius Booking is in the affected range (≤ 1.0.20), it flags it, alongside TLS/HTTPS basics, security headers, cookie flags, exposed files and Firebase/Supabase backend rules. You get a score and the finding titles — no account, no card.
Run the free mini-scan →← Back home · Run a free mini-scan · Scan my app — $29 · See a sample report