# CVE-2026-15001: Privilege escalation in bLoyal: Loyalty & Promotions by bLoyal

> Authenticated subscribers can escalate privileges to Administrator by manipulating plugin API settings to trigger auto-login with attacker-controlled data.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-5h38-4j4g-wf4g

## What is CVE-2026-15001?

CVE-2026-15001 is a high-severity vulnerability in connectordev bLoyal: Loyalty & Promotions by bLoyal, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-15001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15001 is a high-severity vulnerability in connectordev bLoyal: Loyalty & Promotions by bLoyal, published on 15 Aug 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-15001 in the wild and no public exploit code.

Affected product: connectordev bLoyal: Loyalty & Promotions by bLoyal. 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-15001/ (Markdown: https://insights.sbomify.com/CVE-2026-15001/index.md)
```

## Sources

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

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