dbcve.org
AffiliationWordPress extension · Lws

CVE-2024-43962

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 2.3.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 LWS LWS Affiliation allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LWS Affiliation: from n/a through 2.3.4.

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 confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the LWS Affiliation WordPress plugin. The plugin fails to properly verify user permissions before allowing access to certain administrative or affiliate-related functions, allowing attackers to exploit incorrectly configured access control security levels to perform unauthorized actions.

MitigationUpdate LWS Affiliation to version 2.3.5 or later which contains the authorization fix. If immediate update is not possible, restrict access to the plugin's admin pages at the server level and audit user capabilities.

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
AffiliationWordPress extension
Affected:< 2.3.5

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
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 checks

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

  1. Verify LWS Affiliation plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'LWS Affiliation' in the list. Note the version number displayed.
    Affected if The plugin is installed and the version shown is below 2.3.5
  2. Check plugin version via file system
    If wp-admin access is limited, check the plugin header in wp-content/plugins/lws-affiliation/lws-affiliation.php for the 'Version' field.
    Affected if The Version field shows a number lower than 2.3.5
  3. Identify admin user roles with affiliate access
    Navigate to Users > All Users in WordPress admin and review which roles have access to the LWS Affiliation plugin pages. Check each role's capability settings.
    Affected if Any user role with 'subscriber' level or below, or any untrusted role, has access to the plugin's administrative functions
  4. Test access to affiliate management endpoints
    Attempt to access the LWS Affiliation plugin admin pages (typically under 'Affiliation' in the left sidebar) using a low-privilege account (e.g., subscriber, contributor, or custom limited role).
    Affected if A user without Administrator role can view or modify affiliate settings, statistics, or withdrawal requests

You are affected if the LWS Affiliation plugin version is below 2.3.5 AND any user with limited privileges can access or modify affiliate-related administrative 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.

dbcve · scoped
Upgrade available Upgrade to 2.3.5 or later
Fixed in 2.3.5
Interim mitigation

Update LWS Affiliation to version 2.3.5 or later which contains the authorization fix. If immediate update is not possible, restrict access to the plugin's admin pages at the server level and audit user capabilities.

Recommended fix High confidence

2.3.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'LWS Affiliation' plugin
  4. Check if the current version is below 2.3.5
  5. If vulnerable, click 'Update Now' to upgrade to the latest version
  6. Alternatively, navigate to Dashboard > Updates and update all plugins that have updates available
  7. After updating, verify the plugin version shows 2.3.5 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Affiliation 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 the upgrade done

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-43962 — 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-43962 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