CVE-2025-32477 in WP-Easy Menu Plugininfo

Summary

by MITRE • 04/09/2025

Cross-Site Request Forgery (CSRF) vulnerability in Jordi Salord WP-Easy Menu allows Stored XSS. This issue affects WP-Easy Menu: from n/a through 0.41.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 04/09/2025

This cross-site request forgery vulnerability in the WP-Easy Menu plugin presents a critical security risk that enables attackers to execute stored cross-site scripting attacks through manipulated administrative requests. The vulnerability exists within the plugin's handling of user input and request processing mechanisms, specifically affecting versions ranging from the initial release through version 0.41. The flaw allows unauthorized actors to craft malicious requests that, when executed by authenticated administrators, can inject persistent malicious scripts into the plugin's administrative interface.

The technical implementation of this vulnerability stems from insufficient validation and sanitization of input parameters within the plugin's administrative endpoints. When administrators interact with the menu management features, the plugin fails to properly verify the authenticity of requests originating from legitimate administrative sessions. This absence of proper CSRF token validation creates an exploitable condition where attackers can construct malicious payloads that appear to originate from authorized users. The stored nature of the XSS vulnerability means that malicious scripts injected through these CSRF attacks persist in the plugin's database and execute whenever affected pages are loaded, potentially affecting all users who access the compromised administrative interface.

The operational impact of this vulnerability extends beyond simple script execution, as it provides attackers with persistent access to administrative functions and sensitive data within the WordPress environment. Attackers can leverage this vulnerability to modify menu configurations, inject malicious code into the site's frontend, potentially escalate privileges, or even establish backdoor access points. The stored XSS component significantly amplifies the damage potential since malicious scripts remain active until manually removed from the plugin's database, allowing attackers to maintain persistent access and execute long-term malicious activities. This vulnerability directly maps to CWE-352, which specifically addresses Cross-Site Request Forgery issues, and aligns with ATT&CK technique T1059.007 for Scripting, where adversaries use stored scripts to maintain persistent access.

Mitigation strategies should focus on immediate plugin updates to versions that address the CSRF validation gaps and implementation of proper input sanitization measures. Administrators must ensure that all WordPress plugins are regularly updated and that the plugin's CSRF protection mechanisms are properly configured with unique tokens for each administrative session. Network monitoring should be enhanced to detect suspicious administrative requests, and multi-factor authentication should be implemented for administrative accounts. Additionally, the principle of least privilege should be enforced by limiting administrative access to essential personnel only, while regular security audits should verify that all plugin components properly validate and sanitize user input to prevent similar vulnerabilities from emerging in the future.

Responsible

Patchstack

Reservation

04/09/2025

Disclosure

04/09/2025

Moderation

accepted

CPE

ready

EPSS

0.00175

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!