CVE-2026-49067
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 SQL Injection in Advanced 301 and 302 Redirect <= 1.6.9 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 SQL Injection vulnerability exists in the Advanced 301 and 302 Redirect WordPress plugin versions 1.6.9 and earlier. The vulnerability allows remote attackers to execute arbitrary SQL queries via unsanitized input, potentially leading to data exfiltration or complete database compromise. With a CVSS score of 9.3 (Critical), this issue poses severe risk to unpatched installations.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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.
-
Locate the Advanced 301 and 302 Redirect plugin filesCheck the wp-content/plugins directory for a folder named 'advanced-301-302-redirect' or similar variant, or view the installed plugins list in the WordPress admin under Plugins > Installed PluginsAffected if The plugin folder does not exist in the plugins directory
-
Identify the installed plugin versionOpen the main plugin file (usually named redirect-301-302.php or similar) and look for the version comment header, or inspect the readme.txt file for the 'Stable tag' entryAffected if The version cannot be determined or the plugin is not present
-
Compare the installed version against the vulnerable rangeReview the version number found in step 2 and compare it to the affected range: versions 1.6.9 and below are vulnerable; version 1.7.0 and later are patchedAffected if The installed version is 1.6.9 or lower (for example, 1.6.8, 1.6.7, 1.6.0, etc.)
-
Verify the plugin is active on the siteIn WordPress admin, check the Plugins list to confirm the plugin shows as 'Active', or query the wp_options table for the active_plugins option to see if the plugin entry is presentAffected if The plugin is installed but not active (inactive plugins may reduce but not eliminate risk depending on deployment)
The environment is affected if the Advanced 301 and 302 Redirect plugin is installed, active, and running version 1.6.9 or lower.
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.
dbcve · scopedUpdate the Advanced 301 and 302 Redirect plugin to a version newer than 1.6.9 immediately. If no patched version is available, consider disabling the plugin until a fix is released, or implement WAF rules as a temporary mitigation.
Version 1.7.0 or later (latest available version)
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the 'Advanced 301 and 302 Redirect' plugin
- If an update is available, click 'Update Now' to upgrade to the latest patched version
- Alternatively, download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin
- After updating, verify the plugin is running version 1.7.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49067 — 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-49067 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