CVE-2018-1002000

Arigato Autoresponder and Newsletter <= 2.5.1.8 - SQL Injection

2018-09-18 00:00
Larry W. Cashdollar

Strategic Overview

Status
Patched in 2.5.1.9
Affected Version
<= 2.5.1.8
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2018-1002000
View all Arigato Autoresponder and Newsletter vulnerabilities

At a glance

CVE-2018-1002000 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Arigato Autoresponder and Newsletter WordPress plugin, affecting versions <= 2.5.1.8. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.5.1.9; sites on affected versions should update now. Disclosed September 2018, reported by Larry W. Cashdollar.

Vulnerability Overview

There is blind SQL injection in WordPress Arigato Autoresponder and Newsletter v2.5.1.8 These vulnerabilities require administrative privileges to exploit. There is an exploitable blind SQL injection vulnerability via the del_ids variable by POST request.

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 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 Arigato Autoresponder and Newsletter <= 2.5.1.8 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 Arigato Autoresponder and Newsletter the fix is 2.5.1.9: builds <= 2.5.1.8 are affected, anything from 2.5.1.9 onward is not.

Remediation

Update to version 2.5.1.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Arigato Autoresponder and Newsletter: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Arigato Autoresponder and Newsletter 2.5.1.9 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