Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-28864: Cross-Site Request Forgery (CSRF) in planetstudio Builder for Contact Form 7 by Webconstruct

0
Unknown
VulnerabilityCVE-2025-28864cvecve-2025-28864
Published: Tue Mar 11 2025 (03/11/2025, 21:00:35 UTC)
Source: CVE Database V5
Vendor/Project: planetstudio
Product: Builder for Contact Form 7 by Webconstruct

Description

Cross-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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/01/2026, 23:27:11 UTC

Technical Analysis

CVE-2025-28864 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the planetstudio Builder for Contact Form 7 plugin by Webconstruct, affecting all versions up to 1.2.2. CSRF vulnerabilities occur when an attacker tricks an authenticated user into submitting a malicious request unknowingly, exploiting the user's active session and privileges. In this case, the plugin lacks adequate CSRF protections, such as nonce verification or token validation, allowing attackers to perform unauthorized actions like modifying form configurations or submitting data on behalf of the user. The vulnerability is specific to the Builder for Contact Form 7 plugin, a tool widely used to create and manage contact forms on WordPress websites. Although no exploits have been reported in the wild, the vulnerability's presence in a popular plugin poses a risk to many WordPress sites. The absence of a CVSS score suggests that the vulnerability was recently disclosed and not yet fully assessed. The attack requires the victim to be authenticated and visit a malicious site or click a crafted link, which means user interaction is necessary. The scope is limited to websites using the affected plugin, but the impact can include unauthorized form manipulation or data submission, potentially leading to data integrity issues or further exploitation.

Potential Impact

The primary impact of this CSRF vulnerability is unauthorized actions performed within the context of an authenticated user on websites using the vulnerable plugin. Attackers can exploit this to change form configurations, submit fraudulent data, or potentially escalate attacks by injecting malicious content or redirecting users. This can lead to data integrity issues, loss of trust, and potential exposure of sensitive information collected via forms. For organizations relying on the plugin for customer interactions, this could disrupt business processes and damage reputation. Since the vulnerability requires user authentication, the risk is somewhat mitigated but still significant for sites with multiple users or administrators. The lack of known exploits reduces immediate risk, but the widespread use of WordPress and this plugin means many sites could be targeted once exploit code becomes available. The vulnerability could also be leveraged as part of a larger attack chain, increasing its potential impact.

Mitigation Recommendations

To mitigate this vulnerability, organizations should first update the Builder for Contact Form 7 plugin to the latest version once a patch is released by the vendor. Until then, implement the following specific measures: 1) Manually verify and enforce anti-CSRF tokens or nonces in all form submissions and plugin actions to ensure requests are legitimate. 2) Restrict access to the plugin's administrative interfaces to trusted users only, using role-based access controls and IP whitelisting where possible. 3) Employ Web Application Firewalls (WAFs) with rules designed to detect and block CSRF attack patterns targeting this plugin. 4) Educate users and administrators to avoid clicking suspicious links or visiting untrusted websites while logged into the affected WordPress sites. 5) Monitor logs for unusual form submissions or configuration changes that could indicate exploitation attempts. 6) Consider temporarily disabling the plugin if it is not critical to operations until a secure version is available. These targeted actions go beyond generic advice by focusing on the plugin's specific attack surface and operational context.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-03-11T08:08:42.175Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cd72e4e6bfc5ba1deef3d0

Added to database: 4/1/2026, 7:32:52 PM

Last enriched: 4/1/2026, 11:27:11 PM

Last updated: 4/6/2026, 11:16:52 AM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses