Skip to main content
Vulnerability Database/CVE-2024-13452

CVE-2024-13452: Contact Form by Supsystic CSRF Vulnerability

CVE-2024-13452 is a Cross-Site Request Forgery flaw in Contact Form by Supsystic plugin for WordPress that enables attackers to modify settings and inject malicious scripts. This article covers technical details, affected versions, impact analysis, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2024-13452 Overview

CVE-2024-13452 is a Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form by Supsystic plugin for WordPress. The flaw affects all versions up to and including 1.7.29. The plugin's saveAsCopy function lacks proper nonce validation, enabling unauthenticated attackers to forge requests that modify plugin settings. Successful exploitation can inject malicious web scripts into the affected site, chaining CSRF with stored Cross-Site Scripting (XSS) [CWE-79]. Exploitation requires tricking a site administrator into clicking a crafted link or visiting an attacker-controlled page while authenticated.

Critical Impact

Attackers can inject persistent JavaScript into WordPress sites running the vulnerable plugin, enabling session theft, administrator account takeover, or redirection of site visitors to malicious infrastructure.

Affected Products

  • Contact Form by Supsystic plugin for WordPress, versions ≤ 1.7.29
  • WordPress sites with the vulnerable plugin activated
  • Administrator sessions authenticated to affected WordPress installations

Discovery Timeline

  • 2025-04-16 - CVE-2024-13452 published to the National Vulnerability Database (NVD)
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-13452

Vulnerability Analysis

The vulnerability resides in the saveAsCopy function within the plugin's forms model. WordPress conventionally requires nonce tokens generated by wp_create_nonce() and validated with check_admin_referer() or wp_verify_nonce() to protect state-changing actions. The affected function either omits this check or implements it incorrectly.

Without nonce validation, the endpoint accepts any authenticated request regardless of origin. An attacker crafts a page containing an auto-submitting form or image tag that targets the vulnerable action. When an authenticated administrator visits the attacker's page, the browser transmits session cookies with the forged request, and WordPress processes the action under the administrator's context.

Because the request updates form settings that render on public pages, an attacker can inject arbitrary JavaScript into stored configuration values. The injected payload executes in the context of every subsequent visitor, converting a one-shot CSRF into persistent script execution.

Refer to the WordPress Plugin Code Review for the vulnerable function source and the Wordfence Vulnerability Report for the full analysis.

Root Cause

The root cause is missing or incorrect nonce validation on the saveAsCopy function. WordPress's CSRF defense relies on nonces bound to the user session and action. The plugin fails to enforce this control, leaving the settings-update path reachable from any origin capable of triggering an administrator's browser.

Attack Vector

Exploitation is network-based and requires user interaction. The attacker hosts a malicious page or embeds a crafted link in email, chat, or comments. When a logged-in administrator activates the trigger, the browser issues a forged request to the WordPress site. The plugin processes the settings update and stores attacker-supplied JavaScript, which then executes for site visitors and staff.

The vulnerability requires no attacker authentication, only successful social engineering of an administrator.

Detection Methods for CVE-2024-13452

Indicators of Compromise

  • Unexpected modifications to Contact Form by Supsystic form settings, templates, or copied form entries in the WordPress database
  • HTML or <script> tags stored in plugin configuration fields that normally hold plain text
  • Administrator-context HTTP POST requests to the plugin's admin-ajax handler originating from external Referer headers
  • Outbound requests from site visitors to unfamiliar domains after loading pages that render the affected forms

Detection Strategies

  • Review WordPress access logs for POST requests to admin-ajax.php or admin-post.php invoking the saveAsCopy action where the Referer header does not match the site's own domain
  • Query the wp_options and plugin-specific tables for stored values containing <script, onerror=, or javascript: substrings
  • Compare plugin configuration snapshots against a known-good baseline to identify unauthorized changes

Monitoring Recommendations

  • Enable WordPress audit logging to record plugin setting changes with acting user, source IP, and timestamp
  • Deploy a Web Application Firewall (WAF) rule that flags cross-origin POST requests to WordPress admin endpoints
  • Alert on new script content served from pages hosting Supsystic contact forms

How to Mitigate CVE-2024-13452

Immediate Actions Required

  • Update the Contact Form by Supsystic plugin to a version later than 1.7.29 that includes the fix from WordPress Changeset 3267149
  • Audit existing form configurations for injected scripts and remove any unauthorized content
  • Rotate administrator credentials and invalidate active sessions if suspicious settings changes are found

Patch Information

The vendor addressed the vulnerability in the changeset published at WordPress Changeset 3267149, which adds nonce validation to the affected function. Administrators should upgrade through the WordPress plugin dashboard or by replacing the plugin directory with the patched release.

Workarounds

  • Deactivate the Contact Form by Supsystic plugin until the patched version is installed
  • Restrict WordPress administrator accounts to browsers not used for general web browsing to reduce CSRF exposure
  • Deploy a WAF policy requiring a matching Origin or Referer header for POST requests to wp-admin endpoints
  • Enforce Content Security Policy (CSP) headers that block inline script execution on pages rendering plugin output

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.