Reported vulnerability

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

Q: How do I check which product and version this report affects?

This report covers more than one product. Choose your plugin, theme or WordPress core in the version checker, then enter its installed version. Each product has its own affected ranges and fix details in the report above.

Q: Which update should I install?

Find your exact product in the report and read its fixed versions and recommended action. Fix details for one product do not apply to every product covered by this advisory. Follow the linked source when no fixed version is specified.

Q: Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

Q: Does a version outside these ranges mean my website is secure?

A version outside the reported ranges is not listed as affected by this particular issue. Other vulnerabilities, missing information or a previous compromise still need separate checks. Review other reports for your product and keep your website maintained.

Published 4 Nov 2024

Updated 19 Feb 2025

CVE-2024-10097

Compare your installed software with the affected versions below. Follow the source’s remediation guidance and test an available update after taking a backup. A database entry describes a reported issue; it does not establish whether a particular website has been compromised.

Does this affect my version?

Check your installed version against this advisory. This compares the report’s version ranges and does not scan your website.

Wordfence advisory

high · CVSS 8.1

The Loginizer Security and Loginizer plugins for WordPress are vulnerable to authentication bypass in all versions up to, and including, 1.9.2. This is due to insufficient verification on the user being returned by the social login token. This makes it possible for unauthenticated attackers to log in as any existing user on the site, such as an administrator, if they have access to the email and the user does not have an already-existing account for the service returning the token.

Severity vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Loginizer Security

Software: plugin · loginizer-security
Affected versions: Start version unspecified, through 1.9.2
Fix availability: Fix available
Fixed versions: 1.9.3

Recommended action

Update to version 1.9.3, or a newer patched version

Loginizer

Software: plugin · loginizer
Affected versions: Start version unspecified, through 1.9.2
Fix availability: Fix available
Fixed versions: 1.9.3

Recommended action

Update to version 1.9.3, or a newer patched version

Further references (1)

wordfence.com/threat-intel/vulnerabilities/id/5db00b22-d766-4fde-86fe-98d90936028c?source=api-prod

Data sources and licences

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.

Read licence terms

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.

Read licence terms

Source: Wordfence

Need help fixing this issue?

Get help checking your site, applying an available update and resolving any problems after updating.

Get help with this issue

Questions about this vulnerability

How do I check which product and version this report affects?

This report covers more than one product. Choose your plugin, theme or WordPress core in the version checker, then enter its installed version. Each product has its own affected ranges and fix details in the report above.

Which update should I install?

Find your exact product in the report and read its fixed versions and recommended action. Fix details for one product do not apply to every product covered by this advisory. Follow the linked source when no fixed version is specified.

Does an affected version mean my website has been hacked?

An affected version means the installed release matches a vulnerability described in this report. It does not show whether anyone has exploited it on your website. The checker compares version numbers with stored reports; it does not inspect your website.

Does a version outside these ranges mean my website is secure?

A version outside the reported ranges is not listed as affected by this particular issue. Other vulnerabilities, missing information or a previous compromise still need separate checks. Review other reports for your product and keep your website maintained.

These reports cover at least one of the same plugins, themes or WordPress core. Check each report’s affected versions separately.

Back to vulnerability database

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

Does this affect my version?

Wordfence advisory

Loginizer Security

Recommended action

Loginizer

Recommended action

Need help fixing this issue?

Questions about this vulnerability

Other reports for the same product