The Points and Rewards for WooCommerce WordPress plugin before 2.10.4 does not validate the claimed reward amount or restrict who can call its Win Wheel claim handler, allowing authenticated users, Subscriber and above, to credit their own account with an arbitrary and unlimited amount of loyalty points and, where a companion wallet Points and Rewards for WooCommerce WordPress plugin before 2.10.4 is active, wallet balance.
CVE-2026-93510
Score 4.3 from GitHub Security Advisory published 2026-09-23. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (1)
Auto-updated Sep 23, 2026Points and Rewards for WooCommerce < 2.10.4 – Subscriber+ Arbitrary Points and Wallet Balance Manipulation via assign_claim_points | CVE 2026-93510 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/b721d8bb-2426-4635-a419-07074168bd82/Vendor Advisories for CVE-2026-93510(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 18:54 UTCEG score recompute
- 2026-09-24 18:54 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 18:18 UTCEG score recompute
- 2026-09-23 18:18 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 11:23 UTCGHSA enrichment
- 2026-09-23 11:01 UTCEG score recompute▲ 4.30
- 2026-09-23 11:01 UTCGHSA enrichment
- 2026-09-23 11:01 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
- 2026-09-23 06:17 UTCNVD update
- 2026-09-23 06:06 UTCEG score recompute
- 2026-09-23 06:06 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-93510?
When was CVE-2026-93510 disclosed?
Is CVE-2026-93510 actively exploited?
What is the CVSS score of CVE-2026-93510?
How do I remediate CVE-2026-93510?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93510
Is Your Infrastructure Affected by CVE-2026-93510?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.