dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-3063

HIGH · 8.8 CVSS v3.1 Published 2025-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 Shopper Approved Reviews plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the ajax_callback_update_sa_option() function in versions 2.0 to 2.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 Shopper Approved Reviews WordPress plugin versions 2.0-2.1 lacks a capability check on the ajax_callback_update_sa_option() function, allowing any authenticated user with Subscriber-level access to update arbitrary WordPress site options via AJAX. This broken access control can be exploited to escalate privileges by changing the default registration role to Administrator and enabling user registration, giving attackers admin access.

MitigationUpdate to the latest version of the plugin which should include proper capability checks, or remove the plugin if no patched version is available.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Confirm plugin installation and version
    Navigate to WordPress admin > Plugins and locate 'Shopper Approved Reviews'. Check the version number displayed under the plugin name. Alternatively, inspect the plugin header in /wp-content/plugins/shopper-approved-reviews/ folder for the Version tag.
    Affected if The plugin is installed and the version is 2.0 through 2.1 (inclusive).
  2. Identify subscriber-level or higher user accounts
    Go to Users > All Users in WordPress admin. Review the list for any accounts with Subscriber, Contributor, Author, Editor, or Administrator roles that you did not create. Check user registration settings under Settings > General to see if registration is enabled.
    Affected if Any authenticated user with Subscriber-level access or higher exists AND user registration is enabled in WordPress settings.
  3. Verify default user registration role
    In WordPress admin, go to Settings > General and locate 'Default Role' dropdown. Check if it is set to Administrator or any elevated role.
    Affected if The default new user registration role is set to Administrator.
  4. Audit administrator accounts for unauthorized access
    Review all user accounts with Administrator role. Check the user email addresses, account creation dates, and last login times. Compare against known legitimate administrators.
    Affected if There are administrator accounts that were not created by known site administrators, or administrator accounts with suspicious creation dates.

You are affected if the Shopper Approved Reviews plugin versions 2.0-2.1 are installed, any non-admin user account exists on the site, and user registration is enabled or unauthorized administrator accounts are present.

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 to the latest version of the plugin which should include proper capability checks, or remove the plugin if no patched version is available.

Recommended fix Moderate confidence

Version 2.1.1 or latest available version

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Shopper Approved Reviews' plugin
  4. Check if an update is available and upgrade to the latest version (2.1.1 or higher)
  5. If no automatic update is available, manually download the latest version from wordpress.org and reinstall

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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