dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-32802

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-17
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 WordPlus BP Better Messages allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects BP Better Messages: from n/a through 2.4.32.

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

Missing Authorization vulnerability in WordPlus BP Better Messages WordPress plugin allows unauthenticated or unauthorized users to access functionality that should be restricted by Access Control Lists (ACLs). The vulnerability exists in versions up to 2.4.32 and permits accessing sensitive messaging features without proper capability checks.

MitigationUpdate BP Better Messages to the latest version available from WordPress.org, which should contain proper capability checks and authorization controls. If no update is available, restrict access to the affected plugin functions at the web server level until a patch is released.

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. Confirm BP Better Messages plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins/ directory for a folder named 'bp-better-messages' or similar
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    In WordPress admin, view the plugin details to see the version number, or open the main plugin PHP file and look for the Version header in the plugin comment block
    Affected if Version number displayed is 2.4.32 or lower
  3. Verify plugin is active
    Check the Plugins page in WordPress admin - the plugin should show as 'Active' under the BP Better Messages listing
    Affected if Plugin is currently activated on the site
  4. Confirm messaging functionality is accessible
    Test whether public-facing messaging endpoints (such as REST API routes or AJAX actions related to messaging) respond without requiring authentication or capability verification
    Affected if Messaging features respond to unauthenticated requests without proper authorization headers or capability checks

The environment is affected if BP Better Messages plugin is installed, active, and running version 2.4.32 or lower, with messaging features accessible without proper capability verification.

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 BP Better Messages to the latest version available from WordPress.org, which should contain proper capability checks and authorization controls. If no update is available, restrict access to the affected plugin functions at the web server level until a patch is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-32802 — 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-32802 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