Seo RedirectionWordPress extension · Clogica
CVE-2016-10896
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 · uneditedThe seo-redirection plugin before 4.3 for WordPress has stored XSS.
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 confidenceThe seo-redirection plugin before version 4.3 for WordPress contains a stored cross-site scripting (XSS) vulnerability. Attackers can inject malicious scripts into the plugin's redirection settings or SEO-related fields, which are then stored in the database and executed when administrators or users view affected pages in the WordPress admin panel.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Seo RedirectionWordPress extension
< 4.3CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Check if Seo Redirection plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Seo Redirection' or 'Clogica Seo Redirection'. Note the version number displayed there.Affected if Plugin is installed and version is below 4.3
-
Locate plugin files for version confirmationAccess the WordPress site via FTP or file manager, navigate to /wp-content/plugins/seo-redirection/ and open the main plugin file (usually seo-redirection.php or similar) to read the version defined in the plugin header comment.Affected if Version in plugin files reads less than 4.3
-
Identify if redirection rules are configuredIn WordPress admin, go to the Seo Redirection plugin settings panel (usually under Settings or a dedicated Seo Redirection menu). Check if any redirection rules, SEO targets, or URL redirection entries have been created.Affected if Redirection rules exist and the plugin version is below 4.3
-
Inspect database for stored XSS payloadsAccess the WordPress database via phpMyAdmin or command line. Query the options table (wp_options) and any custom tables created by the plugin (often named like wp_seo_redirection_* or similar) for suspicious patterns in redirection/SEO fields. Look for HTML script tags, javascript:, onload, onerror, or other XSS vectors in values stored in redirect URLs, source URLs, or SEO metadata fields.Affected if Database contains any redirection entries with encoded or plain XSS payloads in the stored values
User is affected if the seo-redirection plugin is installed with a version lower than 4.3 and contains any redirection rules or SEO configuration entries.
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 data4.3
Update the seo-redirection plugin to version 4.3 or later to remediate the stored XSS vulnerability. After updating, verify that existing redirection rules do not contain any malicious payloads.
Fix this in Seo Redirection
Scoped from the published advisory
- 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-2016-10896 — 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-2016-10896 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