Skip to content
Web

CVE-2026-84768

9.3
Critical
EPSS 0.24%Patch availableSep 4, 2026

Unauthenticated SQL injection in VikAppointments plugin allows full database compromise.

common questions

Is CVE-2026-84768 being exploited?

Not confirmed. CVE-2026-84768 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.

How severe is CVE-2026-84768?

CVE-2026-84768 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-84768?

Yes. A fix has been recorded for CVE-2026-84768. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-84768 affect?

CVE-2026-84768 affects WordPress VikAppointments Services Booking Calendar <= 1.2.20, WordPress sites using VikAppointments plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-84768?

Update plugin to patched version or remove plugin; restrict DB access and audit logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress VikAppointments Services Booking Calendar <= 1.2.20WordPress sites using VikAppointments plugin
impact

Unauthenticated SQL injection enabling attackers to read/modify/exfiltrate DB, bypass auth, and potentially pivot to RCE on affected WordPress sites.

action required

Immediate action required

affected versions
e4jvikwp VikAppointments Services Booking Calendar
  • affected<= 1.2.20

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free