Zm Ajax Login \& RegisterWordPress extension · Zm Ajax Login \& Register Project
CVE-2023-2027
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe ZM Ajax Login & Register plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.0.2. This is due to insufficient verification on the user being supplied during a Facebook login through the plugin. 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 username.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe ZM Ajax Login & Register WordPress plugin versions up to 2.0.2 contain an authentication bypass vulnerability in the Facebook login functionality. Insufficient verification of the user identity during the Facebook OAuth process allows unauthenticated attackers to log in as any existing user on the site (including administrators) by supplying a valid username.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Zm Ajax Login \& RegisterWordPress extension
<= 2.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'ZM Ajax Login & Register' in the list.Affected if The plugin ZM Ajax Login & Register appears in the installed plugins list.
-
Check the installed version numberIn the Plugins list, locate ZM Ajax Login & Register and note the version number displayed beneath the plugin name.Affected if The version number is 2.0.2 or lower (any version up to and including 2.0.2).
-
Confirm Facebook login feature is activeGo to the plugin settings page (ZM Ajax Login & Register settings). Look for Facebook login configuration options and verify if Facebook login is enabled or configured.Affected if Facebook login functionality is enabled or configured in the plugin settings.
-
Review recent admin user sessionsCheck WordPress user activity logs or audit logs for any unexpected login activity, particularly logins occurring at unusual times or from unknown IP addresses, that correspond to administrator accounts.Affected if There are admin user logins that you cannot attribute to legitimate administrators.
A user is affected if the ZM Ajax Login & Register plugin version 2.0.2 or lower is installed with Facebook login enabled, as this combination allows the authentication bypass to be exploited.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the ZM Ajax Login & Register plugin to version 2.0.3 or later. Until the update can be applied, disable the Facebook login feature or the entire plugin to prevent exploitation.
Fix this in Zm Ajax Login \& Register
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2027 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2027 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data