# CVE-2025-3063: Shopper Approved Reviews 2.0 - 2.1 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Options Update

> Authenticated subscribers can update arbitrary options to escalate privileges to administrator due to missing capability checks.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2025
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-6cgj-2ccj-288g

## What is CVE-2025-3063?

CVE-2025-3063 is a high-severity missing authorization vulnerability in shopperapprovedapp Shopper Approved Reviews, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-3063?


## How do I fix CVE-2025-3063?

Upgrade to a fixed version.

## Is CVE-2025-3063 being exploited?

There is no known exploitation of CVE-2025-3063 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3063 and fix it if it is affected.

What it is: CVE-2025-3063 is a high-severity missing authorization vulnerability in shopperapprovedapp Shopper Approved Reviews, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3063 in the wild and no public exploit code.

Affected product: shopperapprovedapp Shopper Approved Reviews. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3063/ (Markdown: https://insights.sbomify.com/CVE-2025-3063/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3063
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3063
- OSV: https://osv.dev/vulnerability/CVE-2025-3063

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3063/
Summaries are generated and may contain mistakes; the official description above is the record.