Admin Side Data Storage For Contact Form 7WordPress extension · Zestard
CVE-2024-1778
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 · uneditedThe 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_bookmark() function in all versions up to, and including, 1.1.1. This makes it possible for unauthenticated attackers to alter bookmark statuses.
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 confidenceThe Contact Form 7 plugin for WordPress contains a Missing Authorization vulnerability in versions up to 1.1.1. The zt_dcfcf_change_bookmark() function lacks a capability check, allowing unauthenticated attackers to modify bookmark statuses in the admin-side data storage.
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
<= 1.1.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin > Plugins and verify 'Zestard Admin Side Data Storage For Contact Form 7' is installed and activeAffected if the plugin is installed and active in WordPress
-
Identify installed versionIn WordPress admin > Plugins, find the plugin and view the version number displayed under the plugin nameAffected if the installed version is 1.1.1 or lower (any version up to and including 1.1.1)
-
Verify vulnerable function existsInspect plugin files (typically in wp-content/plugins/) for the function named 'zt_dcfcf_change_bookmark' - check main plugin PHP file or ajax handler filesAffected if the function zt_dcfcf_change_bookmark() exists in the plugin code
-
Check authorization on the endpointReview the plugin code where zt_dcfcf_change_bookmark is defined - look for WordPress capability checks (like current_user_can) or nonce verification before the function executesAffected if no capability check or nonce validation is found before the bookmark modification logic
-
Test unauthenticated access (optional)If safe to do in a non-production environment, send a POST request to the WordPress admin-ajax.php endpoint with the action parameter expected by zt_dcfcf_change_bookmark without authenticationAffected if the request succeeds and modifies bookmark status without authentication
If the plugin version is 1.1.1 or lower and the zt_dcfcf_change_bookmark function lacks capability checks, the site is vulnerable to unauthenticated bookmark status modification.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a version beyond 1.1.1 which includes proper authorization checks. If immediate update is not possible, restrict access to the affected endpoint at the server level.
Fix this in Admin Side Data Storage For Contact Form 7
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-1778 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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