CVE-2013-6243

WordPress Landing Pages < 1.2.3 - SQL Injection

2013-10-10 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.3
Affected Version
< 1.2.3
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2013-6243
View all WordPress Landing Pages vulnerabilities

At a glance

CVE-2013-6243 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WordPress Landing Pages WordPress plugin, affecting versions < 1.2.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 1.2.3; sites on affected versions should update now. Disclosed October 2013.

Vulnerability Overview

SQL injection vulnerability in the Landing Pages plugin before 1.2.3 for WordPress allows remote attackers to execute arbitrary SQL commands via the "post" parameter to index.php.

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')

WordPress Landing Pages < 1.2.3 carries this weakness at post, 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 WordPress Landing Pages the fix is 1.2.3: builds < 1.2.3 are affected, anything from 1.2.3 onward is not.

Remediation

Update to version 1.2.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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