# CVE-2026-10628: Missing authorization in Points and Rewards for WooCommerce

> Authenticated attackers can modify reward points, exfiltrate user data, and alter site settings due to missing authorization checks in the Points and Rewards for WooCommerce plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-rv47-ph67-qh37

## What is CVE-2026-10628?

CVE-2026-10628 is a medium-severity missing authorization vulnerability in wpswings Points and Rewards for WooCommerce, published on 11 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Points and Rewards for WooCommerce plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.10.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to convert and drain any user's reward points into wallet balance, exfiltrate all users' emails and point balances to an attacker-controlled Klaviyo account, overwrite the site's Klaviyo public API key, block or unblock arbitrary users from the points system, and modify campaign banner and heading settings. The nonce used for authentication of these requests (wps-wpr-verify-nonce) is injected into every public-facing page via wp_localize_script(), and the wps_wpr_generate_custom_wallet handler is additionally registered on the wp_ajax_nopriv_ hook, meaning unauthenticated visitors can also obtain a valid nonce and exploit that specific action.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-10628?


## How do I fix CVE-2026-10628?

No fix has been published for CVE-2026-10628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10628 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10628 and fix it if it is affected.

What it is: CVE-2026-10628 is a medium-severity missing authorization vulnerability in wpswings Points and Rewards for WooCommerce, published on 11 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10628 in the wild and no public exploit code.

Affected product: wpswings Points and Rewards for WooCommerce. 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-2026-10628/ (Markdown: https://insights.sbomify.com/CVE-2026-10628/index.md)
```

## Sources

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

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