CVE-2024-31375
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 Saleswonder Team: Tobias WP2LEADS wp2leads.This issue affects WP2LEADS: from n/a through <= 3.2.7.
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 WP2LEADS WordPress plugin up to version 3.2.7 has a missing authorization vulnerability, allowing users with low-privileged accounts (such as subscribers) to potentially access or modify data or perform actions that should require higher-level permissions. The specific affected endpoints or functions are not detailed in the available description.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 WP2LEADS plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for WP2LEADS in the listAffected if WP2LEADS plugin is present in the plugins directory
-
Check installed WP2LEADS versionIn Plugins list, click on the plugin to view details, or check the plugin main file header for 'Version:' valueAffected if Version is 3.2.7 or lower (any version up to and including 3.2.7)
-
Identify low-privileged user rolesGo to Users > All Users and review the roles assigned. Look for 'Subscriber' role usersAffected if Any subscriber-level accounts exist on the site
-
Check if plugin exposes AJAX endpointsReview plugin PHP files for 'add_action("wp_ajax_' hooks and verify if any lack capability checks via 'current_user_can()' before processingAffected if AJAX actions exist without capability checks, allowing subscriber-level access
-
Inspect admin function accessibilityReview plugin PHP files for 'add_menu_page' or 'add_submenu_page' calls and check if admin functions lack permission callbacksAffected if Admin pages or functions lack proper capability verification
A site is affected if WP2LEADS version 3.2.7 or lower is installed AND low-privileged subscriber accounts exist with potential access to unprotected AJAX or admin functions.
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 dataImplement proper capability checks (e.g., current_user_can()) and nonce verification on all sensitive AJAX actions and admin functions within the plugin. Update to the latest patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31375 — 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-31375 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