HIGH 8.2

CVE-2016-20071: Critical SQL Injection in WordPress 404 Redirection Manager Plugin v1.0

The 404 Redirection Manager plugin version 1.0 for WordPress has a serious flaw that allows attackers to steal data directly from your WordPress database without needing to log in. An attacker can send a specially crafted web request containing SQL commands, which the plugin fails to validate, leading to unauthorized database access. This is a remote vulnerability that requires no authentication and can be exploited from anywhere on the internet.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.2 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Weaknesses (CWE)
CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-06-15 / 2026-06-17

NVD description (verbatim)

The 404 Redirection Manager plugin version 1.0 for WordPress contains an unauthenticated SQL injection vulnerability that allows remote attackers to execute arbitrary SQL queries by injecting malicious code through unsanitized user input. Attackers can craft GET requests with SQL injection payloads to manipulate database queries and extract sensitive information from the WordPress database.

3 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2016-20071 is an unauthenticated SQL injection vulnerability (CWE-89) in the 404 Redirection Manager WordPress plugin version 1.0. The vulnerability exists because user-supplied input passed through GET parameters is not properly sanitized before being incorporated into SQL queries. An attacker can inject arbitrary SQL commands to bypass query logic, extract data from the WordPress database, or modify query results. The CVSS 3.1 score of 8.2 (HIGH) reflects the network-accessible nature, low attack complexity, and high confidentiality impact, though data modification is limited and availability is not directly threatened.

Business impact

Compromise of a WordPress site running this vulnerable plugin puts customer data, user credentials, and sensitive business information at immediate risk. An attacker could extract user records, email addresses, passwords, or any other information stored in the database. For e-commerce sites, this could include payment information or order history. Reputational damage, regulatory fines under GDPR or similar laws, and loss of customer trust are significant secondary impacts. The ease of exploitation—requiring only a crafted URL—means this risk is active and ongoing without immediate detection.

Affected systems

WordPress installations with the 404 Redirection Manager plugin version 1.0 are affected. The vulnerability is version-specific; verify whether your site uses this exact version. No evidence of exploitation in the wild has been added to the CISA Known Exploited Vulnerabilities (KEV) catalog, though public exploit awareness may still exist. Sites running version 1.0 should treat this as urgent. Check your WordPress plugin directory for this plugin and confirm the installed version.

Exploitability

This vulnerability is highly exploitable. Attack complexity is low—no special conditions or timing are required. An attacker needs only to craft a malicious GET request with SQL injection payloads and send it to any page where the plugin processes 404 redirects. No authentication is needed. The public nature of this CVE means weaponized payloads are or will become readily available. Active threat actors commonly target WordPress plugins due to the large installed base and frequency of unpatched instances.

Remediation

Immediately deactivate and remove the 404 Redirection Manager plugin version 1.0 from all affected WordPress installations. No patch version has been identified for this plugin in available vendor advisories; consider whether an alternative 404 redirection solution is necessary for your site's functionality. If a patched version becomes available from the plugin developer, verify the version number against the official WordPress plugin repository before installing. As an interim measure, block access to the plugin's functionality via Web Application Firewall rules if removal is not immediately feasible.

Patch guidance

As of the current data, no patched version of the 404 Redirection Manager plugin has been released or documented. Contact the plugin developer directly to determine if a fix is available. Check the official WordPress.org plugin page for this plugin to see if an update is posted. If no patch is forthcoming from the developer, plan to migrate to an alternative WordPress redirection plugin that actively maintains security. Verify any replacement solution against current security reviews before deployment.

Detection guidance

Monitor web server logs and WAF logs for GET requests containing SQL injection keywords and patterns (e.g., UNION, SELECT, --, ;, OR 1=1) directed at paths associated with the 404 Redirection Manager plugin. Use WordPress security plugins or database activity monitoring to detect unusual SQL queries or unauthorized database access. Check the WordPress admin panel for the plugin's presence and version number under Plugins → Installed Plugins. Review database access logs for queries originating from web requests rather than legitimate application code, particularly those containing comment syntax or logical operators.

Why prioritize this

This vulnerability should be a top priority for immediate remediation. The combination of unauthenticated access, network reachability, ease of exploitation, and direct access to sensitive data makes it an active and high-impact threat. The HIGH CVSS score and CWE-89 (SQL Injection) classification reflect well-understood attack techniques. Organizations running outdated plugins are frequently targeted in opportunistic scans. Delay increases the window of exposure.

Risk score, explained

The CVSS 3.1 score of 8.2 (HIGH) is driven by network accessibility (AV:N), low attack complexity (AC:L), lack of authentication requirement (PR:N), and high confidentiality impact (C:H). The score is not critical (9.0+) because the vulnerability does not allow arbitrary code execution or denial of service; integrity and availability impacts are limited (I:L, A:N). However, the confidentiality breach alone—unrestricted database read access—justifies the HIGH rating and urgent response posture.

Frequently asked questions

Do I need to be authenticated to exploit this vulnerability?

No. This is an unauthenticated vulnerability, meaning an attacker does not need valid WordPress credentials or admin access. Any remote user can send a malicious GET request to trigger the SQL injection. This makes it particularly dangerous because it requires no prior access to your site.

What versions of the 404 Redirection Manager plugin are affected?

Based on available information, version 1.0 is confirmed vulnerable. If you are running this plugin, immediately check your version in the WordPress admin panel under Plugins. If alternative versions exist, verify their security status with the developer before upgrading, as this plugin may lack active maintenance.

What data can an attacker access through this SQL injection?

An attacker can access any data stored in your WordPress database, including user accounts and passwords (if not properly hashed), email addresses, posts, pages, plugin settings, and any custom data. The extent of exposure depends on your database schema and what information your site stores. E-commerce data, member information, and confidential content are all at risk.

If this CVE was published in June 2026, why haven't I heard of it?

New vulnerabilities in older or less commonly maintained plugins sometimes receive delayed public attention. The 404 Redirection Manager plugin may have a smaller user base than mainstream WordPress core or popular plugins, so news may not have reached all organizations. This is why a layered security approach that includes regular plugin audits and scanning is essential.

This analysis is based on available CVE and vulnerability intelligence data as of the provided source date. Exploit details, affected product versions, patch availability, and KEV catalog status may change. Organizations should verify patch versions against official vendor advisories before deployment. This guidance is for informational purposes; conduct your own risk assessment based on your specific environment, installed plugin versions, and business context. SEC.co makes no warranty regarding the completeness or accuracy of third-party plugin data. Regular security scanning and plugin auditing remain essential preventive practices. Source: NVD (public-domain), retrieved 2026-07-20. Analysis generated by SEC.co (claude-haiku-4-5).