dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-3237

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
The ConvertPlug plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the cp_dismiss_notice() function in all versions up to, and including, 3.5.25. This makes it possible for authenticated attackers, with subscriber-level access and above, to update arbitrary option values to true.

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

The ConvertPlug WordPress plugin has a missing capability check on the cp_dismiss_notice() function, allowing any authenticated user with subscriber-level access or higher to update arbitrary WordPress options to true. This Broken Access Control vulnerability in versions up to 3.5.25 enables privilege escalation through unauthorized option manipulation.

MitigationUpdate ConvertPlug to version 3.5.26 or later which includes proper capability verification. If an update is unavailable, disable the plugin or restrict access via a WAF rule blocking the vulnerable endpoint.

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 checks

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

  1. Verify ConvertPlug plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ConvertPlug' or 'ConvertPlug - Popups, Optins, CTAs & Slices' in the list
    Affected if ConvertPlug appears in the installed plugins list
  2. Check installed ConvertPlug version
    In the plugins list, click on the plugin name or hover over it to reveal the version number. Compare against the affected range: any version 3.5.25 or earlier
    Affected if The version shown is 3.5.25 or earlier, or the version cannot be determined and ConvertPlug is present
  3. Confirm subscriber-level user accounts exist
    Go to Users > All Users in WordPress admin and note the role assigned to each user. Any user with 'Subscriber' role or higher satisfies the authentication requirement for this flaw
    Affected if At least one user account with Subscriber, Contributor, Author, Editor, or Administrator role exists (any authenticated user)
  4. Identify if the vulnerable endpoint is exposed
    Check if the file /wp-admin/admin-ajax.php is accessible and responds to the 'cp_dismiss_notice' action. This typically requires a POST request to admin-ajax.php with action=cp_dismiss_notice and a notice_id parameter
    Affected if The endpoint returns a successful response (HTTP 200) without requiring elevated privileges, indicating the capability check is missing

You are affected if ConvertPlug version 3.5.25 or earlier is installed, the plugin is active, and at least one authenticated user with subscriber-level access exists in WordPress.

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

Update ConvertPlug to version 3.5.26 or later which includes proper capability verification. If an update is unavailable, disable the plugin or restrict access via a WAF rule blocking the vulnerable endpoint.

Recommended fix Moderate confidence

ConvertPlug version 3.5.26 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate ConvertPlug in the plugin list
  4. 4. Check the current version number of the plugin
  5. 5. If the installed version is 3.5.25 or lower, update the plugin to the latest available version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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