Skip to main content
WordPress plugin recordReviewed

Loginizer vulnerability records, and how to read its Brute Force, 2FA and reCAPTCHA screens

Loginizer's listing says it blocks login for an IP after it reaches the maximum retries allowed, and the vendor's upgrade page says its Pro version needs a separate plugin named Loginizer Security.

A record title names both. Set your installed version against each record, then read the lockout figures, 2FA roles, CAPTCHA forms and failed login log.

Loginizer vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 8 records for Loginizer. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 1.9.3

Worked out from data retrieved on .

Every affected range listed in this source for Loginizer ends before version 1.9.3.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Loginizer Security and Loginizer <= 1.9.2 - Authentication Bypass via WordPress.com OAuth provider

    Published:
    Last updated:
    Severity:
    High (CVSS 8.1)
    Affected versions
    • All versions up to and including 1.9.2

    Patched versions: 1.9.3

    Update to at least version 1.9.3.

  2. Loginizer <= 1.7.8 - Reflected Cross-Site Scripting via 'limit_session[count]'

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 1.7.8

    Patched versions: 1.7.9

    Update to at least version 1.7.9.

  3. Loginizer <= 1.7.5 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    Medium (CVSS 4.3)
    Affected versions
    • All versions before 1.7.6

    Patched versions: 1.7.6

    Update to at least version 1.7.6.

  4. Loginizer <= 1.7.5 - Reflected Cross-Site Scripting via 'name'

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • All versions up to and including 1.7.5

    Patched versions: 1.7.6

    Update to at least version 1.7.6.

  5. Loginizer <= 1.6.3 - SQL Injection

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions before 1.6.4

    Patched versions: 1.6.4

    Update to at least version 1.6.4.

Show 3 older records
  1. Loginizer 1.3.8-1.3.9 - Unauthenticated Stored Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 6.1)
    Affected versions
    • From version 1.3.8 up to and including 1.3.9

    Patched versions: 1.4.0

    Update to at least version 1.4.0.

  2. Loginizer <= 1.3.5 - Blind SQL Injection

    Published:
    Last updated:
    Severity:
    Critical (CVSS 9.8)
    Affected versions
    • All versions before 1.3.6

    Patched versions: 1.3.6

    Update to at least version 1.3.6.

  3. Loginizer <= 1.3.5 - Cross-Site Request Forgery

    Published:
    Last updated:
    Severity:
    High (CVSS 8.8)
    Affected versions
    • All versions before 1.3.6

    Patched versions: 1.3.6

    Update to at least version 1.3.6.

Check Loginizer on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

Where Loginizer takes input, and who reaches its screens

Loginizer is published on WordPress.org by Softaculous.

Its listing describes a plugin that blocks login for an IP address after it reaches the maximum retries allowed, with IP blacklists and whitelists. Its "Pro Features" include "Two Factor Auth via Email", "Two Factor Auth via App", "reCAPTCHA" and "Social Login".

Failed logins are where visitor input lands: the vendor's logs page says its table shows the IP address of each user attempting to log in, the last username used and the exact URL of the page where they attempted to log in, which it says includes attempts on the login page as well as xml-rpc.

The vendor's reCAPTCHA page lists the login, lost password, reset password, registration and comment forms as the available forms where reCAPTCHA will appear, and says you choose the forms where you want to enable it.

The vendor's two-factor page says that as an admin you can enable all of its methods and let each user choose, and that each user then sees a "My Security" link in the left menu. WordPress's roles page says an Administrator has access to all administration features within a single site.

Reading the Loginizer records: a title that names Loginizer Security and Loginizer

The records here are those the source data files under the WordPress.org slug loginizer.

The title of CVE-2024-10097 begins "Loginizer Security and Loginizer" and ends "Authentication Bypass via WordPress.com OAuth provider" (affected: all versions up to and including 1.9.2; patched: 1.9.3). The vendor's upgrade page says the Pro version needs a separate plugin named Loginizer Security. Being filed under this slug does not settle whether a record covers that plugin, so on a paid site, write down the version of each row.

SQL injection and cross-site scripting each recur. CVE-2020-27615 has a title ending "SQL Injection" (affected: all versions before 1.6.4; patched: 1.6.4), and CVE-2017-12650 one ending "Blind SQL Injection" (affected: all versions before 1.3.6; patched: 1.3.6). CVE-2022-45084 has one ending "Reflected Cross-Site Scripting via 'name'" (affected: all versions up to and including 1.7.5; patched: 1.7.6).

Of the titles named here, only CVE-2018-11366 states an access level, ending "Unauthenticated Stored Cross-Site Scripting". Its range starts partway through the version line, from version 1.3.8 up to and including 1.3.9 (patched: 1.4.0), so a version below 1.3.8 sits outside it, though versions before 1.3.6 sit inside the range of CVE-2017-12650.

Titles and fields can word a bound differently: the title of CVE-2020-27615 begins "Loginizer <= 1.6.3", while its affected range reads all versions before 1.6.4. Where the two differ, go by the record's affected range and patched versions field. On Loginizer's WordPress.org listing, the changelog tags some entries "Security" or "Security Fix", and those entries are a second place to read before planning an update.

Where each Loginizer check is read, screen by screen

Each check is reading and writing down, on a site you are authorised to review.

Leave every screen without pressing "Save Settings" or any other button.

Plugin version, and any Loginizer Security row

Copy the version from the Loginizer row's Description column, which WordPress's Plugins screen page says includes the version number. 1 min read

Brute force rules under Brute Force Settings

The vendor's brute force page says to go to Loginizer Security > Brute Force and scroll to "Brute Force Settings"; the listing says the default configuration can be changed from the Loginizer > Brute force page. 1 min read

Two-factor methods, roles and enforcement

The listing places "Two Factor Auth via Email" and "Two Factor Auth via App" under "Pro Features", and the vendor's two-factor page sends you to Loginizer Security > Two Factor Auth. 1 min read

CAPTCHA type and the forms it covers

The listing also puts "reCAPTCHA" under "Pro Features"; the vendor's page sends you to Loginizer Security > reCAPTCHA. 1 min read

Failed login logs, and where the emails go

The vendor calls the log the "Failed Login Attempts Logs" tab, and the plugin's own text holds that heading in the same file as "Brute Force Settings". 1 min read

Settings a Loginizer version match leaves unread

Matching the installed version to the history cannot tell you the "Max Retries" figure saved, which ranges are on the whitelist and whose they are, which roles "Apply 2FA to Roles" covers, which forms "Show Captcha On" includes, or whether a Loginizer Security plugin has its licence key installed.

A version inside a record's range means exposure to that record, and says nothing about whether a flaw was used on this site.

For accounts, a WordPress security audit checks that every administrator and editor, not only whoever set up the plugin, is covered by two-factor. It lists the accounts holding an application password and tests whether the login form's lockout and two-factor controls also apply to requests signed with one.

Frequently asked questions

Each record carries its own range. CVE-2024-10097 lists all versions up to and including 1.9.2, with 1.9.3 in its patched versions field, while CVE-2018-11366 lists only versions from 1.3.8 up to and including 1.3.9. Set the installed Loginizer version against every record in the history on this page, and only then read the update guidance at the top of the history.

The records are those the source data files under the slug loginizer, and being filed there does not settle the paid edition, even where a title begins "Loginizer Security and Loginizer". The vendor's upgrade page says the Pro version needs a separate plugin named Loginizer Security, downloaded from the Client area while the licence is active, and that it will automatically upgrade if the licence is active.

The WordPress.org listing puts "Two Factor Auth via Email", "Two Factor Auth via App" and "reCAPTCHA" under "Pro Features". Its "Free Features" start with brute force protection, which the vendor's brute force page says is available in the Free as well as Pro version, and include failed login attempt logs and IP blacklists and whitelists.

The vendor's page on the "Failed Login Attempts Logs" tab says the "URL Attacked" column includes login attempts on the login page as well as xml-rpc, so you can tell which one was the target. The listing's "Pro Features" also include "Disable XML-RPC" and "Rename XML-RPC", the second described as renaming XML-RPC to something different from xmlrpc.php.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to every record listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.