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-2024-13509: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in westguard WS Form LITE – Drag & Drop Contact Form Builder for WordPress

0
High
VulnerabilityCVE-2024-13509cvecve-2024-13509cwe-79
Published: Tue Jan 28 2025 (01/28/2025, 06:38:42 UTC)
Source: CVE Database V5
Vendor/Project: westguard
Product: WS Form LITE – Drag & Drop Contact Form Builder for WordPress

Description

CVE-2024-13509 is a high-severity stored Cross-Site Scripting (XSS) vulnerability in the WS Form LITE – Drag & Drop Contact Form Builder for WordPress plugin, affecting all versions up to 1. 10. 13. The vulnerability arises from improper input sanitization and output escaping of the 'url' parameter, allowing unauthenticated attackers to inject malicious scripts that execute when users view the affected pages. This can lead to theft of sensitive information, session hijacking, or unauthorized actions performed on behalf of users. The issue is partially fixed in version 1. 10. 13 and fully resolved in 1. 10. 14.

AI-Powered Analysis

AILast updated: 02/25/2026, 23:56:39 UTC

Technical Analysis

CVE-2024-13509 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, found in the WS Form LITE – Drag & Drop Contact Form Builder plugin for WordPress. The flaw exists due to insufficient sanitization and escaping of the 'url' parameter in the plugin's web page generation process. This allows unauthenticated attackers to inject arbitrary JavaScript code that is stored persistently and executed in the browsers of users who access the compromised pages. The vulnerability affects all plugin versions up to and including 1.10.13, with a partial fix introduced in 1.10.13 and a complete fix in 1.10.14. The CVSS v3.1 base score is 7.2, reflecting a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and a scope change. The impact includes potential confidentiality and integrity breaches, such as session hijacking, credential theft, or unauthorized actions performed via the victim's browser context. No known exploits are reported in the wild yet, but the ease of exploitation and the widespread use of WordPress and this plugin increase the risk. The vulnerability is particularly critical because it requires no authentication or user interaction, making automated exploitation feasible. The plugin is popular among WordPress users for building contact forms, thus affecting a broad user base.

Potential Impact

The vulnerability enables attackers to execute arbitrary scripts in the context of affected websites, potentially leading to theft of user credentials, session tokens, or other sensitive data. It can also facilitate phishing attacks, unauthorized actions on behalf of users, and distribution of malware. For organizations, this can result in data breaches, loss of customer trust, regulatory penalties, and reputational damage. Since the vulnerability is exploitable without authentication or user interaction, automated mass exploitation campaigns could emerge, increasing the threat surface. Websites relying on this plugin for contact forms are particularly at risk, including e-commerce, corporate, and government sites that use WordPress. The scope of impact is broad due to WordPress's global popularity and the plugin's user base. Although availability is not directly affected, the indirect consequences of data compromise and trust erosion can be severe.

Mitigation Recommendations

Organizations should immediately verify their WS Form LITE plugin version and upgrade to version 1.10.14 or later, where the vulnerability is fully patched. If upgrading is not immediately possible, temporarily disabling the plugin or removing the vulnerable contact forms can reduce risk. Implementing a Web Application Firewall (WAF) with rules to detect and block malicious payloads targeting the 'url' parameter can provide interim protection. Regularly audit and sanitize user inputs and outputs in custom WordPress plugins and themes to prevent similar issues. Employ Content Security Policy (CSP) headers to restrict script execution origins, mitigating impact if exploitation occurs. Monitor web server logs for suspicious requests targeting the vulnerable parameter. Educate site administrators on the importance of timely plugin updates and vulnerability management. Finally, conduct security testing on WordPress sites to detect residual XSS or other injection flaws.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-01-17T14:13:37.548Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6e5cb7ef31ef0b59eecb

Added to database: 2/25/2026, 9:49:16 PM

Last enriched: 2/25/2026, 11:56:39 PM

Last updated: 2/26/2026, 8:59:27 AM

Views: 3

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats