dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-53315

HIGH · 7.1 CVSS v3.1 Published 2025-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in alanft Relocate Upload relocate-upload allows Stored XSS.This issue affects Relocate Upload: from n/a through <= 0.24.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A CSRF vulnerability in the Relocate Upload WordPress plugin (versions <= 0.24.1) allows attackers to inject malicious scripts via stored XSS. By tricking authenticated administrators into visiting attacker-controlled pages, forged requests can cause persistent malicious JavaScript to be stored in the database, executing whenever users view the affected content.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations and apply proper output escaping/sanitization for all stored data rendered in the plugin.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Relocate Upload'. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file header for the 'Version' comment.
    Affected if The plugin is installed and the reported version is 0.24.1 or lower.
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify that the Relocate Upload plugin shows as 'Active' under its status.
    Affected if The plugin is both installed (version <= 0.24.1) AND active.
  3. Check for admin session susceptibility
    Review whether administrators in your environment could be tricked into visiting attacker-controlled pages while logged in (for example, via phishing links in emails or external sites). This is a prerequisite for the CSRF attack to succeed.
    Affected if Administrators can be socially engineered to visit external URLs while authenticated to WordPress.
  4. Inspect stored plugin data for malicious scripts
    Query the WordPress database for any records created by the Relocate Upload plugin that contain suspicious patterns (such as <script> tags, javascript: URLs, or event handler attributes like onerror/onclick). The exact table depends on how the plugin stores its data.
    Affected if Database records associated with the plugin contain unsanitized HTML or JavaScript that could execute in admin or user contexts.

You are affected if the Relocate Upload plugin version 0.24.1 or lower is installed and active, and administrators can be socially engineered into triggering forged requests or malicious scripts are already present in plugin-stored data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations and apply proper output escaping/sanitization for all stored data rendered in the plugin.

Recommended fix Moderate confidence

latest available version (check WordPress Plugin Repository for the most recent release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Relocate Upload' plugin by alanft
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository or the vendor's official source
  6. 6. After updating, verify the plugin is working correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53315 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53315 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data