dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9107

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Kali Forms — Contact Form & Drag-and-Drop Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'meta[kaliforms_field_components]' parameter in all versions up to, and including, 2.4.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Kali Forms WordPress plugin fails to properly sanitize and escape the 'meta[kaliforms_field_components]' parameter, allowing authenticated users with contributor-level access or higher to inject malicious JavaScript code that persists in the database and executes when other users view affected pages.

MitigationUpdate the plugin to version 2.4.14 or later, which includes proper input sanitization and output escaping for the affected parameter. Until then, review user permissions and audit existing form submissions for malicious content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Kali Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate Kali Forms, or check the /wp-content/plugins/kaliforms/ directory for the main plugin file and read its version header
    Affected if Kali Forms plugin is present in the WordPress installation
  2. Determine installed plugin version
    Read the Version line from the plugin header in kaliforms.php or view the version displayed in the WordPress plugins list
    Affected if Version is lower than 2.4.14 (vulnerable versions)
  3. Identify users with contributor-level access or higher
    Go to Users > All Users in WordPress admin and filter by roles: Administrator, Editor, Author, Contributor. Check for any users with these roles who could access the plugin's form builder
    Affected if Any user account with contributor, author, editor, or administrator role exists in the system
  4. Inspect database for malicious script content in form data
    Query the WordPress database tables (typically wp_options, wp_postmeta, or plugin-specific tables with 'kaliforms' prefix) for the meta key 'kaliforms_field_components' and examine stored values for unescaped HTML script tags, event handlers (onload, onerror, onclick), or suspicious JavaScript patterns
    Affected if Database contains entries in meta[kaliforms_field_components] with raw <script> tags, javascript: URIs, or unescaped HTML attributes like onerror/onload
  5. Check if form submissions or previews are publicly accessible
    Navigate to any published form created with Kali Forms, or access form preview URLs (/?kaliforms_preview=... or similar). Examine if injected scripts execute in the browser when viewing the form page as a non-authenticated user
    Affected if Form pages render and stored XSS payloads execute when viewed by other users

You are affected if Kali Forms plugin versions below 2.4.14 are installed AND any user with contributor-level or higher access exists AND malicious scripts are already present in the database or could be injected via the vulnerable parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 2.4.14 or later, which includes proper input sanitization and output escaping for the affected parameter. Until then, review user permissions and audit existing form submissions for malicious content.

Recommended fix Moderate confidence

Kali Forms version 2.4.14 or later

  1. 1. Update the Kali Forms plugin to version 2.4.14 or later
  2. 2. After updating, verify the fix by checking that the meta[kaliforms_field_components] parameter is properly sanitized when saving form components
  3. 3. Review user roles and permissions to ensure only trusted users have contributor-level or higher access to form editing

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9107 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9107 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data