dbcve.org
Admin Side Data Storage For Contact Form 7WordPress extension · Zestard

CVE-2024-1779

MEDIUM · 5.3 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to after 1.1.1 or later.
See remediation →
62/100
Remediation priority · Elevated
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 Admin side data storage for Contact Form 7 plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the zt_dcfcf_change_status() function in all versions up to, and including, 1.1.1. This makes it possible for unauthenticated attackers to alter the message read status of messages.

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 Contact Form 7 plugin's admin data storage has a missing capability check on the zt_dcfcf_change_status() function. This allows unauthenticated attackers to invoke this function directly and modify the read status of messages without any authorization, representing an Insecure Direct Object Reference (IDOR) vulnerability.

MitigationUpdate the plugin to the latest version which should include proper capability checks and nonce verification on the zt_dcfcf_change_status() function. Until patched, consider blocking the vulnerable endpoint via WAF rules.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Admin Side Data Storage For Contact Form 7WordPress extension
Affected:<= 1.1.1

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. Confirm plugin installation
    Check if the 'Zestard Admin Side Data Storage For Contact Form 7' plugin is installed in WordPress via Plugins page or by searching for the plugin folder in /wp-content/plugins/
    Affected if Plugin is installed and active
  2. Check installed version
    Locate the main plugin file (typically within the plugin folder named 'zt-dcfcf' or similar) and open it to find the 'Version' header in the plugin comment block, or view version via WordPress admin plugin list
    Affected if Version is 1.1.1 or lower, or version cannot be determined (indicating potentially outdated)
  3. Verify vulnerable function exists
    Search plugin source files for the function 'zt_dcfcf_change_status' - this function should exist in the plugin code
    Affected if Function 'zt_dcfcf_change_status' is found in the plugin files
  4. Check endpoint accessibility
    Test if the AJAX or admin-post endpoint that calls zt_dcfcf_change_status() is reachable without authentication by inspecting the plugin's hook registrations (look for add_action calls with 'wp_ajax_' or 'wp_ajax_nopriv_' hooks)
    Affected if The function is hooked to an action accessible to unauthenticated users (wp_ajax_nopriv_) or has no capability check
  5. Inspect function for capability check
    Open the PHP file containing zt_dcfcf_change_status and verify if the function includes a capability check (e.g., current_user_can()) or nonce verification before processing status changes
    Affected if No capability check (like current_user_can) or nonce validation is found within the function

User is affected if the Zestard Admin Side Data Storage For Contact Form 7 plugin is installed with version 1.1.1 or lower and the zt_dcfcf_change_status function lacks proper authorization checks.

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.

From vendor data
Upgrade available Upgrade to a release after 1.1.1
Interim mitigation

Update the plugin to the latest version which should include proper capability checks and nonce verification on the zt_dcfcf_change_status() function. Until patched, consider blocking the vulnerable endpoint via WAF rules.

Fix this in Admin Side Data Storage For Contact Form 7 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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-2024-1779 — 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-2024-1779 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