Security readout for executives and security teams
Plain-English summary
CVE-2026-2230 affects the WordPress Booking Calendar plugin through version 10.14.14. A logged-in low-privilege user, if granted booking permissions by an administrator, may change another user’s plugin settings. The likely business impact is disruption or misconfiguration of booking calendar behavior, not full site takeover.
Executive priority
Treat as a moderate-priority WordPress plugin issue. Prioritize sites with customer-facing booking workflows or many low-privilege users. The main risk is booking disruption and unauthorized settings changes, not confirmed data theft or remote takeover.
Technical view
The issue is an insecure direct object reference in Booking Calendar’s handle_ajax_save function. Missing validation on a user-controlled key allows authenticated Subscriber-level or higher users with administrator-granted booking permissions to modify other users’ plugin settings, such as calendar display options. CVSS is 4.3, reflecting low-complexity, authenticated network exploitation with limited integrity impact.
Likely exposure
Exposure is limited to WordPress sites running Booking Calendar versions up to and including 10.14.14, where untrusted or broad user accounts have booking permissions.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Exploitation requires authentication and booking permissions granted by an administrator.
Researcher notes
Root cause is CWE-639 authorization bypass via user-controlled object reference in handle_ajax_save. Public sources identify the vulnerable range but do not provide evidence of active exploitation. Fixed-version details should be confirmed from vendor or WordPress.org release guidance.
Mitigation direction
- Inventory WordPress sites using the Booking Calendar plugin.
- Identify installations running Booking Calendar 10.14.14 or earlier.
- Review vendor or WordPress plugin guidance for the fixed release.
- Apply the vendor-provided update when available.
- Restrict booking permissions to trusted users only.
- Remove unnecessary Subscriber-level accounts with booking permissions.
Validation and detection
- Confirm installed Booking Calendar plugin versions across WordPress environments.
- Review user roles and booking permissions for least-privilege alignment.
- Check whether any untrusted accounts have booking permissions.
- Review plugin update history against WordPress.org changeset 3456856.
- Monitor plugin settings changes for unexpected modifications.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-2230 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/60f7df44-22f9-4a9e-a20c-4b8628674079?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/booking/trunk/includes/save-user-meta/save-user-meta.php#L90CVE reference
- https://plugins.trac.wordpress.org/changeset/3456856/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.