CVE-2023-27608 is a missing authorization flaw in the Points and Rewards for WooCommerce plugin from WP Swings. NVD scores it 6.5, Medium. Versions up to 1.5.0 are affected, and Patchstack lists 1.6.0 as the fix. Patchstack says no login is needed to reach it.
What's affected
- Points and Rewards for WooCommerce 1.5.0 and earlier: affected.
- Version 1.6.0: the fixed release listed by Patchstack.
Patchstack reports the required privilege as unauthenticated, rates the priority Medium and gives a score of 6.5, the same as NVD. I found no conflict on severity.
How to check if you're exposed
With WP-CLI:
wp plugin list --name=points-and-rewards-for-woocommerce --fields=name,status,version,update
Or read the version on the Plugins page. Anything at 1.5.0 or lower needs the update. On a store with a loyalty scheme, also compare recent point balances against orders to see whether anything looks wrong.
What to do now
- Update the plugin to 1.6.0 or later.
- Review points balances and redemption logs for unusual activity since the plugin was installed.
- If you cannot update at once, ask your host or developer for help. Patchstack customers can enable its mitigation rule.
- Take a backup before updating a live store.
- Check the Gold page for this CVE for later changes.
Why it matters
The weakness class is CWE-862 (Missing Authorization). A request handler performs an action without checking whether the caller is allowed to. For an unauthenticated flaw, that means anyone who can send the request.
The record does not say which action is exposed, and the Patchstack title says broken access control. What it means in practice depends on the plugin function involved, so do not assume more than the sources say. For a store, loyalty points behave like money, and gaps in who may change them are worth closing quickly.
For a store owner the next question is what to check after patching. Look at the plugin's logs, if it keeps any, and at point balances for accounts that earned an unusual number of points in a short time. If the plugin keeps a transaction history, compare it with order records.
Patchstack lists a mitigation rule for its own users that blocks attacks until the update is installed. That helps while you schedule the change, but it does not replace the update, since the vulnerable code remains in the plugin.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Does an attacker need an account?
No. Patchstack lists the required privilege as unauthenticated.
Sources
Last reviewed: 19 October 2026.