CVE-2024-12276

Ultimate Member <= 2.9.2 - Authenticated SQL Injection

2025-02-20 21:16
tiborisaak

Strategic Overview

Status
Patched in 2.10.0
Affected Version
<= 2.9.2
CVSS
5.3Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2024-12276
View all Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin vulnerabilities

At a glance

CVE-2024-12276 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Ultimate Member WordPress plugin, affecting versions <= 2.9.2. It carries a CVSS score of 5.3 (reachable over the network; high confidentiality impact). Exploitation requires an authenticated account. The issue is fixed in version 2.10.0; sites on affected versions should update now. Disclosed February 2025, reported by tiborisaak.

Vulnerability Overview

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to second-order SQL Injection via filenames in all versions up to, and including, 2.9.2 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, with access to upload files and manage filenames through a third-party plugin like a File Manager, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The risk of this vulnerability is very minimal as it requires a user to be able to manipulate filenames in order to successfully exploit.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Ultimate Member <= 2.9.2 takes any authenticated account. 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 Ultimate Member the fix is 2.10.0: builds <= 2.9.2 are affected, anything from 2.10.0 onward is not.

Remediation

Update to version 2.10.0, or a newer patched version

How does WordSec protect against this?

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