Activity Log 2.3.5 - 2.6.1 - SQL Injection

2021-05-03 00:00
Synacktiv

Strategic Overview

Status
Patched in 2.7.0
Affected Plugin
Activity Log – Monitor User and Agent Changes
Affected Version
2.3.5 – 2.6.1
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all Activity Log – Monitor User and Agent Changes vulnerabilities

At a glance

This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Activity Log WordPress plugin, affecting versions 2.3.5 – 2.6.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.7.0; sites on affected versions should update now. Disclosed May 2021, reported by Synacktiv.

Vulnerability Overview

The Activity Log plugin for WordPress is vulnerable to SQL Injection via the ‘orderby’ parameter in versions 2.3.5 - 2.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

Activity Log 2.3.5 – 2.6.1 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 Activity Log the fix is 2.7.0: builds 2.3.5 – 2.6.1 are affected, anything from 2.7.0 onward is not.

Remediation

Update to version 2.7.0, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/7a94229a-6316-48e7-bcaa-23cb2cc047b4

Related records

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