CVE-2025-49856

Responsive Plus <= 3.2.2 - Cross-Site Request Forgery to Settings Update

2025-06-12 00:00
Chazz Wolcott

Strategic Overview

Status
Patched in 3.2.3
Affected Plugin
Responsive Starter Templates – Elementor Templates & Starter Sites
Affected Version
<= 3.2.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-49856
View all Responsive Starter Templates – Elementor Templates & Starter Sites vulnerabilities

At a glance

CVE-2025-49856 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Responsive Starter Templates WordPress plugin, affecting versions <= 3.2.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.3; sites on affected versions should update now. Disclosed June 2025, reported by Chazz Wolcott.

Vulnerability Overview

The Responsive Plus – Starter Templates, Advanced Features and Customizer Settings for Responsive Theme. plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.2.2. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update plugin settings granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Responsive Starter Templates <= 3.2.2 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Responsive Starter Templates the fix is 3.2.3: builds <= 3.2.2 are affected, anything from 3.2.3 onward is not.

Remediation

Update to version 3.2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Responsive Starter Templates: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Responsive Starter Templates 3.2.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-49856https://www.wordfence.com/threat-intel/vulnerabilities/id/70eff082-be02-471e-9ee6-42a1234009b2https://nvd.nist.gov/vuln/detail/CVE-2025-49856

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C