dbcve.org
VulnerabilityAwaiting classification

CVE-2026-11581

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable 8 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 WordPress plugin before 2.4.13 does not sanitise a form field's caption before outputting it as a column header on the administrator form-entries screen, allowing users with Contributor-level access or above to store JavaScript that executes in an administrator's session. A missing capability check in the Kali Forms — Contact Form & Drag-and-Drop Builder WordPress plugin before 2.4.13's post-duplication action additionally lets the Contributor publish the malicious form so an administrator renders it.

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

Stored XSS vulnerability in Kali Forms WordPress plugin before 2.4.13 allows Contributor+ users to inject malicious JavaScript into form field captions, which executes when administrators view the form-entries screen. Additionally, a missing capability check in the post-duplication action permits Contributors to publish malicious forms.

MitigationUpdate Kali Forms plugin to version 2.4.13 or later to obtain the fix that adds proper sanitization of form field captions and implements capability checks on duplication actions.

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
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify if Kali Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Kali Forms' in the list, or check the plugin files in /wp-content/plugins/kali-forms/ for the main plugin file to read the version header
    Affected if Kali Forms plugin is present on the WordPress site
  2. Determine the installed version of Kali Forms
    Read the plugin version from the plugin header in the main Kali Forms file (e.g., kali-forms.php) or from the Plugins page in WordPress admin
    Affected if The version number is lower than 2.4.13 (e.g., 2.4.12, 2.4.10, etc.)
  3. Verify if Contributor or higher role users exist
    Go to Users > All Users in WordPress admin and check for any users assigned the Contributor, Author, Editor, or Administrator role
    Affected if At least one user with Contributor or higher role exists on the site
  4. Check for existing forms with custom field captions
    Navigate to Kali Forms in the admin panel and review any created forms; inspect form field settings to see if custom captions have been defined
    Affected if Forms exist with custom field captions that could contain injected scripts

A site is affected if Kali Forms plugin version is below 2.4.13 AND at least one Contributor+ user exists who could inject malicious JavaScript into form field captions that would execute when administrators view form entries.

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 Kali Forms plugin to version 2.4.13 or later to obtain the fix that adds proper sanitization of form field captions and implements capability checks on duplication actions.

Recommended fix Moderate confidence

Kali Forms version 2.4.13 or latest stable release

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Kali Forms — Contact Form & Drag-and-Drop Builder'
  4. Check the current version installed
  5. If the version is below 2.4.13, click 'Update Now' to upgrade to version 2.4.13 or latest available
  6. Verify the update completed successfully
  7. Review any recently added users with Contributor access for suspicious activity
  8. Clear any cached data if a caching plugin is in use

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11581 — 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-11581 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