CVE-2025-2797

Woffice Core <= 5.4.21 - Cross-Site Request Forgery to User Registration Approval

2025-04-03 00:00
Foxyyy

Strategic Overview

Status
Patched in 5.4.22
Affected Plugin
Woffice Core
Affected Version
<= 5.4.21
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-2797
View all Woffice Core vulnerabilities

At a glance

CVE-2025-2797 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Woffice Core WordPress plugin, affecting versions <= 5.4.21. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.4.22; sites on affected versions should update now. Disclosed April 2025, reported by Foxyyy.

Vulnerability Overview

The Woffice Core plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.4.21. This is due to missing or incorrect nonce validation on the 'woffice_handle_user_approval_actions' function. This makes it possible for unauthenticated attackers to approve registration for any user 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)

Woffice Core <= 5.4.21 carries this weakness at woffice_handle_user_approval_actions, 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 Woffice Core the fix is 5.4.22: builds <= 5.4.21 are affected, anything from 5.4.22 onward is not.

Remediation

Update to version 5.4.22, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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