Skip to main content

Kali Forms CVE-2026-59542

| EUVDEUVD-2026-48195 HIGH
Path Traversal (CWE-22)
2026-07-23 Patchstack GHSA-f785-j866-927f
7.7
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Register or obtain Subscriber account
  2. Delivery
    Call plugin file-deletion handler
  3. Exploit
    Inject path traversal (../wp-config.php)
  4. Execution
    Delete arbitrary server file
  5. Impact
    Site outage / denial of service

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

Requires an authenticated session at Subscriber level or higher (CVSS PR:L), so the practical prerequisite is either that the target site has open user registration enabled - allowing anyone to self-provision a Subscriber account - or that the attacker already holds any low-privilege credential. The vulnerable code path is the Kali Forms file-deletion functionality, reachable over the network (AV:N) with no user interaction and low attack complexity. Limiting factors: the attack cannot be performed fully unauthenticated (a valid login is mandatory), and on sites that disable public registration and provision accounts only for vetted users the attack surface is substantially reduced; the impact is destructive (file deletion / denial of service) rather than data disclosure.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H, base 7.7 High) describes a network-reachable, low-complexity attack requiring only low privileges and no user interaction, with a scope change and High availability impact - consistent with deleting files outside the plugin's own component to disable the whole site. Real-world risk hinges primarily on one deployment factor: whether the site permits open user registration (Subscriber accounts). On registration-open sites the barrier is trivial; where accounts are provisioned only for vetted staff the attacker must first obtain any authenticated session. No EPSS score, KEV entry, or POC was supplied in the input, so exploitation probability cannot be quantified - the absence of these signals suggests this is not yet subject to mass automated exploitation, but path-traversal delete bugs in WordPress plugins are historically easy to weaponize once details are public. The impact is confined to availability (C:N/I:N/A:H): it destroys/denies rather than exfiltrates data, though deleting wp-config.php can indirectly enable a takeover-via-reinstall path in some scenarios.

Exploit ScenarioDerived

An attacker registers a free Subscriber account (or uses any existing low-privilege login) on a WordPress site running Kali Forms <= 2.4.18, then sends a crafted authenticated request to the plugin's file-deletion handler with a traversal path such as ../../../wp-config.php. The server deletes the targeted file, taking the site offline or forcing it into a fresh-install state. No public exploit code is identified in the source data, but the low complexity (AC:L) and lack of required user interaction make weaponization straightforward.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.4% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 23, 2026

Arbitrary file deletion in the Kali Forms WordPress plugin (versions 2.4.18 and earlier) lets a low-privileged authenticated user - as low as a Subscriber - delete arbitrary files on the server via path traversal. On sites that allow open registration, an attacker can self-provision an account and remove critical files such as wp-config.php, knocking the site offline or forcing it into a fresh-install state. Reported by Patchstack; no public exploit identified at time of analysis and not listed in CISA KEV.

RemediationAI

Update Kali Forms to the first fixed release above 2.4.18 as published by the vendor; the exact patched version is not included in the provided data, so consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/kali-forms/vulnerability/wordpress-kali-forms-plugin-2-4-18-arbitrary-file-deletion-vulnerability) and the plugin changelog on WordPress.org to confirm the fixed version before deploying. Until patched, disable open user registration (Settings > General > uncheck 'Anyone can register') so untrusted accounts cannot reach the vulnerable authenticated action - trade-off: blocks legitimate self-service signup. As additional compensating controls, apply a WAF/virtual patch (Patchstack offers virtual patching) to block path-traversal payloads (../ sequences) sent to admin-ajax.php and REST routes; deactivate the Kali Forms plugin entirely if it is not business-critical (trade-off: forms stop working); and enforce least-privilege filesystem permissions for the web-server/PHP user so core files cannot be deleted, while keeping tested backups to recover from any file destruction.

Affected VersionsENISA

Kali Forms n/a ≤2.4.18

Affected Packages

euvd kali_forms 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

Kali Forms is a drag-and-drop form-builder plugin for WordPress (vendor namespace wp_chill / WP Chill) used to create contact, subscription, and payment forms. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal): a file-handling routine - typically a form attachment/upload deletion handler exposed through admin-ajax.php or the WordPress REST API - accepts a user-controlled filename or path and passes it to a filesystem delete operation without normalizing or constraining it to the intended directory. By supplying traversal sequences (e.g. ../../), the caller escapes the plugin's upload directory and deletes files anywhere the PHP/web-server process can write, including WordPress core files. The CPE cpe:2.3:a:wp_chill:kali_forms:*:*:*:*:*:*:*:* confirms all versions up to and including 2.4.18 are in scope.

Know when Kali Forms 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 (Patchstack) PRIMARY 7.7 HIGH
AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
vuln.today AI 7.7 HIGH

Network-reachable authenticated action (PR:L for a Subscriber), low complexity, no user interaction; deleting files outside the plugin (e.g. wp-config.php) justifies S:C and A:H with no confidentiality or integrity impact.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Subscriber Arbitrary File Deletion in Kali Forms <= 2.4.18 versions.

Executive ViewAI

Why It Matters

Kali Forms WordPress plugin versions 2.4.18 and earlier contain a file deletion vulnerability allowing low-privilege authenticated users to remove critical system files including wp-config.php, rendering affected sites inoperative. Organizations running this plugin without immediate remediation face complete site outages and business continuity disruption, particularly those permitting open user registration.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable Kali Forms plugin entirely if alternative exists or functionality not business-critical; (2) Restrict filesystem permissions on wp-config.php, .htaccess, wp-settings.php to read-only for web server processes; (3) Disable public user registration on WordPress; (4) Configure user role management to prevent Subscriber accounts from accessing file management functionality; (5) Deploy file integrity monitoring (e.g., AIDE, Tripwire) to detect unauthorized file deletions in real-time; (6) Maintain validated backup and restore procedures with regular testing to ensure rapid recovery capability.

Threat Intelligence Overview

EPSS Score
0.4%
Top 63% exploitable
Prevalence
Medium
moderately popular WordPress form-builder plugin, tens of thousands of installs
Data Quality
4 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 HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
No
Human Impact
High
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
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.

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