Loginizer Security and Loginizer <= 1.9.2 — Authentication Bypass via WordPress.com OAuth provider
CVE-2024-10097Published · Updated Action summary
Loginizer: Affected: ≤1.9.2Update to 1.9.3 or newer
Loginizer Security: Affected: ≤1.9.2Update to 1.9.3 or newer
All remediation steps- Severity
- High8.1
- CVSS
- 8.1CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HWhat does this vector mean?
AV:NAttack vector- Network
AC:HAttack complexity- High
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:HConfidentiality- High
I:HIntegrity- High
A:HAvailability- High
- Weakness
- CWE-287 Improper Authentication
- Required access
- No account needed
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
Loginizer loginizer
- Affected≤ 1.9.2
- Patched in1.9.3
Update to 1.9.3 or newer.
You are affected if you run ≤ 1.9.2. Version 1.9.3 and later are not affected by this issue.
Loginizer Security loginizer-security
- Affected≤ 1.9.2
- Patched in1.9.3
Update to 1.9.3 or newer.
You are affected if you run ≤ 1.9.2. Version 1.9.3 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Loginizer.
- No admin access? Run a passive check of your site. It reads public files only.
- No account is needed to exploit this. Treat any exposed site on an affected version as at risk.
What to do
- Update to version 1.9.3, or a newer patched version
- Update to version 1.9.3, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch Loginizer to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to wesley (wcraft).
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in Loginizer
All 8| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.1 | Reflected Cross-Site Scripting via 'limit_session[count]' ≤1.7.8Update to 1.7.9 | CVE-2023-2296 | |
| Medium4.3 | Cross-Site Request Forgery <1.7.6Update to 1.7.6 | CVE-2022-45079 | |
| Medium6.1 | Reflected Cross-Site Scripting via 'name' ≤1.7.5Update to 1.7.6 | CVE-2022-45084 | |
| Critical9.8 | SQL Injection <1.6.4Update to 1.6.4 | CVE-2020-27615 | |
| Medium6.1 | Unauthenticated Stored Cross-Site Scripting 1.3.8 – 1.3.9Update to 1.4.0 | CVE-2018-11366 |
- Medium6.1Reflected Cross-Site Scripting via 'limit_session[count]'
≤1.7.8Update to 1.7.9
- Medium4.3Cross-Site Request Forgery
<1.7.6Update to 1.7.6
- Medium6.1Reflected Cross-Site Scripting via 'name'
≤1.7.5Update to 1.7.6
- Critical9.8SQL Injection
<1.6.4Update to 1.6.4
- Medium6.1Unauthenticated Stored Cross-Site Scripting
1.3.8 – 1.3.9Update to 1.4.0
Timeline
CVE published
Severity high, CVSS 8.1
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- [object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.