dbcve.org
Wp Ultimate ReviewWordPress extension · Wpmet

CVE-2024-32685

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-17
Fix available
A fix is available. Upgrade to 2.3.0 or later.
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
Client-Side Enforcement of Server-Side Security vulnerability in Wpmet Wp Ultimate Review allows Functionality Bypass.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 Client-Side Enforcement of Server-Side Security vulnerability in the Wp Ultimate Review WordPress plugin (versions up to 2.2.5). The plugin relies on client-side checks to enforce security functionality that should be validated server-side, allowing attackers to bypass security controls by manipulating client-side requests or code.

MitigationUpgrade to the latest version of Wp Ultimate Review plugin which should include proper server-side validation. If no update is available, audit the plugin code to identify and migrate client-side security checks to server-side equivalents.

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
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. Check if Wp Ultimate Review plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wp Ultimate Review' or check the file /wp-content/plugins/wp-ultimate-review/ for the plugin directory
    Affected if The plugin directory wp-ultimate-review exists in the WordPress plugins folder
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Wp Ultimate Review, and note the version number displayed, or read the 'Version' field from the plugin header in /wp-content/plugins/wp-ultimate-review/wp-ultimate-review.php
    Affected if The version number is less than 2.3.0 (e.g., 2.2.5, 2.2.4, etc.)
  3. Verify plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm Wp Ultimate Review shows as 'Active'
    Affected if The plugin is active and the version is below 2.3.0
  4. Identify client-side security features in use
    Review plugin settings at Reviews > Ultimate Review > Settings and look for security-related features that may rely on client-side validation (such as access controls, submission restrictions, or permission checks)
    Affected if Any security-critical features are enabled and rely on client-side checks rather than server-side validation

A user is affected if Wp Ultimate Review plugin version below 2.3.0 is installed and active, with security features that depend on client-side enforcement rather than server-side validation.

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

Upgrade to the latest version of Wp Ultimate Review plugin which should include proper server-side validation. If no update is available, audit the plugin code to identify and migrate client-side security checks to server-side equivalents.

Recommended fix Moderate confidence

Wp Ultimate Review version 2.3.0 or later

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Find 'Wp Ultimate Review' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 2.3.0 or later from the WordPress plugin repository
  5. Verify the plugin updated successfully by checking the version number
  6. Test that the review functionality works correctly 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
  • 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-32685 — 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-32685 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