dbcve.org
Wp Customer ReviewsWordPress extension · Gowebsolutions

CVE-2016-10902

HIGH · 8.8 CVSS v3.0 Published 2019-08-21
Fix available
A fix is available. Upgrade to 3.0.9 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
The wp-customer-reviews plugin before 3.0.9 for WordPress has CSRF in the admin tools.

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

The wp-customer-reviews plugin before version 3.0.9 for WordPress contains a Cross-Site Request Forgery (CSRF) vulnerability in its admin tools section. This allows attackers to trick authenticated administrators into performing unintended actions by forging malicious requests.

MitigationUpdate the wp-customer-reviews plugin to version 3.0.9 or later to remediate the CSRF vulnerability in the admin tools.

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 Customer ReviewsWordPress extension
Affected:< 3.0.9

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.0/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. Verify WordPress installation exists
    Check for wp-content/plugins directory or access WordPress admin dashboard at /wp-admin/
    Affected if WordPress is installed and the wp-customer-reviews plugin may be present
  2. Check if wp-customer-reviews plugin is installed
    Look for the plugin directory at wp-content/plugins/wp-customer-reviews/ or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin directory or listing exists in the WordPress installation
  3. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find 'Wp Customer Reviews' to view the version number, or read the main plugin file header at wp-content/plugins/wp-customer-reviews/wp-customer-reviews.php
    Affected if Installed version is less than 3.0.9 (e.g., 3.0.8, 3.0.7, etc.)
  4. Confirm admin access to plugin tools
    Log in as an administrator and navigate to the plugin settings page (usually under Reviews > Customer Reviews or a dedicated admin tools section)
    Affected if Administrator user can access the admin tools section of the plugin

User is affected if the wp-customer-reviews plugin version is below 3.0.9 and an administrator has access to the plugin admin tools section.

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
Upgrade available Upgrade to 3.0.9 or later
Fixed in 3.0.9
Interim mitigation

Update the wp-customer-reviews plugin to version 3.0.9 or later to remediate the CSRF vulnerability in the admin tools.

Fix this in Wp Customer Reviews Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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