CVE-2025-53270

WordPress CTA <= 1.7.0 - Cross-Site Request Forgery

2025-06-27 00:00
Nguyen Xuan Chien

Strategic Overview

Status
Patched in 1.7.1
Affected Plugin
WP CTA – Call Now Button, Sticky Button & Call to Action Builder
Affected Version
<= 1.7.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-53270
View all WP CTA – Call Now Button, Sticky Button & Call to Action Builder vulnerabilities

At a glance

CVE-2025-53270 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP CTA WordPress plugin, affecting versions <= 1.7.0. 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 1.7.1; sites on affected versions should update now. Disclosed June 2025, reported by Nguyen Xuan Chien.

Vulnerability Overview

The WP CTA – Call To Action Plugin, Sticky CTA, Sticky Buttons plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.7.0. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 WP CTA <= 1.7.0 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 WP CTA the fix is 1.7.1: builds <= 1.7.0 are affected, anything from 1.7.1 onward is not.

Remediation

Update to version 1.7.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-53270https://www.wordfence.com/threat-intel/vulnerabilities/id/3586da3d-fec0-4890-8918-bc1c417e44f7https://nvd.nist.gov/vuln/detail/CVE-2025-53270

Related records

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