CVE-2026-2283
Received Received - Intake

SQL Injection in WordPress User Login History Plugin

Publication date: 2026-08-16

Last updated on: 2026-08-16

Assigner: Wordfence

Description
The User Login History plugin for WordPress is vulnerable to SQL Injection via the 'blog_id' parameter in all versions up to, and including, 2.1.7. This is 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 Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is only exploitable on multisite installations.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-16
Last Modified
2026-08-16
Generated
2026-08-16
AI Q&A
2026-08-16
EPSS Evaluated
N/A
NVD
CVE-2026-2283
EUVD
EUVD-2026-59896

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
wp_user_login_history plugin to 2.1.7 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 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.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL Injection flaw in the User Login History WordPress plugin versions up to 2.1.7. It occurs due to insufficient escaping of the 'blog_id' parameter and lack of proper SQL query preparation. Authenticated attackers with Administrator-level access or higher can exploit this to inject malicious SQL queries into existing ones, potentially extracting sensitive database information. The vulnerability only affects multisite WordPress installations.

Detection Guidance

Detection requires checking for the User Login History plugin version up to 2.1.7 on WordPress multisite installations. No specific commands are provided in the context, but monitoring for unusual SQL queries or database access patterns may help.

Impact Analysis

If you are an administrator on a multisite WordPress installation using the User Login History plugin up to version 2.1.7, an attacker with admin access could exploit this to steal sensitive data from your database, such as user credentials or other confidential information.

Compliance Impact

This vulnerability could lead to unauthorized access and exposure of personal data, which may violate compliance requirements under GDPR, HIPAA, or other regulations. Organizations could face legal penalties, reputational damage, and loss of trust due to data breaches resulting from this flaw.

Mitigation Strategies

Immediately update the User Login History plugin to the latest version beyond 2.1.7. If updates are unavailable, consider disabling the plugin until a patch is released. Restrict Administrator-level access to reduce attack surface.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-2283. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart