HomeWordPress vulnerabilitiesDoLogin Security
DoLogin Security vulnerabilities
DoLogin Security has 4 known vulnerabilities in this database. The most recent published record is dated 8 Jul 2026.
- Known vulnerabilities
- 4
- Active installs
- 8,000+
- Latest version
- 5.0.10
- Last updated
- 16 Aug 2026
- Most recent
- 8 Jul 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 |
|---|---|---|---|---|
| Authentication bypass CVE-2026-14495 | High 8.8 | Up to 4.3 | Fixed in a later version (latest 5.0.10) | 8 Jul 2026 |
| Security weakness CVE-2023-4800 | Medium 6.5 | Before 3.7.1 | Fixed in 3.7.1 | 16 Oct 2023 |
| Cross-site scripting (XSS) CVE-2023-4549 | Medium 6.1 | Before 3.7 | Fixed in 3.7 | 25 Sep 2023 |
| Security weakness CVE-2023-4631 | Medium 5.3 | Before 3.7 | Fixed in 3.7 | 25 Sep 2023 |
Read the published descriptions
- CVE-2026-14495, 8 Jul 2026
- The DoLogin Security plugin for WordPress is vulnerable to Authentication Bypass via Insufficient Randomness in all versions up to, and including, 4.3. The vulnerability exists because `dologin\s::rrand()` seeds the Mersenne Twister with `mt_srand((double) microtime() * 1000000)` - discarding the integer-seconds component of `microtime()` and constraining the seed to a range of approximately 10^6 values (~20 bits of entropy) - after which every character of the 32-character magic-link token is drawn sequentially with `mt_rand()`, making the entire token a deterministic function of that seed. Because `Pswdless::try_login()` is registered on the unauthenticated `init` hook, resolves the target account by the auto-increment numeric ID embedded in the `?dologin=<id>.<hash>` parameter, performs the hash comparison using a non-constant-time `!=` operator, and then calls `wp_set_auth_cookie()` directly - never passing through `wp_authenticate()` and therefore never triggering the plugin's own `Auth::_has_login_err()` lockout - an unauthenticated attacker can brute-force the ~10^6-candidate seed space to reconstruct an active passwordless login token and authenticate as any targeted user, including administrators, without a password. Exploitation requires that a valid, unexpired passwordless login link (active for up to 7 days) exists for the target account at the time of the attack, and that the numeric link ID is known or guessable from the auto-increment primary key. CVE record
- CVE-2023-4800, 16 Oct 2023
- The DoLogin Security WordPress plugin before 3.7.1 does not restrict the access of a widget that shows the IPs of failed logins to low privileged users. CVE record
- CVE-2023-4549, 25 Sep 2023
- The DoLogin Security WordPress plugin before 3.7 does not properly sanitize IP addresses coming from the X-Forwarded-For header, which can be used by attackers to conduct Stored XSS attacks via WordPress' login form. CVE record
- CVE-2023-4631, 25 Sep 2023
- The DoLogin Security WordPress plugin before 3.7 uses headers such as the X-Forwarded-For to retrieve the IP address of the request, which could lead to IP spoofing. CVE record
What to do if you run DoLogin Security
If you run DoLogin Security, 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 DoLogin Security vulnerabilities
Free. We email you when a new vulnerability is published for DoLogin Security, 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.