dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-2599

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.4.7 via deserialization of untrusted input in the 'download_csv' function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

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 Database for Contact Form 7, WPforms, Elementor forms plugin for WordPress is vulnerable to PHP Object Injection via deserialization of untrusted input in the 'download_csv' function. Unauthenticated attackers can inject PHP objects through this deserialization flaw. While no POP chain exists in the plugin itself, exploitation is possible if other plugins or themes containing POP chains are installed on the target WordPress site.

MitigationUpdate the plugin to a version beyond 1.4.7 when a patched release becomes available. Until then, consider disabling the plugin or implementing web application firewall rules to block requests to the vulnerable 'download_csv' endpoint.

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
High
Integrity
High
Availability
High

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

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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Database for Contact Form 7, WPforms, Elementor forms' or check the plugin files in /wp-content/plugins/ for a folder containing these form plugins
    Affected if The plugin is not found in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin_plugins list, view the plugin details to see the version number, or read the main plugin PHP file header for the 'Version' tag
    Affected if The installed version is 1.4.7 or lower (or if no version is displayed and the plugin appears unpatched)
  3. Verify the vulnerable download_csv endpoint exists
    Check if the file handling the 'download_csv' action exists in the plugin directory, typically in includes/admin or similar paths, and examine if it contains unserialize() calls on user input
    Affected if The endpoint is present and contains unserialize() on $_GET, $_POST, or $_REQUEST parameters without prior sanitization
  4. Confirm the endpoint is accessible to unauthenticated users
    Test accessing the AJAX endpoint (usually /wp-admin/admin-ajax.php?action=download_csv) without logging in, or check the plugin code for capability checks before the deserialization logic
    Affected if The endpoint can be reached without authentication and performs deserialization on request parameters

The environment is affected if the plugin is installed with version 1.4.7 or lower AND the download_csv function processes unserialize() on unauthenticated request parameters, especially if other plugins with POP chains are present.

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 a version beyond 1.4.7 when a patched release becomes available. Until then, consider disabling the plugin or implementing web application firewall rules to block requests to the vulnerable 'download_csv' endpoint.

Recommended fix High confidence

Upgrade to version 1.4.8 or later of the Form Data plugin

  1. Identify the plugin: The vulnerable plugin is 'Form Data - Database for Contact Form 7, WPforms, Elementor forms' from wordpress.org/plugins/form-data/
  2. Navigate to WordPress admin dashboard > Plugins
  3. Locate 'Form Data - Database for Contact Form 7, WPforms, Elementor forms' in the installed plugins list
  4. Check current installed version - if it is 1.4.7 or below, the site is vulnerable
  5. Update the plugin to the latest available version (1.4.8 or later)
  6. Verify the update was successful by confirming the new version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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