CVE-2025-6059

Seraphinite Accelerator <= 2.27.21 - Cross-Site Request Forgery to Multiple Administrative Actions

2025-04-29 00:00
Nabil Irawan

Strategic Overview

Status
Patched in 2.27.22
Affected Plugin
Seraphinite Accelerator
Affected Version
<= 2.27.21
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-6059
View all Seraphinite Accelerator vulnerabilities

At a glance

CVE-2025-6059 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Seraphinite Accelerator WordPress plugin, affecting versions <= 2.27.21. 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 2.27.22; sites on affected versions should update now. Disclosed April 2025, reported by Nabil Irawan.

Vulnerability Overview

The Seraphinite Accelerator plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.27.21. This is due to missing or incorrect nonce validation on the 'OnAdminApi_CacheOpBegin' function. This makes it possible for unauthenticated attackers to perform several administrative actions, including deleting the cache, via a forged request 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)

Seraphinite Accelerator <= 2.27.21 carries this weakness at OnAdminApi_CacheOpBegin, and reaching it 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 Seraphinite Accelerator the fix is 2.27.22: builds <= 2.27.21 are affected, anything from 2.27.22 onward is not.

Remediation

Update to version 2.27.22, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-6059https://www.wordfence.com/threat-intel/vulnerabilities/id/f711c9d0-aa56-4e4c-bbcf-afa9598c3518https://nvd.nist.gov/vuln/detail/CVE-2025-6059

Related records

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