dbcve.org
Wp Ultimate ReviewWordPress extension · Wpmet

CVE-2023-46085

HIGH · 8.8 CVSS v3.1 Published 2023-10-22
Fix available
A fix is available. Upgrade to after 2.2.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Wpmet Wp Ultimate Review plugin <= 2.2.4 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Wpmet Wp Ultimate Review WordPress plugin versions 2.2.4 and below allows attackers to trick authenticated users into performing unintended actions by forging HTTP requests.

MitigationUpdate the Wpmet Wp Ultimate Review plugin to a version higher than 2.2.4 which contains the CSRF fix.

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.2.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Locate plugin installation directory
    Check the WordPress plugins folder at /wp-content/plugins/ for a folder named 'wpmet-wp-ultimate-review' or similar variant containing 'wpmet' and 'ultimate-review'
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    Open the main plugin PHP file (usually named index.php or wpmet-wp-ultimate-review.php) and locate the version in the plugin header comment, or check the readme.txt file's 'Stable tag' field
    Affected if The version listed is 2.2.4 or lower, or if no version is found but the plugin is present
  3. Verify plugin is active
    In WordPress admin, navigate to Plugins > Installed Plugins and check if Wpmet Wp Ultimate Review shows as 'Active'
    Affected if The plugin is active and running on the site
  4. Check for authenticated access to review features
    The vulnerability affects any authenticated user action - verify if user registration is enabled or if there are existing user accounts that could be targeted for CSRF attacks
    Affected if The site allows user registration or has existing registered users with access to review-related functionality

A user is affected if the Wpmet Wp Ultimate Review plugin version 2.2.4 or lower is installed and active on their WordPress site, enabling CSRF attacks against authenticated users.

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 a release after 2.2.4
Interim mitigation

Update the Wpmet Wp Ultimate Review plugin to a version higher than 2.2.4 which contains the CSRF fix.

Recommended fix Moderate confidence

Version 2.2.5 or latest available version (check wpmet.com or WordPress plugin repository for current release)

  1. 1. Visit the official WordPress plugin repository or the vendor's website (wpmet.com) to check for the latest version of Wp Ultimate Review plugin.
  2. 2. Verify if version 2.2.5 or higher is available, as this version should contain the CSRF fix.
  3. 3. Before updating, backup your WordPress site database and files.
  4. 4. Update the Wp Ultimate Review plugin to the latest available version through the WordPress admin dashboard under Plugins > Installed Plugins, or via FTP if needed.
  5. 5. After updating, verify that the plugin functionality remains intact and test critical review submission forms.
Caveat Minor plugin update; review plugin settings after upgrade to ensure custom configurations are preserved

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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