dbcve.org
Seo RedirectionWordPress extension · Clogica

CVE-2022-40695

HIGH · 8.8 CVSS v3.1 Published 2022-11-18
Fix available
A fix is available. Upgrade to 9.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Multiple Cross-Site Scripting (CSRF) vulnerabilities in SEO Redirection Plugin plugin <= 8.9 on WordPress.

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 confidence

Multiple Cross-Site Scripting vulnerabilities in the SEO Redirection Plugin for WordPress (version 8.9 and below) allow authenticated attackers to inject malicious scripts through plugin parameters, potentially leading to session hijacking or data theft.

MitigationUpdate the SEO Redirection Plugin to a version newer than 8.9, or deactivate and remove the plugin until a patched version is available.

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
Affected:< 9.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm SEO Redirection Plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Look for 'Seo Redirection' or 'SEO Redirection Plugin' in the list. Alternatively, check if the directory wp-content/plugins/seo-redirection/ or similar exists on the server.
    Affected if The plugin appears in the WordPress plugin list or plugin directory exists on the server.
  2. Identify the installed plugin version
    In WordPress admin, click on the plugin name in the Plugins list to view its details, which typically display the version number. Alternatively, open the main plugin PHP file (usually seo-redirection.php or similar in the plugin directory) and look for the version header in the plugin comment block at the top of the file.
    Affected if The displayed version number is 8.9 or lower, or if no version is displayed but the plugin is present.
  3. Compare version against affected range
    Take the identified version number and compare it against the affected range: any version less than 9.1 is vulnerable. Version 8.9 and all versions below 9.1 are affected.
    Affected if The installed version is less than 9.1 (for example, 8.9, 8.8, 8.7, etc.).
  4. Determine if authentication is possible
    The XSS vulnerabilities require an authenticated attacker. Check if user registration is enabled (Settings > General > Membership) or if there are user accounts beyond the administrator. Also verify if any user roles with access to the plugin settings exist.
    Affected if The site allows user registration, has multiple user accounts, or has users with contributor/author/editor roles who could access plugin functionality.
  5. Review plugin settings for suspicious activity
    Navigate to the SEO Redirection plugin settings panel in WordPress admin. Look for any unexpected redirect rules, modified URLs, or injected script content in fields that may have been tampered with.
    Affected if Unknown redirect rules, suspicious URLs pointing to external domains, or script tags appear in plugin configuration fields.

You are affected if the SEO Redirection Plugin by Clogica is installed with any version below 9.1 and any authenticated user (including self-registered users) has access to the WordPress site.

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
Upgrade available Upgrade to 9.1 or later
Fixed in 9.1
Interim mitigation

Update the SEO Redirection Plugin to a version newer than 8.9, or deactivate and remove the plugin until a patched version is available.

Recommended fix High confidence

SEO Redirection version 9.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'SEO Redirection' plugin
  4. Click 'Update now' if an update is available, or manually download version 9.1 or later from wordpress.org and upload it
  5. Verify the plugin is updated to version 9.1 or higher

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

Fix this in Seo Redirection Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40695 — 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-2022-40695 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