HomeWordPress vulnerabilitiesUser Login History
User Login History vulnerabilities
User Login History has 2 known vulnerabilities in this database. The most recent published record is dated 16 Aug 2026.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 2.1.8
- Last updated
- 17 Mar 2026
- Most recent
- 16 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| SQL injection CVE-2026-2283 | Medium 4.9 | Up to 2.1.7 | Fixed in a later version (latest 2.1.8) | 16 Aug 2026 |
| Cross-site scripting (XSS) CVE-2017-15867 | Medium 6.1 | Up to 1.5.2 | Fixed in a later version (latest 2.1.8) | 24 Oct 2017 |
Read the published descriptions
- CVE-2026-2283, 16 Aug 2026
- 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. CVE record
- CVE-2017-15867, 24 Oct 2017
- Multiple cross-site scripting (XSS) vulnerabilities in the user-login-history plugin through 1.5.2 for WordPress allow remote attackers to inject arbitrary web script or HTML via the (1) date_from, (2) date_to, (3) user_id, (4) username, (5) country_name, (6) browser, (7) operating_system, or (8) ip_address parameter to admin/partials/listing/listing.php. CVE record
What to do if you run User Login History
If you run User Login History, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new User Login History vulnerabilities
Free. We email you when a new vulnerability is published for User Login History, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.