The bLoyal: Loyalty & Promotions by bLoyal plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.1.611.78. This is due to the AJAX actions save_bloyal_configuration_data and save_bloyal_accesskeyverification_data being registered without any capability or nonce checks, and the bloyal_customer_auto_login function unconditionally trusting the Customer.ExternalId value returned by whichever API URL is stored in the plugin's options. This makes it possible for authenticated attackers, with Subscriber-level access and above, to overwrite the plugin's bLoyal Loyalty Engine API URL (bloyal_custom_loyaltyengine_api_url) and the is_bloyal_custom_api_url flag via the unprotected AJAX actions, then trigger the unauthenticated /cart REST route to cause bloyal_customer_auto_login to fetch customer data from an attacker-controlled endpoint and call wp_set_auth_cookie() with an attacker-supplied Customer.ExternalId, thereby authenticating as any WordPress user including the site Administrator.
CVE-2026-15001
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
August 15, 2026
Last Modified
August 20, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L2429
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L2470
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L2512
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L421
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L494
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L806
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/bloyal.php#L1196
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/bloyal.php#L1553
- security@wordfencehttps://plugins.trac.wordpress.org/browser/bloyal/tags/3.1.611.78/bloyal.php#L1596
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/ba4b58ad-97b3-482a-bf24-1fa85d6ef93d?source=cve
Vendor Advisories for CVE-2026-15001(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 29× in last 7d / 29× 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-08-21 00:39 UTCEG score recompute
- 2026-08-21 00:39 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 13:03 UTCGHSA enrichment
- 2026-08-20 02:30 UTCEG score recompute
- 2026-08-20 02:30 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 14:53 UTCGHSA enrichment
- 2026-08-19 03:16 UTCGHSA enrichment
- 2026-08-18 15:38 UTCEG score recompute
- 2026-08-18 15:38 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 04:02 UTCGHSA enrichment
- 2026-08-17 16:25 UTCEG score recompute
- 2026-08-17 16:25 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 13:20 UTCGHSA enrichment
- 2026-08-17 01:44 UTCEG score recompute
- 2026-08-17 01:44 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:07 UTCGHSA enrichment
- 2026-08-16 02:31 UTCEG score recompute
- 2026-08-16 02:31 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 14:55 UTCEG score recompute
Show 4 moreShow fewer
- 2026-08-15 14:55 UTCGHSA enrichment
- 2026-08-15 03:18 UTCEG score recompute
- 2026-08-15 02:41 UTCEG score recompute
- 2026-08-15 02:40 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2026-15001?
When was CVE-2026-15001 disclosed?
Is CVE-2026-15001 actively exploited?
What is the CVSS score of CVE-2026-15001?
How do I remediate CVE-2026-15001?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15001
Is Your Infrastructure Affected by CVE-2026-15001?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.