Skip to main content
VulnerabilityPublished

CVE-2026-87115: VikAppointments Services Booking Calendar (WordPress plugin) · Path Traversal

Affects VikAppointments Services Booking Calendar (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
e4jvikwpVikAppointments Services Booking CalendarAffected
  • <=1.2.21
Fixed in–

AI-suggested

Users should verify the vendor advisory for updates. Until a fix is available, avoid publishing File-type custom fields on the confirmation page shortcode to reduce exposure. Monitor vendor channels for official remediation guidance.

Description

The VikAppointments Services Booking Calendar plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the extract function in all versions up to, and including, 1.2.21. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires at least one File-type custom field to be published on the confirmation page shortcode, as this field is not created by default during plugin installation.

References

Community reviews

Loading reviews…