WordPress plugin · Updated daily · Source: Wordfence Intelligence

Persistent Login vulnerabilities: affected versions and fixes

Persistent Login has 5,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Persistent Login at a glance

  • 5 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Sep 30, 2026.
  • Ranked #2933 by popularity on WordPress.org (5,000+ active installs).
  • The latest version is 3.1.6 (released Nov 8, 2026). The most recent security fix shipped in 3.1.4.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Persistent Login version

Enter the Persistent Login version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Persistent Login”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Persistent Login”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.1.6). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Persistent Login vulnerabilities

  • Persistent Login <= 3.1.3 - Unauthenticated Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2026-94081

    Affected versions: ≤ 3.1.3

    Fixed in: 3.1.4

    Severity: High 7.2 · Disclosed Sep 30, 2026

  • Persistent Login <= 3.1.0 - Authenticated (Subscriber+) SQL Injection via 'wppl_device_id' Cookie

    SQL injection · CVE-2026-18752

    Affected versions: ≤ 3.1.0

    Fixed in: 3.1.1

    Severity: Medium 6.5 · Disclosed Aug 31, 2026

  • Persistent Login <= 3.1.0 - Authenticated (Subscriber+) SQL Injection

    SQL injection · CVE-2026-66594

    Affected versions: ≤ 3.1.0

    Fixed in: 3.1.1

    Severity: Medium 6.5 · Disclosed Aug 19, 2026

  • Freemius SDK <= 2.5.9 - Reflected Cross-Site Scripting via fs_request_get

    Cross-site scripting (XSS) · CVE-2023-33999

    Affected versions: ≤ 2.0.14

    Fixed in: 2.0.15

    Severity: Medium 6.1 · Disclosed Jul 18, 2023

  • Freemius SDK <= 2.4.2 - Missing Authorization Checks

    Missing authorization · CVE-2022-4974

    Affected versions: < 2.0.0

    Fixed in: 2.0.0

    Severity: Medium 6.3 · Disclosed Mar 4, 2022

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Sep 30, 2026.

Most common weaknesses in Persistent Login

Cross-site scripting (XSS)

2 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

SQL injection

2 issues

Input such as a form field can be used to rewrite the queries the site sends to its database. Attackers use it to pull out customer, member or order data.

Missing authorization

1 issue

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

Frequently asked questions

Is Persistent Login safe to use?

Persistent Login is a well-known plugin with 5,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.1.6) and turn on automatic updates.

How do I find which version of Persistent Login my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesPersistent Login on WordPress.org