CVERadar
CRITICAL · CVSS 3.1 9.1EPSS 0.35% (p28)Threat level 46

CVE-2026-116557: CVE-2026-116557: The WP Booking System - Booking Calendar plugin for WordPress is vulnerable to unauthorize…

Unknown · WP Booking System - Booking Calendar WordPress plugin · NVD published 2026-10-31 · posted 2026-11-04 · last modified 2026-11-02

CVE-2026-116557 at a glance

CVE-2026-116557 is a critical-severity Missing Authorization vulnerability in WP Booking System - Booking Calendar WordPress plugin, with a CVSS 3.1 base score of 9.1. NVD published it on 2026-10-31 and classifies the weakness as CWE-862. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.35% (percentile 28.4, scored 2026-11-03). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Privilege Escalation, inferred from the CWE and the description. Its CVERadar threat level is 46/100.

What it is

The WP Booking System - Booking Calendar plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the wpbs_action_ajax_calendar_remove_note() function in versions up to, and including, 2.1.0.5 This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary calendar notes belonging to any calendar.

WeaknessCWE-862 definition
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H (source: Wordfence)
ATT&CK tacticsPrivilege Escalation

Defend the Chain

The attack chain for CVE-2026-116557 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 46/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1068 Exploitation for Privilege Escalation Inferred

Inferred from CWE CWE-862

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

MITRE ATT&CK mitigations for this chain

  • M1051 Update Software (for T1068) : Update software regularly by employing patch management for internal enterprise endpoints and servers.
  • M1050 Exploit Protection (for T1068) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
  • M1048 Application Isolation and Sandboxing (for T1068) : Make it difficult for adversaries to advance their operation through exploitation of undiscovered or unpatched vulnerabilities by using sandboxing. Other types of virtualization and application microsegmentation may also mitigate the impact of some types of exploitation. Risks of additional exploits and weaknesses in t
  • M1019 Threat Intelligence Program (for T1068) : Develop a robust cyber threat intelligence capability to determine what types and levels of threat may use software exploits and 0-days against a particular organization.
  • M1038 Execution Prevention (for T1068) : Consider blocking the execution of known vulnerable drivers that adversaries may exploit to execute code in kernel mode. Validate driver block rules in audit mode to ensure stability prior to production deployment.

Detection Generic guidance

  • Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and on exploitation crashes of privileged services.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Not sure which of your web apps face the internet? An attack surface review from LayerLogix maps what is exposed.

Sources