CVE-2026-52702
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 · uneditedUnauthenticated Cross Site Scripting (XSS) in SEO Redirection <= 9.17 versions.
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 confidenceAn unauthenticated Cross Site Scripting (XSS) vulnerability exists in the SEO Redirection plugin for WordPress in versions 9.17 and below. Attackers can inject malicious JavaScript code through the plugin without needing authentication, potentially stealing session cookies or performing actions on behalf of authenticated users.
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.
-
Verify SEO Redirection plugin is installedLog into WordPress admin and navigate to Plugins > Installed Plugins, or use WP-CLI: wp plugin list --name=seo-redirectionAffected if The plugin does not appear in the list of installed plugins, then you are not affected by this CVE.
-
Identify the installed version of SEO RedirectionIn WordPress admin, find the SEO Redirection entry in Plugins > Installed Plugins and read the version number under the plugin name. Alternatively, inspect the main plugin file header in wp-content/plugins/seo-redirection/Affected if The version displayed is 9.17 or lower (such as 9.17, 9.16, 9.15, etc.), indicating the installation falls within the affected version range.
-
Confirm the plugin is activeIn WordPress admin at Plugins > Installed Plugins, verify the SEO Redirection plugin shows as Active, or run: wp plugin status seo-redirectionAffected if The plugin is active and the version is 9.17 or below, meaning the vulnerable code is currently executing in your environment.
-
Check for unauthenticated access pointsThe vulnerability is unauthenticated, meaning the affected input fields are accessible without logging in. Assess whether your WordPress site exposes the plugin functionality to unauthenticated users (the plugin processes requests without requiring login credentials).Affected if Unauthenticated users can access and submit data through the plugin's forms or parameters, which is the condition required for this XSS to be exploitable.
Your environment is affected if the SEO Redirection plugin is installed, active, and the version is 9.17 or lower, allowing unauthenticated users to interact with the plugin's input fields.
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 the SEO Redirection plugin to the latest version (greater than 9.17) which contains the vendor patch for this vulnerability. If immediate update is not possible, consider disabling the plugin until the patch can be applied.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52702 — 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-2026-52702 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