{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15001 is a high-severity vulnerability in connectordev bLoyal: Loyalty \u0026 Promotions by bLoyal, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15001 and fix it if it is affected.\n\nWhat it is: CVE-2026-15001 is a high-severity vulnerability in connectordev bLoyal: Loyalty \u0026 Promotions by bLoyal, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-15001 in the wild and no public exploit code.\n\nAffected product: connectordev bLoyal: Loyalty \u0026 Promotions by bLoyal. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-15001/ (Markdown: https://insights.sbomify.com/CVE-2026-15001/index.md)","id":"CVE-2026-15001","markdown":"https://insights.sbomify.com/CVE-2026-15001/index.md","name":"CVE-2026-15001","record":{"aliases":["GHSA-5h38-4j4g-wf4g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated subscribers can escalate privileges to Administrator by manipulating plugin API settings to trigger auto-login with attacker-controlled data.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"The bLoyal: Loyalty \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in bLoyal: Loyalty \u0026 Promotions by bLoyal","id":"CVE-2026-15001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Autopay \u003c= 5.0.0 - Unauthenticated Stored Cross-Site Scripting via 'bm_woocommerce_css_editor_content' Parameter","id":"CVE-2026-15002"},"packages":[],"prev":{"headline":"Cross-site scripting in Connect Contact Form 7 and Mailchimp","id":"CVE-2026-15000"},"products":["bLoyal: Loyalty \u0026 Promotions by bLoyal"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["connectordev"]},"summary":"Authenticated subscribers can escalate privileges to Administrator by manipulating plugin API settings to trigger auto-login with attacker-controlled data.","url":"https://insights.sbomify.com/CVE-2026-15001/"}