Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-15001 high CVSS 8.8

Privilege Escalation in bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin) (CVE-2026-15001)

Summary

Vulnerability in bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin) (CVE-2026-15001). Successful exploitation can lead to full system takeover. Exploitable via save_bloyal_configuration_data.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-15001 has been found in bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin).
Attackers can target a specific entry point like save_bloyal_configuration_data over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin) CVE-2026-15001" on the vendor's site.

CVE-2026-15001 (bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin)) — CWE-269 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: save_bloyal_configuration_data / save_bloyal_accesskeyverification_data / bloyal_customer_auto_login / Customer.ExternalId
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-269) exists in bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin). Attackers reach the vulnerable code path via save_bloyal_configuration_data.

📍 Affected scope

Check the vendor advisory for the affected versions of bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin). Attack surface: save_bloyal_configuration_data / save_bloyal_accesskeyverification_data / bloyal_customer_auto_login / Customer.ExternalId.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで bLoyal: Loyalty & Promotions by bLoyal (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details