CVE-2026-2283: User Login History <= 2.1.7 - Authenticated (Administrator+) SQL Injection via 'blog_id' Parameter
The User Login History plugin for WordPress is vulnerable to SQL Injection via the 'blogid' 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
WordPress User Login History pluginto a version that resolves this vulnerability.Fixed in 2.1.7 - Compensating control
If you use the WordPress User Login History plugin on a multisite installation, restrict access to the WordPress admin area to trusted administrators only (since exploitation is only possible on multisite installations and requires authenticated Administrator-level access and above).
Event History
Frequently Asked Questions
What is the severity of CVE-2026-2283?
The severity of CVE-2026-2283 is rated medium with a score of 4.9.
How do I fix CVE-2026-2283?
To fix CVE-2026-2283, update the User Login History plugin to version 2.1.8 or later.
What type of vulnerability is CVE-2026-2283?
CVE-2026-2283 is an SQL Injection vulnerability affecting the User Login History plugin for WordPress.
Can CVE-2026-2283 be exploited remotely?
Yes, CVE-2026-2283 can be exploited remotely due to the nature of SQL Injection.
Who is affected by CVE-2026-2283?
Administrators with the User Login History plugin installed on WordPress sites up to version 2.1.7 are affected by CVE-2026-2283.