Wp Contact FormWordPress extension · Ftwr
CVE-2024-24929
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Ryan Duff, Peter Westwood WP Contact Form.This issue affects WP Contact Form: from n/a through 1.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the WP Contact Form plugin allows attackers to induce authenticated users to perform unintended actions by tricking their browsers into submitting malicious requests. The CVSS 8.8 score indicates significant potential impact on confidentiality and integrity.
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
Wp Contact FormWordPress extension
<= 1.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Locate WP Contact Form plugin installationCheck the wp-content/plugins/ directory for a folder named 'wp-contact-form', 'ftwr-wp-contact-form', or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Contact Form' or 'Ftwr Wp Contact Form'.Affected if The plugin is installed in the WordPress plugins directory.
-
Identify installed plugin versionIn WordPress admin, click on the plugin from the Plugins list to view details, or inspect the plugin's main PHP file header for 'Version:' comment, or check the readme.txt file in the plugin folder.Affected if The reported version is 1.6 or lower.
-
Inspect form submissions for missing CSRF tokensExamine the PHP source code of the plugin's form handling files (typically in the main plugin file or a file handling form submissions). Look for state-changing operations like saving settings, sending emails, or updating options. Check if these operations include any token validation, nonce checks, or referer validation.Affected if Form processing code lacks wp_nonce_verify, check_admin_referer, or any token/Nonce validation before processing requests.
-
Verify SameSite cookie attributesReview the plugin's code that sets cookies or sessions. Look for setcookie() calls or cookie headers. Check if the SameSite attribute is set to 'Strict' or 'Lax', or if it is missing entirely.Affected if Cookies related to the plugin do not specify SameSite=Strict or SameSite=Lax, or no cookie-based session handling exists.
A user is affected if the WP Contact Form plugin (version 1.6 or lower) is installed and its form-processing code lacks anti-CSRF token validation (nonces) and proper SameSite cookie attributes.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and configure SameSite cookie attributes to prevent cross-origin request forgery.
Fix this in Wp Contact Form
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24929 — 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-24929 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