CrowdSecLive Exploit Tracker
Limited ExploitationCVE-2024-1071Public Exploit

Ultimatemember - SQLi (CVE-2024-1071)

PublishedMar 13, 2024
First SeenDec 16, 2024
Last Seen
Reported
CVSS9.8
Ultimatemember
UltimatememberUser Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin
cmswordpress

Description

The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to SQL Injection via the 'sorting' parameter in versions 2.1.3 to 2.8.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 unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

psychologyCrowdSec Analysis

CVE-2024-1071 is a critical SQL injection vulnerability affecting the Ultimate Member plugin for WordPress. This flaw arises from inadequate input sanitization, allowing unauthenticated attackers to inject arbitrary SQL through the sorting parameter and potentially extract sensitive information from the database.

CrowdSec has been tracking this vulnerability and its exploits since 16th of December 2024.

CrowdSec has not observed any significant exploitation activity targeting CVE-2024-1071 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.

Typical exploitation attempts target requests with manipulated sorting parameters intended to trigger SQL injection within the plugin.

lock

Full Intelligence Available

Connect your API key to access CrowdSec scores, exploit timelines, and attacker IPs.

EventDate
CVE Published2024-03-13
Rule Released2024-12-16
CrowdSec First Seen2024-12-16

Related Weaknesses

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

The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

arrow_forward

Remediation & Protection

lock to download blocklists, subscribe to firewalls, and access IP intelligence.

External References