EUVD-2025-28512Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Attack requires no prior authentication (PR:N) due to CSRF; user interaction (UI:R) is the sole exploitation constraint.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
Cross-Site Request Forgery (CSRF) vulnerability in alanft Relocate Upload allows Stored XSS. This issue affects Relocate Upload: from n/a through 0.24.1.
AnalysisAI
Stored cross-site scripting (XSS) via cross-site request forgery (CSRF) in the Relocate Upload WordPress plugin up to version 0.24.1 allows an unauthenticated attacker to inject malicious scripts into the administrative interface. The attack requires an authenticated administrator to be tricked into clicking a crafted link, after which the injected script executes in the context of the admin user. No active exploitation or public exploit code has been identified, and EPSS data indicates a very low exploitation probability (0.02%).
Technical ContextAI
The vulnerability arises from a missing or insufficient anti-CSRF token in the Relocate Upload plugin’s administrative functionalities, classified under CWE-352 (Cross-Site Request Forgery). The plugin, as indicated by the available references, is a WordPress component likely handling file relocation or upload functionality. Because WordPress admin panels typically execute within the browser context of an authenticated administrator, a successful CSRF attack can submit a request that stores a malicious JavaScript payload (Stored XSS) in the plugin settings, which then executes whenever an admin views the affected settings page.
RemediationAI
As of this analysis, no vendor-released patch has been confirmed. The primary recommended action is to deactivate the Relocate Upload plugin until an updated version is made available. For environments where the plugin cannot be disabled, implement a web application firewall (WAF) rule to block requests to the vulnerable administrative endpoints without valid anti-CSRF tokens, and enforce the use of the SameSite cookie attribute to limit cross-origin requests. Additionally, applying Content Security Policy (CSP) headers with strict script-src directives can reduce the impact of any stored XSS, though this does not prevent the CSRF itself. Monitor the vendor’s advisory page and the Patchstack entry for patch information.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today