Security readout for executives and security teams
Plain-English summary
A critical flaw in the WordPress WP BASE Booking plugin could let an unauthenticated remote attacker execute arbitrary code. Successful exploitation could compromise the website, its data, and potentially the hosting environment. The supplied description identifies versions through 6.3.0, but the structured affected-version metadata is incomplete and internally inconsistent.
Executive priority
Treat this as an immediate inventory and containment priority. Internet-facing confirmed installations at 6.3.0 or earlier warrant urgent action because exploitation could cause complete compromise. Do not assume a fixed version from the supplied data; require technical owners to verify authoritative guidance and report exposure, containment, and remediation status.
Technical view
CVE-2026-61962 is classified as CWE-94 code injection with CVSS 3.1 score 10.0. The vector indicates network access, low complexity, no privileges, no user interaction, changed scope, and high confidentiality, integrity, and availability impact. The supplied sources do not describe the vulnerable component, attack mechanism, prerequisites beyond the vector, or a fixed release.
Likely exposure
Highest risk applies to internet-accessible WordPress sites running the plugin slug wp-base-booking-of-appointments-services-and-events at version 6.3.0 or earlier. Exposure cannot be determined from WordPress alone; organizations must inventory installations and confirm versions. Treat the structured “n/a” and default-unaffected metadata cautiously because it conflicts with the title and description.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not listed as KEV in the supplied data. No public exploit availability or observed campaign is documented here. Nevertheless, unauthenticated network-reachable code execution with a 10.0 score presents severe exploitation potential where affected plugin versions are exposed.
Researcher notes
Evidence supports severity and broad impact, but not the underlying code path, exploit maturity, or active attacks. The structured affected entry reports versions as “n/a” with default status “unaffected,” conflicting with the title and description’s “<= 6.3.0” claim. Validate authoritative records and vendor guidance before making precise version assertions.
Mitigation direction
- Identify every WordPress installation using WP BASE Booking and record its installed version.
- Check current vendor and Patchstack guidance for an approved fixed release or mitigation.
- Apply the vendor-supported update promptly when its fixed-version status is confirmed.
- Disable or remove the plugin where operationally acceptable until authoritative remediation is available.
- Restrict public access to affected sites if the plugin cannot be safely disabled or updated.
Validation and detection
- Confirm the plugin slug and version on each production, staging, and dormant WordPress instance.
- Verify whether the plugin is active and whether the WordPress site is internet-accessible.
- Compare installed versions with current vendor or Patchstack remediation guidance.
- Review relevant web, WordPress, and host telemetry for unexplained changes or suspicious activity.
- After remediation, confirm the vulnerable version is absent and required booking functions still operate.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-61962 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
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
SSVC decision data
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:N/UI:N/S:C/C:H/I:H/A:H3.96PatchstackVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.