CVE-2025-59572

8.8

purethemes · WorkScout-Core

A Cross-Site Request Forgery (CSRF) vulnerability in the purethemes WorkScout-Core WordPress plugin allows unauthorized actions to be performed on behalf of an authenticated user.

Executive summary

A high-severity Cross-Site Request Forgery vulnerability in the purethemes WorkScout-Core plugin could allow an attacker to perform unauthorized actions, potentially leading to total compromise.

Vulnerability

This vulnerability is a Cross-Site Request Forgery (CWE-352) that allows an unauthenticated attacker to trick a user into executing unintended actions. The lack of proper request validation enables the attacker to manipulate plugin functions via a crafted link or page.

Business impact

Successful exploitation of this CSRF vulnerability allows an attacker to perform sensitive operations without the victim's consent. Given the CVSS score of 8.8, this poses a significant risk to data integrity and system control, as an attacker could potentially modify plugin settings or perform administrative actions if a privileged user is targeted.

Remediation

Immediate Action: Update the purethemes WorkScout-Core plugin to version 1.7.06 or later to incorporate the necessary security patches.

Proactive Monitoring: Review web server access logs for unusual patterns of POST requests or suspicious referral headers that might indicate attempted CSRF attacks.

Compensating Controls: Deploy a Web Application Firewall (WAF) to detect and block suspicious requests that lack valid anti-CSRF tokens or originate from unexpected sources.

Exploitation status

Public Exploit Available: No — there is no confirmed public exploit available.

Analyst recommendation

This vulnerability presents a high risk to the security of the affected WordPress environment. Administrators should verify their current plugin version immediately and apply the update to 1.7.06 to remediate this flaw. Failure to patch may leave the application susceptible to unauthorized administrative actions performed by external attackers.

More purethemes CVEs

History

  1. Disclosed CVE record published
  2. Published in the daily brief high section
  3. Published in the daily brief high section
  4. Analyst report written
  5. Fix documented version 1.7.06 per Wordfence

Sources

Originally found and disclosed by Bonds | Patchstack Bug Bounty Program, per the CVE Program record.