CVE-2025-39417
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Eslam Mahmoud Redirect wordpress to welcome or landing page redirect-to-welcome-or-landing-page allows Stored XSS.This issue affects Redirect wordpress to welcome or landing page: from n/a through <= 2.0.
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 · high confidenceA CSRF vulnerability in the 'Redirect wordpress to welcome or landing page' WordPress plugin (versions <= 2.0) allows authenticated administrators to be tricked into submitting malicious requests that inject Stored XSS payloads into the plugin's settings or redirect configuration. The attacker does not directly execute code but exploits the lack of CSRF tokens to induce an admin to unknowingly store malicious scripts.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins and look for 'Redirect wordpress to welcome or landing page' or inspect the wp-content/plugins directory for a folder matching this plugin nameAffected if The plugin appears in the list of installed plugins
-
Check installed plugin versionView the main plugin PHP file header (typically in wp-content/plugins/[plugin-folder]/index.php or similar) to read the Version field declared in the plugin metadata comment blockAffected if The version number displayed is 2.0 or lower
-
Inspect plugin settings for suspicious contentQuery the wp_options table (via phpMyAdmin or WP CLI: wp db query "SELECT * FROM wp_options WHERE option_name LIKE '%redirect%'") and examine any stored values for the plugin settings or redirect URLsAffected if Any option_value contains unexpected script tags, javascript: URIs, or HTML markup that was not intentionally configured by an administrator
-
Review .htaccess or redirect configurationsCheck the .htaccess file in the WordPress root directory and any custom redirect rules that may have been injected, or inspect the plugin's saved configuration for unauthorized redirect targetsAffected if Unexpected redirect rules or URLs point to external malicious domains or contain XSS payloads
You are affected if the plugin is installed at version 2.0 or lower AND its settings or database records contain any unrecognized or malicious script injections or redirect configurations.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate to the latest plugin version if available; otherwise disable the plugin. All admin forms should implement anti-CSRF tokens (nonces) and all user-supplied redirect URLs and parameters must be sanitized/validated before storage and output.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-39417 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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