dbcve.org
Wp Ultimate ReviewWordPress extension · Wpmet

CVE-2024-32684

HIGH · 7.5 CVSS v3.1 Published 2024-04-22
Fix available
A fix is available. Upgrade to 2.3.0 or later.
See remediation →
84/100
Remediation priority · High
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 Wpmet Wp Ultimate Review.This issue affects Wp Ultimate Review: from n/a through 2.2.5.

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

This is a Missing Authorization vulnerability in the Wpmet Wp Ultimate Review WordPress plugin affecting versions up to 2.2.5. The vulnerability allows attackers to bypass proper authorization checks, likely enabling unauthorized access to review management functions or sensitive data without proper authentication or privilege validation.

MitigationUpdate to the latest version of Wp Ultimate Review when available, and review user role and capability configurations in WordPress admin to ensure least-privilege principles are applied.

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
Wp Ultimate ReviewWordPress extension
Affected:< 2.3.0

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Wp Ultimate Review' or check the main plugin file (wp-ultimate-review.php) for the 'Version' header in the plugin comments
    Affected if The version listed is 2.2.5 or lower (anything below 2.3.0)
  2. Identify plugin entry points
    Examine the main plugin file for add_action calls registering AJAX handlers (wp_ajax_*) or admin menu pages using add_menu_page or add_submenu_page
    Affected if The plugin registers any AJAX actions or admin menu pages without corresponding capability checks
  3. Review AJAX action capability verification
    Search plugin PHP files for the registered AJAX action callbacks and check if they include current_user_can(), wp_verify_nonce(), or check_admin_referer() calls before executing sensitive operations
    Affected if AJAX handlers execute review management functions without verifying user capabilities or nonces
  4. Inspect admin page capability requirements
    Look at the capability parameter in add_menu_page/add_submenu_page calls (the 7th argument) and verify it is set to a restrictive capability like 'manage_options' rather than a loose one like 'edit_posts'
    Affected if Admin pages are registered with weak or default capability settings

You are affected if the plugin version is below 2.3.0 AND the plugin exposes any review management functions without proper current_user_can() capability checks on AJAX handlers or admin pages.

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.0 or later
Fixed in 2.3.0
Interim mitigation

Update to the latest version of Wp Ultimate Review when available, and review user role and capability configurations in WordPress admin to ensure least-privilege principles are applied.

Recommended fix High confidence

2.3.0

  1. Backup your WordPress site before making any changes
  2. Update the Wp Ultimate Review plugin to version 2.3.0 or later through the WordPress admin dashboard (Plugins > Updates) or via wp-cli: wp plugin update wp-ultimate-review
  3. Verify the plugin version has been updated to 2.3.0 or higher in the plugins list
  4. Test that the review functionality works as expected after the update

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

Fix this in Wp Ultimate Review Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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