User Activity Log <= 1.6.2 - Unauthenticated SQL Injection via username

2023-07-14 00:00
Anonymous

Strategic Overview

Status
Patched in 1.6.3
Affected Plugin
User Activity Log
Affected Version
<= 1.6.2
CVSS
8.1High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE pending
View all User Activity Log 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 User Activity Log WordPress plugin, affecting versions <= 1.6.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.6.3; sites on affected versions should update now. Disclosed July 2023.

Vulnerability Overview

The User Activity Log plugin for WordPress is vulnerable to generic SQL Injection via the username value when logging in in versions up to, and including, 1.6.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query in the ual_shook_wp_login_failed function. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The login_failed_non_existing_user option must be enabled for this to be successful.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, 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 User Activity Log <= 1.6.2 takes no account at all. 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 User Activity Log the fix is 1.6.3: builds <= 1.6.2 are affected, anything from 1.6.3 onward is not.

Remediation

Update to version 1.6.3, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: User Activity Log 1.6.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/8483196e-f476-41e5-a988-bcd8a9952a64

Related records

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