CVE-2015-9323

404 to 301 – Redirect, Log and Notify 404 Errors <= 2.0.2 - SQL Injection

2015-08-20 00:00
Marcin Probola

Strategic Overview

Status
Patched in 2.0.3
Affected Plugin
404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring
Affected Version
< 2.0.3
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-9323
View all 404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring vulnerabilities

At a glance

CVE-2015-9323 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the 404 to 301 WordPress plugin, affecting versions < 2.0.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.0.3; sites on affected versions should update now. Disclosed August 2015, reported by Marcin Probola.

Vulnerability Overview

The 404-to-301 plugin before 2.0.3 for WordPress has SQL injection via the 'orderby' and 'order' parameters.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

404 to 301 < 2.0.3 carries this weakness at orderby, and reaching it takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For 404 to 301 the fix is 2.0.3: builds < 2.0.3 are affected, anything from 2.0.3 onward is not.

Remediation

Update to version 2.0.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to 404 to 301: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: 404 to 301 2.0.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-9323https://www.wordfence.com/threat-intel/vulnerabilities/id/69b2f126-8f57-4bea-b0e9-14b4566ac470https://nvd.nist.gov/vuln/detail/CVE-2015-9323

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C