CVE-2015-9344

Link Log – external link click monitor < 2.1 - SQL Injection

2015-12-11 00:00
Anonymous

Strategic Overview

Status
Patched in 2.1
Affected Version
< 2.1
CVSS
9.8Critical
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2015-9344
View all Smart External Link Click Monitor [Link Log] vulnerabilities

At a glance

CVE-2015-9344 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Smart External Link Click Monitor [Link Log] WordPress plugin, affecting versions < 2.1. 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.1; sites on affected versions should update now. Disclosed December 2015.

Vulnerability Overview

The link-log plugin before 2.1 for WordPress has SQL injection via the ipaddress parameter.

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

Reaching this weakness in Smart External Link Click Monitor [Link Log] < 2.1 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 Smart External Link Click Monitor [Link Log] the fix is 2.1: builds < 2.1 are affected, anything from 2.1 onward is not.

Remediation

Update to version 2.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Smart External Link Click Monitor [Link Log]: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Smart External Link Click Monitor [Link Log] 2.1 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