Skip to main content

Kali Forms CVE-2026-15395

| EUVDEUVD-2026-45130 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-07-17 Wordfence GHSA-mjg8-2mjg-9rwc
7.2
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Locate page with Kali Forms shortcode
  2. Delivery
    Scrape public submission nonce
  3. Exploit
    Submit digitalSignature field with script payload
  4. Execution
    Value stored unsanitized
  5. Persist
    Admin or visitor views injected page
  6. Impact
    Script executes, hijack session or forge actions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

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

Exploitation Conditions

The target WordPress site must have a Kali Forms form published via the form shortcode that includes a 'digitalSignature' field, which is the exact injectable sink. No authentication is required (CVSS PR:N) and no attacker-side interaction is needed to plant the payload; the submission nonce that would normally gate the POST is publicly readable from any page rendering the form shortcode, so it is not a real limiting factor. The practical limiting conditions are therefore that the form must be published and reachable, it must use the digitalSignature field type, and the plugin version must be 2.4.18 or earlier; payload execution additionally requires that some user (for example an admin reviewing submissions) subsequently loads the page into which the value is reflected.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2 High) describes a remotely reachable, low-complexity, unauthenticated injection requiring no attacker-side user interaction, and the description confirms this is realistic because the required submission nonce is publicly retrievable from the shortcode-bearing page, removing the usual practical hurdle. Confidentiality and integrity impacts are Limited (session/cookie theft, defacement, admin-action forgery in the victim's browser) with no availability impact. No EPSS score, KEV entry, or SSVC decision data was provided, so probabilistic and decision-framework signals are unknown rather than low - absence of an EPSS value must not be read as low likelihood. The report originates from Wordfence, a credible WordPress-security source. One nuance to verify: the vector marks UI:N, yet execution of the stored payload still depends on a victim eventually visiting the injected page; the 'no interaction' scoring reflects that the attacker needs no interaction to plant the payload, which is Wordfence's standard convention for stored XSS. Overall this is a genuine, easily automatable web risk for internet-exposed installations rather than a high-score-but-low-reality finding, though it is not currently confirmed to be under active exploitation.

Exploit ScenarioDerived

An attacker crawls WordPress sites for pages containing a Kali Forms shortcode with a digitalSignature field, scrapes the publicly embedded submission nonce from that page, and submits the form with a script payload as the signature value. When a site administrator or visitor later opens the page that renders the stored submission, the injected JavaScript runs in their session, enabling session/cookie theft, forged admin actions, or redirection. No public exploit code is identified at time of analysis, but the low complexity and unauthenticated network vector make weaponization straightforward.

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

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

Alert me

AnalysisAIv1 – Jul 17, 2026

Stored cross-site scripting in the Kali Forms - Contact Form & Drag-and-Drop Builder plugin for WordPress (all versions through 2.4.18) lets fully unauthenticated attackers persist arbitrary JavaScript through the form's 'digitalSignature' field value, which is neither sanitized on input nor escaped on output. Because the form-submission nonce is exposed on any page rendering the form shortcode, the normal anti-CSRF barrier provides no protection, and the injected script executes in the browser of any user (including administrators) who later views the affected page. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the low attack complexity and lack of authentication make it a practical scan-and-spray candidate.

RemediationAI

Upstream fix available (PR/commit); released patched version not independently confirmed - the fix is present in the WordPress plugin repository changeset 3609303 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3609303%40kali-forms&new=3609303%40kali-forms), but the input data does not state an exact tagged release, so administrators should update Kali Forms to the latest available version above 2.4.18 and verify the version string against the Wordfence advisory rather than assuming a specific number. Until a confirmed patched release is installed, compensating controls include temporarily unpublishing or shortcode-removing any forms that use the digitalSignature field (eliminates the injectable sink but disables signature capture), placing the site behind a WAF such as Wordfence with XSS rules enabled to filter script payloads in submissions (may cause false positives on legitimate signature data), and reviewing stored submissions and rendered submission pages for injected markup before administrators open them (labor-intensive and does not stop the injection itself). Consult the advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/90e39398-19d7-435d-b23f-e93b8cdbcae4?source=cve for the confirmed fixed version.

Affected VersionsENISA

Kali Forms — Contact Form & Drag-and-Drop Builder 0 ≤2.4.18

Affected Packages

euvd kali_forms_contact_form_drag_and_drop_builder 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 vulnerability lives in the plugin's frontend submission-handling code (Inc/Frontend/class-submission-shortcode.php and Inc/Frontend/class-form-processor.php, referenced around lines 88, 198, and 997 in the 2.4.17/2.4.18 sources). Kali Forms is a drag-and-drop WordPress form builder that renders forms via a shortcode; the 'digitalSignature' field type captures a signature value that is stored with the submission and later reflected into generated pages. This is a classic CWE-79 (Improper Neutralization of Input During Web Page Generation) failure: the field value is trusted end-to-end without WordPress escaping primitives such as esc_html or wp_kses on storage or on output rendering, so markup in the field survives into the DOM. The Scope:Changed CVSS flag reflects that the vulnerable component (the WordPress site/plugin) causes impact in a separate security authority - the victim's browser session and the WordPress admin context.

Know when Kali Forms Contact Form Drag And Drop Builder 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 7.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 7.2 HIGH

Unauthenticated network stored XSS with public nonce (PR:N/AC:L); scope changes to the victim browser (S:C) with limited confidentiality/integrity and no availability impact.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

DescriptionCVE.org

The Kali Forms - Contact Form & Drag-and-Drop Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'digitalSignature' Field Value in all versions up to, and including, 2.4.18 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The required form-submission nonce is publicly available on any page containing the form shortcode, making this exploitable by fully unauthenticated attackers without any precondition beyond the form being published.

Executive ViewAI

Why It Matters

The Kali Forms WordPress plugin (versions through 2.4.18) contains a stored cross-site scripting vulnerability permitting unauthenticated attackers to persistently inject malicious JavaScript into forms, which executes in the browsers of all users-including administrators-who subsequently view the affected form. This creates direct risk of website defacement, user credential harvesting, and administrative account compromise across any organization using this plugin. The combination of zero authentication barriers and low attack complexity makes this vulnerability a practical mass-exploitation candidate.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Immediately disable the plugin and revoke public access to form pages; (2) Deploy Content Security Policy headers with script-src restrictions to prevent injected script execution; (3) Implement Web Application Firewall rules to block requests containing script payloads in the digitalSignature field; (4) Enable detailed logging and real-time alerting on form submission endpoints and administrator login activity; (5) Conduct immediate forensic review of form submission records and administrator session logs for signs of prior exploitation or unauthorized account modifications.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Prevalence
Medium
moderately popular WordPress form-builder plugin, not universally deployed
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.2%
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
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

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