CVE-2025-0801

RateMyAgent Official <= 1.4.0 - Cross-Site Request Forgery to API Key Update

2025-02-27 16:15
Dhabaleshwar Das

Strategic Overview

Status
Patched in 1.5.0
Affected Plugin
RateMyAgent Official
Affected Version
<= 1.4.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-0801
View all RateMyAgent Official vulnerabilities

At a glance

CVE-2025-0801 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the RateMyAgent Official WordPress plugin, affecting versions <= 1.4.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.5.0; sites on affected versions should update now. Disclosed February 2025, reported by Dhabaleshwar Das.

Vulnerability Overview

The RateMyAgent Official plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.4.0. This is due to missing or incorrect nonce validation on the 'rma-settings-wizard'. This makes it possible for unauthenticated attackers to update the plugin's API key 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)

RateMyAgent Official <= 1.4.0 carries this weakness at rma-settings-wizard, 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 RateMyAgent Official the fix is 1.5.0: builds <= 1.4.0 are affected, anything from 1.5.0 onward is not.

Remediation

Update to version 1.5.0, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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