Login As UsersWordPress extension · Geekcodelab
CVE-2024-43982
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 · uneditedMissing Authorization vulnerability in Geek Code Lab Login As Users allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Login As Users: from n/a through 1.4.3.
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 · moderate confidenceThe Login As Users plugin by Geek Code Lab contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This means the plugin fails to properly verify user permissions before allowing the 'Login As' functionality to be executed, potentially allowing lower-privileged users to impersonate other users including administrators.
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
Login As UsersWordPress extension
<= 1.4.4CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm plugin is installedLocate the Geekcodelab Login As Users plugin in your WordPress installation under wp-content/plugins/ directory, or check via WordPress admin Plugins pageAffected if Plugin directory 'login-as-users' exists or plugin appears in WordPress plugin list
-
Identify installed versionOpen the main plugin file (usually login-as-users.php) and locate the Version header in the plugin comment block, or view version in WordPress plugin admin panelAffected if Version number is 1.4.4 or lower
-
Verify plugin is activeCheck WordPress admin under Plugins > Installed Plugins to confirm the Geekcodelab Login As Users plugin is activatedAffected if Plugin is currently active on the WordPress site
-
Check user access controlsReview user roles and capabilities assigned to non-administrator users; attempt to determine if lower-privileged users can access the Login As functionalityAffected if Non-admin users have been granted or can access the Login As capability without proper authorization checks
Your environment is affected if the Geekcodelab Login As Users plugin is active at version 1.4.4 or lower, as the missing authorization vulnerability allows improper permission verification before the Login As function executes.
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.
dbcve · scopedUpgrade to the latest version of Login As Users plugin which should contain proper authorization checks. If no update is available, restrict access to the plugin's functionality to trusted administrators only and audit user roles/permissions.
1.4.4
- Update the Login As Users plugin to version 1.4.4 or later via the WordPress plugin repository, theme composer, or managed hosting dashboard
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Login As Users
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-43982 — 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-2024-43982 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