Loginizer Security
Approved changes feed: RSS · Atom
cpe:2.3:a:softaculous:loginizer_security:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Softaculous (65f23925-db99-5043-a6d0-39da9bceb2f5) |
|---|---|
| Product | Loginizer Security (b2037723-cb47-58a5-9c30-efc1e2a6149a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-10097 |
vulnerable | 2026-06-03 14:54:04.886435 |
Loginizer Security and Loginizer <= 1.9.2 - Authentication Bypass via WordPress.com OAuth provider
HIGH (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.
Published: 2024-11-05T06:42:46.533Z
Updated: 2026-04-08T16:55:58.714Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.