Summary
CVE-2026-84768 is an unauthenticated SQL Injection vulnerability affecting the VikAppointments Services Booking Calendar plugin for WordPress, in versions up to and including 1.2.20. The flaw allows a remote, unauthenticated attacker to inject and execute malicious SQL statements against the underlying database via a vulnerable plugin parameter. It carries a CVSS v3.1 base score of 9.3 (Critical), reflecting the combination of network exploitability, no authentication requirement, and significant confidentiality impact.
Technical details
- Root cause: Improper neutralization of special elements used in an SQL command (CWE-89) within the VikAppointments plugin codebase, allowing untrusted input to be incorporated into SQL queries without adequate sanitization or parameterization.
- Trigger conditions: No authentication or user interaction is required; the vulnerable functionality is reachable by any remote, unauthenticated user against a WordPress site running the affected plugin version.
- Attack vector: Network (AV:N) — exploitable remotely over HTTP(S) against the WordPress site’s exposed plugin endpoints.
- Exploitation technique: Classified as Blind SQL Injection (CAPEC-7), meaning the attacker infers database responses indirectly (e.g., via timing or boolean-based behavior) rather than through direct output of query results.
- Impact: High confidentiality impact (unauthorized read access to database contents, potentially including sensitive booking, customer, or WordPress user/credential data) and low availability impact. No integrity impact was noted (I:N).
Affected software
- VikAppointments – Services Booking Calendar WordPress plugin, versions ≤ 1.2.20
- Fixed in version 1.2.21 and later
Severity
- CVSS v3.1 Base Score: 9.3 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Mitigation and recommended actions
- Immediate: Update the VikAppointments Services Booking Calendar plugin to version 1.2.21 or later, where the SQL injection issue has been remediated.
- If immediate patching is not possible:
- Restrict or disable public access to the affected plugin’s booking/appointment endpoints until the update can be applied.
- Deploy or update a Web Application Firewall (WAF) with SQL injection detection rules in front of the WordPress site.
- Monitor web server and database logs for anomalous query patterns or unusual response timing consistent with blind SQL injection probing.
- As a general hardening measure, ensure the WordPress core, all plugins, and themes are kept current, and limit database account privileges used by the application to the minimum required.

