dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-11580

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 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.17 does not perform a per-object capability check in its post-duplication AJAX action, allowing users with Contributor-level access or above to duplicate any post (regardless of owner, post type, or status) into a published post they own and read its private post metadata, including secrets stored by other Kali Forms — Contact Form & Drag-and-Drop Builder WordPress plugin before 2.4.17.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Kali Forms WordPress plugin. The post-duplication AJAX action lacks per-object capability checks, allowing any user with Contributor-level permissions or higher to duplicate arbitrary posts (regardless of ownership, post type, or status) and read their private metadata, including sensitive plugin-stored secrets.

MitigationUpdate Kali Forms plugin to version 2.4.17 or later which implements proper per-object capability validation for the duplication action.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/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. Confirm Kali Forms plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Kali Forms' in the list. Alternatively, check the wp-content/plugins/ directory for a folder named 'kaliforms' or check the database wp_options table for options containing 'kaliforms'.
    Affected if Kali Forms plugin is present in the WordPress installation
  2. Identify installed Kali Forms version
    In WordPress admin > Plugins > Installed Plugins, find Kali Forms and note the version number displayed below the plugin name. If not visible in admin, check the main plugin file (usually kaliforms.php) in wp-content/plugins/kaliforms/ for the 'Version:' header comment.
    Affected if Version is lower than 2.4.17 (the fixed release)
  3. Verify Contributor-level or higher users exist
    In WordPress admin > Users, review the list of users. Check if any users are assigned the 'Contributor' role or higher (Author, Editor, Administrator). Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'contributor', 'author', 'editor', or 'administrator'.
    Affected if At least one user with Contributor-level or higher permissions exists in the WordPress site
  4. Check if AJAX actions are accessible (optional validation)
    WordPress AJAX actions are typically at /wp-admin/admin-ajax.php. The vulnerable endpoint relates to post duplication functionality. For manual verification, examine plugin code for AJAX handlers handling 'duplicate' or 'kaliforms_duplicate' actions and verify if they perform post ownership checks before allowing duplication.
    Affected if The plugin handles post duplication AJAX requests without validating that the requesting user owns the target post

A WordPress site is affected if Kali Forms plugin versions before 2.4.17 are installed AND at least one user with Contributor-level or higher permissions exists, allowing unauthorized post duplication and metadata access.

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.17 or later which implements proper per-object capability validation for the duplication action.

Recommended fix High confidence

Kali Forms plugin version 2.4.17 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Kali Forms — Contact Form & Drag-and-Drop Builder
  4. If an update is available, click 'Update Now' to update to version 2.4.17 or later
  5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org/plugins/kali-forms
  6. Verify the plugin version is 2.4.17 or higher after updating

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 / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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