Is User Login History safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (2.1.8). As of 2026-11-04. 2 issues are on record for older versions; version 2.1.8 or newer fixes all of them that state a fix. Keep User Login History on the latest version (2.1.8) and remove it if you do not use it.

Which versions of User Login History are vulnerable?

Known issues on record (newest first): SQL injection (2.1.7 and older, fixed in 2.1.8); Stored cross-site scripting (XSS) (2.1.6 and older, fixed in 2.1.7). The full list with sources is on this page.

What is the latest version of User Login History?

2.1.8, according to wordpress.org (last updated 2026-03-17). It has 10,000+ active installs.

What should I do if my User Login History is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update user-login-history). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · user-login-history · data as of 2026-11-04

Is User Login History safe? Known vulnerabilities and latest version

Latest version: 2.1.8
Last updated: 2026-03-17
Active installs: 10,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 6.9.11 · PHP 7.4+

Helps you to know your website's visitors by tracking their login related information like login/logout time, country, browser and many more. — by Faiyaz Alam

What to do

Update to the latest version (2.1.8). Anything older than 2.1.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get user-login-history --field=version shows what you run; wp plugin update user-login-history updates it.

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.9 CVE-2026-2283 · published 2026-08-16

SQL injection in User Login History (2.1.7 and older)

Affected: 2.1.7 and older
Fixed in: 2.1.8 *
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-2283 Wordfence advisory Code change (fix)Plugin source

medium 6.5 CVE-2025-47676 · published 2025-05-07

Stored cross-site scripting (XSS) in User Login History (2.1.6 and older)

Affected: 2.1.6 and older
Fixed in: 2.1.7
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Faiyaz Alam User Login History user-login-history allows Stored XSS.This issue affects User Login History: from n/a through <= 2.1.6.

NVD CVE-2025-47676 Patchstack advisory

Recent activity

2026-03-17 — latest release on wordpress.org (2.1.8).
2026-08-16 — SQL injection disclosed (CVE-2026-2283), fixed in 2.1.8.
2025-05-07 — Stored cross-site scripting (XSS) disclosed (CVE-2025-47676), fixed in 2.1.7.

Free. We check the CVE feeds every day and email you only when a new issue for User Login History (user-login-history) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: SQL injection (1) · Cross-site scripting (XSS) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/user-login-history (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/user-login-history"><img src="https://laskyr.com/plugins/user-login-history/badge.svg" alt="User Login History vulnerability status"></a>

← Check another plugin · Free hacked-site scan