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-13140: CWE-352 Cross-Site Request Forgery (CSRF) in devsoftbaltic SurveyJS: Drag & Drop WordPress Form Builder to create, style and embed multiple forms of any complexity

0
Medium
VulnerabilityCVE-2025-13140cvecve-2025-13140cwe-352
Published: Tue Dec 02 2025 (12/02/2025, 06:40:25 UTC)
Source: CVE Database V5
Vendor/Project: devsoftbaltic
Product: SurveyJS: Drag & Drop WordPress Form Builder to create, style and embed multiple forms of any complexity

Description

The SurveyJS: Drag & Drop WordPress Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.12.20. This is due to missing nonce validation on the SurveyJS_DeleteSurvey AJAX action. This makes it possible for unauthenticated attackers to delete surveys via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

AI-Powered Analysis

AILast updated: 12/02/2025, 06:59:02 UTC

Technical Analysis

The vulnerability CVE-2025-13140 affects the SurveyJS: Drag & Drop WordPress Form Builder plugin, which is widely used to create and embed complex forms in WordPress sites. The issue is a Cross-Site Request Forgery (CSRF) vulnerability classified under CWE-352, caused by the absence of nonce validation on the AJAX action SurveyJS_DeleteSurvey. Nonce validation is a security mechanism used in WordPress to verify that requests are intentional and originate from legitimate users. Without this protection, attackers can craft malicious links or web pages that, when visited or clicked by an authenticated site administrator, trigger the deletion of surveys without their consent. The vulnerability does not require the attacker to be authenticated, but it does require the administrator to interact with the malicious content (user interaction). The impact is limited to the integrity of survey data, as attackers can delete surveys, potentially disrupting business processes or data collection efforts. Confidentiality and availability are not directly impacted. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) reflects that the attack can be launched remotely with low complexity, no privileges required, but requires user interaction and affects integrity only. No patches or exploits are currently publicly available, but the vulnerability is published and should be addressed promptly to prevent exploitation.

Potential Impact

For European organizations, the primary impact is the potential loss or manipulation of survey data, which can affect decision-making, customer feedback collection, and compliance reporting. Organizations relying on SurveyJS forms for regulatory data collection or customer interactions may face operational disruptions and reputational damage if surveys are deleted unexpectedly. While the vulnerability does not expose sensitive data directly, the integrity loss can undermine trust in the data and lead to additional costs for data recovery or re-collection. Since the attack requires administrator interaction, social engineering risks increase, necessitating heightened awareness among staff. The impact is more pronounced in sectors with heavy reliance on digital forms, such as public administration, healthcare, and market research firms across Europe.

Mitigation Recommendations

1. Monitor for updates from devsoftbaltic and apply patches immediately once available to address nonce validation issues. 2. Implement manual nonce validation on the SurveyJS_DeleteSurvey AJAX action if patching is delayed, by customizing the plugin or using WordPress hooks to enforce nonce checks. 3. Educate WordPress administrators and site managers about the risks of clicking unknown or suspicious links, especially when logged into administrative accounts. 4. Employ Content Security Policy (CSP) headers and SameSite cookie attributes to reduce CSRF risks. 5. Regularly audit WordPress plugins for security compliance and minimize the use of unnecessary plugins. 6. Use multi-factor authentication (MFA) for WordPress admin accounts to reduce the risk of account compromise. 7. Implement web application firewalls (WAF) with CSRF protection rules to detect and block suspicious requests targeting AJAX endpoints.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-13T18:51:13.288Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 692e8e125ae71122647f9691

Added to database: 12/2/2025, 6:58:26 AM

Last enriched: 12/2/2025, 6:59:02 AM

Last updated: 12/2/2025, 10:18:01 AM

Views: 9

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats