CVE-2025-0801: CWE-352 Cross-Site Request Forgery (CSRF) in ratemyagent RateMyAgent Official
CVE-2025-0801 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the RateMyAgent Official WordPress plugin up to version 1. 4. 0. The flaw arises from missing or incorrect nonce validation on the 'rma-settings-wizard' endpoint, allowing unauthenticated attackers to trick site administrators into executing forged requests. Exploitation enables attackers to update the plugin's API key without authentication, potentially disrupting plugin functionality or redirecting data flows. The vulnerability requires user interaction, specifically an administrator clicking a malicious link. The CVSS 3. 1 base score is 4. 3 (medium severity), reflecting low impact on confidentiality and availability but some integrity risk. No known exploits are reported in the wild as of now.
AI Analysis
Technical Summary
CVE-2025-0801 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability identified in the RateMyAgent Official plugin for WordPress, affecting all versions up to and including 1.4.0. The vulnerability stems from missing or incorrect nonce validation on the 'rma-settings-wizard' functionality, which is responsible for managing plugin settings including the API key. Nonce validation is a security mechanism designed to ensure that requests originate from legitimate users and not from malicious third-party sites. Due to the absence or improper implementation of this validation, an attacker can craft a malicious web request that, when an authenticated site administrator visits or clicks a specially crafted link, causes the administrator’s browser to unknowingly submit a request that updates the plugin’s API key. This attack does not require the attacker to be authenticated on the target site but does require user interaction from an administrator, making it a classic CSRF scenario. The impact primarily affects the integrity of the plugin’s configuration, as unauthorized API key changes could disrupt plugin functionality, potentially leading to data misrouting or loss of control over plugin features. The CVSS 3.1 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), unchanged scope (S:U), no confidentiality or availability impact (C:N/A:N), and low integrity impact (I:L). No public exploits have been reported yet, but the vulnerability is published and should be addressed promptly. The lack of a patch link suggests that a fix may not yet be available, emphasizing the need for interim mitigations.
Potential Impact
The primary impact of this vulnerability is on the integrity of the RateMyAgent plugin’s configuration, specifically the API key used for its operations. Unauthorized modification of the API key could lead to loss of control over plugin data exchanges, potentially allowing attackers to redirect or disrupt data flows between the WordPress site and RateMyAgent services. While this does not directly compromise site confidentiality or availability, it undermines trust in the plugin’s functionality and could indirectly affect business operations relying on accurate agent ratings and reviews. Organizations using this plugin risk unauthorized configuration changes that could lead to service disruption or data integrity issues. Since exploitation requires an administrator to interact with a malicious link, social engineering is a key factor, increasing the risk in environments where administrators may be targeted. The vulnerability affects all sites running the vulnerable plugin versions, which could be widespread given WordPress’s popularity. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after public disclosure.
Mitigation Recommendations
Organizations should immediately verify if they are running RateMyAgent Official plugin versions up to 1.4.0 and plan to update to a patched version once available. Until a patch is released, administrators should be educated about the risk of clicking untrusted links, especially those that could trigger plugin settings changes. Implementing web application firewall (WAF) rules to detect and block suspicious POST requests targeting the 'rma-settings-wizard' endpoint can help mitigate exploitation attempts. Additionally, site owners can manually add nonce verification checks in the plugin code if feasible or disable the plugin temporarily if it is not critical. Monitoring administrative activity logs for unexpected changes to plugin settings or API keys can provide early detection of exploitation attempts. Enforcing multi-factor authentication (MFA) for administrator accounts reduces the risk of account compromise that could facilitate exploitation. Finally, maintaining regular backups of site configurations ensures recovery capability if unauthorized changes occur.
Affected Countries
United States, United Kingdom, Canada, Australia, Germany, France, Netherlands, New Zealand, South Africa
CVE-2025-0801: CWE-352 Cross-Site Request Forgery (CSRF) in ratemyagent RateMyAgent Official
Description
CVE-2025-0801 is a Cross-Site Request Forgery (CSRF) vulnerability affecting the RateMyAgent Official WordPress plugin up to version 1. 4. 0. The flaw arises from missing or incorrect nonce validation on the 'rma-settings-wizard' endpoint, allowing unauthenticated attackers to trick site administrators into executing forged requests. Exploitation enables attackers to update the plugin's API key without authentication, potentially disrupting plugin functionality or redirecting data flows. The vulnerability requires user interaction, specifically an administrator clicking a malicious link. The CVSS 3. 1 base score is 4. 3 (medium severity), reflecting low impact on confidentiality and availability but some integrity risk. No known exploits are reported in the wild as of now.
AI-Powered Analysis
Technical Analysis
CVE-2025-0801 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability identified in the RateMyAgent Official plugin for WordPress, affecting all versions up to and including 1.4.0. The vulnerability stems from missing or incorrect nonce validation on the 'rma-settings-wizard' functionality, which is responsible for managing plugin settings including the API key. Nonce validation is a security mechanism designed to ensure that requests originate from legitimate users and not from malicious third-party sites. Due to the absence or improper implementation of this validation, an attacker can craft a malicious web request that, when an authenticated site administrator visits or clicks a specially crafted link, causes the administrator’s browser to unknowingly submit a request that updates the plugin’s API key. This attack does not require the attacker to be authenticated on the target site but does require user interaction from an administrator, making it a classic CSRF scenario. The impact primarily affects the integrity of the plugin’s configuration, as unauthorized API key changes could disrupt plugin functionality, potentially leading to data misrouting or loss of control over plugin features. The CVSS 3.1 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), unchanged scope (S:U), no confidentiality or availability impact (C:N/A:N), and low integrity impact (I:L). No public exploits have been reported yet, but the vulnerability is published and should be addressed promptly. The lack of a patch link suggests that a fix may not yet be available, emphasizing the need for interim mitigations.
Potential Impact
The primary impact of this vulnerability is on the integrity of the RateMyAgent plugin’s configuration, specifically the API key used for its operations. Unauthorized modification of the API key could lead to loss of control over plugin data exchanges, potentially allowing attackers to redirect or disrupt data flows between the WordPress site and RateMyAgent services. While this does not directly compromise site confidentiality or availability, it undermines trust in the plugin’s functionality and could indirectly affect business operations relying on accurate agent ratings and reviews. Organizations using this plugin risk unauthorized configuration changes that could lead to service disruption or data integrity issues. Since exploitation requires an administrator to interact with a malicious link, social engineering is a key factor, increasing the risk in environments where administrators may be targeted. The vulnerability affects all sites running the vulnerable plugin versions, which could be widespread given WordPress’s popularity. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits after public disclosure.
Mitigation Recommendations
Organizations should immediately verify if they are running RateMyAgent Official plugin versions up to 1.4.0 and plan to update to a patched version once available. Until a patch is released, administrators should be educated about the risk of clicking untrusted links, especially those that could trigger plugin settings changes. Implementing web application firewall (WAF) rules to detect and block suspicious POST requests targeting the 'rma-settings-wizard' endpoint can help mitigate exploitation attempts. Additionally, site owners can manually add nonce verification checks in the plugin code if feasible or disable the plugin temporarily if it is not critical. Monitoring administrative activity logs for unexpected changes to plugin settings or API keys can provide early detection of exploitation attempts. Enforcing multi-factor authentication (MFA) for administrator accounts reduces the risk of account compromise that could facilitate exploitation. Finally, maintaining regular backups of site configurations ensures recovery capability if unauthorized changes occur.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-01-28T14:45:28.388Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6b6bb7ef31ef0b5553a0
Added to database: 2/25/2026, 9:36:43 PM
Last enriched: 2/25/2026, 11:55:52 PM
Last updated: 2/26/2026, 7:11:48 AM
Views: 1
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25191: Uncontrolled Search Path Element in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-23703: Incorrect default permissions in Digital Arts Inc. FinalCode Ver.5 series
HighCVE-2026-1311: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in bearsthemes Worry Proof Backup
HighFinding Signal in the Noise: Lessons Learned Running a Honeypot with AI Assistance [Guest Diary], (Tue, Feb 24th)
MediumCVE-2026-2506: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in motahar1 EM Cost Calculator
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.