CVE-2026-15001 json
bLoyal: Loyalty & Promotions by bLoyal <= 3.1.611.78 - Authenticated (Subscriber+) Privilege Escalation via Unprotected AJAX API URL Settings
published 2026-08-15 2 mo ago modified 2026-08-20 2 mo ago also EUVD-2026-58841
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 mo ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- connectordev bLoyal: Loyalty & Promotions by bLoyal
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ba4b58ad-97b3-482a-bf24-1fa85d6ef93d?source=cve
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L421
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L2470
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L2429
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/bloyal.php#L1553
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/bloyal.php#L1596
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L494
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/bloyal.php#L1196
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L2512
- plugins.trac.wordpress.org /browser/bloyal/tags/3.1.611.78/app/controller/class-bloyalcontroller.php#L806
Sources
- CVE List CVE-2026-15001
- NVD CVE-2026-15001
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.