Kali Forms <= 2.4.18 - Unauthenticated Stored Cross-Site Scripting via 'digitalSignature' Field Value
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.
Browse WordPress security risksQuick answer
Kali Forms — Contact Form & Drag-and-Drop Builder should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- up to and including 2.4.18
Fixed versions
- 2.4.19
How to fix it
Kali Forms — Contact Form & Drag-and-Drop Builder is affected by CVE-2026-15395, an unauthenticated stored cross-site scripting flaw in digital signature values. An attacker can submit script through a public Kali Forms form and run it when the stored entry is viewed. Update Kali Forms — Contact Form & Drag-and-Drop Builder to 2.4.19 or a newer vendor-supported patched release. Prioritize internet-facing and shared production systems first.
- Inventory every Kali Forms — Contact Form & Drag-and-Drop Builder deployment, version, exposed endpoint, environment, and owner.
- Confirm the installed release is not an affected version up to and including 2.4.18.
- Update Kali Forms — Contact Form & Drag-and-Drop Builder to 2.4.19 or a newer vendor-supported patched release.
- Until the update is complete, disable affected public forms or remove the digitalSignature field.
- Review relevant logs and search form submissions for scripts, SVG or event handlers, javascript or data URLs, and encoded active content.
- Purge malicious entries, clear caches, revoke exposed administrator sessions, and review actions taken after affected submissions were viewed.
- Clear WordPress, object, page, CDN, and browser caches, then update the asset inventory and close any temporary controls only after validation.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Kali Forms — Contact Form & Drag-and-Drop Builder is on the patched version or mitigation stated above and record the exact deployed version.
- Submit a harmless active-content test and confirm the digital signature value is sanitized and rendered as safe data.
- Confirm the affected WordPress REST, AJAX, form, shortcode, upload, export, or admin feature is available only to the roles and requests that need it.
- Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
- Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-15395.
Related categories
Related security risks
More published guidance from the same primary category.
CVE-2026-65475 Modula Image Gallery vulnerability
Updated July 24, 2026
highCVE-2026-65511 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
mediumCVE-2026-65522 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
Trusted references
FAQ
What is affected by CVE-2026-15395?
Kali Forms — Contact Form & Drag-and-Drop Builder versions listed as affected should be reviewed: up to and including 2.4.18.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.