Builder For Contact Form 7WordPress extension · Planetstudio
CVE-2025-28864
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 planetstudio Builder for Contact Form 7 by Webconstruct cf7-builder allows Cross Site Request Forgery.This issue affects Builder for Contact Form 7 by Webconstruct: from n/a through <= 1.2.2.
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 · moderate confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in the planetstudio Builder for Contact Form 7 WordPress plugin (versions up to 1.2.2). The plugin fails to properly validate the origin of requests, allowing attackers to trick authenticated administrators into performing unintended actions such as modifying plugin settings or submitting/altering form data.
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
Builder For Contact Form 7WordPress extension
<= 1.2.2CVSS 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.
-
Confirm plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate 'planetstudio Builder for Contact Form 7'. Check the version number listed under the plugin name.Affected if The installed version is 1.2.2 or lower.
-
Identify plugin admin AJAX handlersAccess the plugin directory via file manager or FTP (wp-content/plugins/planetstudio-builder-cf7 or similar naming). Search for files containing 'add_action' calls with 'wp_ajax' or 'wp_ajax_nopriv' hooks.Affected if The plugin registers AJAX endpoints without associated nonce verification logic.
-
Inspect form handling for nonce validationExamine PHP files that process form submissions (typically in main plugin file or handler classes). Look for calls to 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' within functions that handle settings changes or form data submissions.Affected if Form processing functions lack nonce verification or only perform superficial checks without validating the request origin.
-
Check referer header validationReview the same form handling code for server-side validation of '$_SERVER[HTTP_REFERER]' or '$_SERVER[HTTP_ORIGIN]' headers before processing any admin actions or form submissions.Affected if The plugin does not validate the referer or origin header to confirm the request originated from the expected domain.
You are affected if the planetstudio Builder for Contact Form 7 plugin version is 1.2.2 or lower and the plugin handles admin actions or form submissions without verifying nonces or validating request origins.
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 (nonces) on all form submissions and AJAX endpoints within the plugin, and validate the referer header or origin header on server-side operations.
Fix this in Builder For Contact Form 7
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-2025-28864 — 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-2025-28864 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