Skip to main content

VikAppointments EUVDEUVD-2026-91958

| CVE-2026-87115 CRITICAL
Path Traversal (CWE-22)
2026-10-03 Wordfence GHSA-x82w-x82x-7998
9.1
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach public confirmation-page shortcode
  2. Delivery
    Craft traversal path in extract request
  3. Exploit
    Bypass insufficient file-path validation
  4. Execution
    Delete wp-config.php on server
  5. Impact
    Hijack reinstall flow for RCE

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the VikAppointments site has published at least one File-type custom field on the confirmation-page shortcode; this field is NOT created by default at installation, so stock/default deployments are not directly exploitable. When that field exists, the flaw is reachable remotely and without authentication (PR:N/UI:N) against affected versions up to and including 1.2.21, with no user interaction needed. The primary limiting factor is therefore this non-default configuration state; impact is maximized when a security-relevant file (e.g., wp-config.php) can be targeted, which enables site takeover/RCE.

Impact

This is a genuinely high-severity flaw but with an important real-world caveat. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) is fully consistent with the description: a network-reachable, unauthenticated path-traversal file deletion (CWE-22) with high integrity and availability impact, and the deletion of a sensitive file such as wp-config.php plausibly escalates to RCE, justifying the 9.1 CRITICAL rating. However, the raw score overstates out-of-the-box exposure: exploitation is gated on a non-default configuration (at least one File-type custom field published on the confirmation-page shortcode), which is NOT created during plugin installation. This precondition is environmental rather than attacker-controlled, so it does not change PR (still unauthenticated) but it materially narrows the exploitable population - many installs will simply not have the required field. No EPSS score, no CISA KEV listing, and no public exploit were provided in the input, so there is no signal of active exploitation or mass-automatable attacks at this time. Net assessment: treat as a high priority to patch for any site that uses File-type custom fields on the confirmation page, but recognize that default/stock installations are not directly exploitable, making this closer to a conditional-critical than a universally wormable issue.

Exploit ScenarioDerived

An unauthenticated attacker reaches the public confirmation-page shortcode of a VikAppointments site that has published a File-type custom field, and submits a crafted request to the plugin's file 'extract' handler containing directory-traversal sequences. The insufficient path validation lets the request resolve to a sensitive file outside the intended upload directory - deleting wp-config.php, which can force WordPress into its installation flow and enable takeover/RCE. No public exploit code was identified at time of analysis, and exploitation requires that the non-default File custom field be present.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.9% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 03, 2026

Unauthenticated arbitrary file deletion in the VikAppointments Services Booking Calendar WordPress plugin (all versions up to and including 1.2.21) lets a remote attacker specify a server file path that the plugin will remove without authentication or user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H, 9.1), which can escalate to full site takeover when a critical file such as wp-config.php is deleted. Exploitation is conditional: the site must have published at least one File-type custom field on the confirmation-page shortcode, a configuration that is not created by default during plugin installation, so stock deployments are not directly reachable. No public exploit code was identified and the issue is not listed in CISA KEV at time of analysis, but the low complexity and unauthenticated reachability make prompt patching important on any site that uses custom File-type booking fields. Reported by Wordfence via the CVE program.

RemediationAI

Update the VikAppointments plugin to a release above 1.2.21, since every version through 1.2.21 is affected and the vendor has published a code fix in changeset 3721264 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3721264%40vikappointments&new=3721264%40vikappointments); consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/75fc5df5-a774-4fe1-8452-d35ba7b69081?source=cve for the vendor-confirmed fixed version before upgrading, and note that the exact patched version number is not confirmed by the data provided here. If immediate update is not possible, the most effective compensating control is to remove or unpublish every File-type custom field attached to the confirmation-page shortcode, which eliminates the vulnerable code path entirely - the trade-off is that customers lose the file-upload capability on those booking forms. Deactivating the plugin until it can be patched is the safest fallback, at the cost of losing all booking functionality on the site. A WAF or virtual-patching rule that blocks path-traversal sequences and absolute paths in requests to the confirmation endpoint can reduce exposure but is bypassable and should not substitute for the update. Because the worst-case outcome is deletion of wp-config.php leading to site takeover, take and verify off-host backups of WordPress core, wp-config.php and the database before and after remediation, and review web server logs for anomalous deletion requests; deleting wp-config.php also forces WordPress into its setup routine, so any unexpected setup screen should be treated as a likely compromise indicator.

Affected VersionsENISA

VikAppointments Services Booking Calendar 0 ≤1.2.21

Affected Packages

euvd vikappointments_services_booking_calendar no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a path-traversal (CWE-22) weakness in the file-handling library used by VikAppointments' custom-field subsystem, specifically the extract logic in site/helpers/libraries/customfields/types/file.php, which is reached through the confirmation controller (site/controllers/confirmapp.php) and the plugin bootstrap (vikappointments.php). When a File-type custom field is attached to the confirmation-page shortcode, attacker-supplied input reaches a file path that is not sufficiently validated before the file is deleted, giving arbitrary deletion rather than read or write. WordPress plugins run with the web server's file-system privileges, so deleting a bootstrap-relevant file such as wp-config.php causes WordPress to fall back to its setup routine and allows re-configuration of the database connection - a standard step toward remote code execution and site takeover. The CVSS vector confirms network reachability with no privileges (PR:N) and no user interaction (UI:N), while confidentiality impact is rated none because the primitive is deletion only; the affected product is identified in the CPE dictionary as e4jvikwp:vikappointments_services_booking_calendar with a wildcard version, consistent with the vendor statement that every release through 1.2.21 is vulnerable. A comparison of the 1.2.19 and 1.2.21 tagged sources in the referenced Trac links shows the file-handling code that remained unchanged up to the last affected release.

Know when Vikappointments Services Booking Calendar gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
vuln.today AI 9.1 CRITICAL

Remote unauthenticated traversal (AV:N/PR:N/UI:N); arbitrary deletion gives I:H and A:H, no direct read so C:N; the non-default File-field precondition is environmental, not attacker complexity, so AC:L retained.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

The VikAppointments Services Booking Calendar WordPress plugin (up to version 1.2.21) contains a critical unauthenticated file deletion flaw (CVE-2026-87115) that could allow attackers to delete wp-config.php and achieve full site takeover, disrupting booking operations and potentially exposing customer data. This affects any organization using the plugin with custom File-type booking fields enabled, a non-default configuration. No vendor-released patch is identified at time of analysis, and no public exploit has been identified, so leadership should prioritize immediate risk mitigation to protect brand trust and operational continuity.

Business Impact: High
Compensating Controls

No vendor patch available; interim mitigations include: disable or uninstall the plugin if not essential, remove or disable File-type custom fields on the confirmation-page shortcode, implement WAF rules to block malicious file path parameters, restrict file system permissions on critical files such as wp-config.php, ensure isolated backups, and monitor file integrity for unexpected deletions.

Threat Intelligence Overview

EPSS Score
0.9%
Top 42% exploitable
Prevalence
Low
niche WordPress appointment-booking plugin with limited install base
Social Media
5
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.9%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

47
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy