dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-43277

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Missing Authorization vulnerability in AyeCode Ltd UsersWP allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects UsersWP: from n/a through 1.2.15.

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 confidence

A missing authorization vulnerability in UsersWP plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to user data or administrative functions due to improper authorization checks.

MitigationUpdate UsersWP to the latest patched version and review all access control points to ensure proper authorization checks are enforced before granting access to sensitive functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify UsersWP plugin installation and version
    Navigate to WordPress admin dashboard > Plugins section, locate UsersWP, and note the installed version number. Alternatively, check the plugin files in wp-content/plugins/userswp/ for the version in the main PHP file or readme.txt
    Affected if UsersWP plugin is installed and the version is earlier than the patched release (compare to official WordPress repository for current patched version)
  2. Identify active UsersWP endpoints and functionality
    Review the UsersWP settings at UsersWP > Settings. Check which modules are enabled, particularly user registration, profile management, and any public-facing user data display features
    Affected if Any UsersWP public endpoints or user data modules are active without additional access restrictions
  3. Inspect user role and capability configurations
    Go to UsersWP > Settings > Access/Privacy and review which user roles can access profile data, user directories, and administrative functions. Check if any settings allow unauthenticated or lower-privileged users to access higher-privilege data
    Affected if Access control settings permit unauthenticated users or standard registered users to view administrative data or access restricted features
  4. Test for authorization bypass on sensitive functions
    Using a low-privileged test account or unauthenticated browser session, attempt to access direct UserWP URLs such as profile edit pages, user directory listings, or admin-function endpoints that should require elevated privileges
    Affected if Unauthenticated or standard users can access pages or data that should require administrator-level authorization
  5. Review access logs for unauthorized access patterns
    Check WordPress debug logs, server access logs, or security plugin logs for repeated requests to UsersWP endpoints from unexpected IP ranges or users attempting to access restricted areas
    Affected if Logs show successful access to protected UsersWP functions by users lacking proper authorization roles

A user is affected if the UsersWP plugin is installed with any public-facing functionality and access controls do not properly enforce authorization checks before granting access to sensitive user data or admin functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update UsersWP to the latest patched version and review all access control points to ensure proper authorization checks are enforced before granting access to sensitive functionality.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43277 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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