dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-11579

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 verify that a file upload is made against an existing form configured with a file-upload field, accepting uploads regardless of whether any such form exists, which allows unauthenticated users to upload files to the WordPress Media Library; the uploads are limited to WordPress's default-allowed MIME types, so this does not lead to code execution.

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 before 2.4.17 lacks proper validation to ensure file uploads are submitted against an existing form with a file-upload field configured. This allows unauthenticated attackers to upload arbitrary files to the WordPress Media Library, though restricted to WordPress's default-allowed MIME types, preventing code execution.

MitigationUpdate Kali Forms plugin to version 2.4.17 or later to apply the security patch that adds proper form validation for file uploads.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify Kali Forms plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Kali Forms. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header or the plugins/kaliforms directory for a version constant.
    Affected if The installed version is below 2.4.17 (e.g., 2.4.16, 2.4.15, etc.)
  2. Verify file upload fields exist in any forms
    In WordPress admin, navigate to Kali Forms > Forms and review each form. Check if any form contains a File Upload field component that has been enabled and configured.
    Affected if At least one form has an active file upload field, allowing the upload endpoint to be reachable via the vulnerable code path
  3. Confirm WordPress default MIME type restrictions
    Review WordPress allowed MIME types at Settings > Media (or via wp_get_mime_types filter). The vulnerability is limited to these default-allowed types (images, documents, videos, audio).
    Affected if Default MIME type restrictions are in place (the restriction is the only mitigating factor preventing code execution)
  4. Check for unexpected files in Media Library
    Go to Media > Library and scan for unfamiliar or suspicious file uploads that were not intentionally added, especially files with unusual extensions or from unknown dates.
    Affected if Unexpected files appear in the Media Library that correspond to the vulnerable timeframe

A user is affected if Kali Forms plugin version is below 2.4.17 AND at least one form with a file upload field exists on the site, as this combination enables the unauthenticated file upload vulnerability.

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 to apply the security patch that adds proper form validation for file uploads.

Recommended fix High confidence

Kali Forms plugin version 2.4.17

  1. Navigate to WordPress admin dashboard > Plugins
  2. Find Kali Forms — Contact Form & Drag-and-Drop Builder plugin
  3. Update the plugin to version 2.4.17 or later
  4. Verify the update was successfully applied by checking the plugin version number
  5. Optionally, review the WordPress Media Library for any unexpected file uploads that may have occurred prior to the patch

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation0.5 h
  • Testing1.0 h
  • Review / QA0.5 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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