Security readout for executives and security teams
Plain-English summary
A flaw in the WordPress VikAppointments booking plugin may let an unauthenticated internet user manipulate database queries. Successful exploitation could expose sensitive database information and cause limited service disruption. The supplied CVSS score is 9.3, making rapid exposure assessment important.
Executive priority
Treat this as an urgent internet-facing exposure review. Prioritize public booking sites and systems holding customer or appointment data. Remediate confirmed installations promptly, while avoiding unsupported assumptions about a fixed version. Escalate if suspicious activity or unexpected database access is identified.
Technical view
CVE-2026-84768 is an unauthenticated SQL injection vulnerability, classified as CWE-89, reportedly affecting VikAppointments Services Booking Calendar through version 1.2.20. The CVSS 3.1 vector indicates network access, low complexity, no privileges or user interaction, high confidentiality impact, no integrity impact, limited availability impact, and changed scope.
Likely exposure
WordPress sites are potentially exposed when they run VikAppointments version 1.2.20 or earlier and vulnerable plugin functionality is publicly reachable. The bundle does not identify the affected endpoint, configuration prerequisites, or whether exploitation requires an active booking form. Confirm installed versions and exposure directly.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. They also provide no public exploit details here. Risk remains serious because the reported flaw is remotely reachable without authentication and requires low attack complexity.
Researcher notes
The bundle identifies versions through 1.2.20 in its title and description, but its structured affected record lists versions as “n/a” with default status “unaffected.” This inconsistency reduces certainty. No vulnerable parameter, endpoint, root cause detail, fixed version, or forensic indicator is supplied. Validate those details against updated CVE and Patchstack records.
Mitigation direction
Identify every WordPress site running VikAppointments and record its installed version.
Check current vendor and Patchstack guidance for a fixed release or official mitigation.
Upgrade beyond the affected range when a trusted source confirms the corrected version.
Temporarily disable the plugin or restrict access if remediation cannot be completed promptly.
Preserve relevant web, application, and database logs before making changes.
Validation and detection
Confirm the plugin version through trusted WordPress administration or asset inventory records.
Verify affected functionality is not reachable anonymously after mitigation.
Review logs for unusual requests and database errors involving VikAppointments routes.
Confirm the site and booking workflows operate normally after updating or disabling the plugin.
Recheck vendor and CVE records for revised affected-version or remediation information.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.