CVE-2025-6187: bSecure (WordPress plugin) · Missing Authorization
Affects bSecure (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bsecuretech bSecure – Your Universal Checkout | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2025-6187, organizations should immediately update the bSecure plugin to a patched version once released by the vendor. Until a patch is available, administrators should consider disabling the vulnerable REST endpoint /webhook/v2/order_info/ via custom code or firewall rules to block unauthenticated access. Implementing Web Application Firewall (WAF) rules to restrict access to the REST API endpoints only to trusted IP addresses or authenticated users can reduce exposure. Monitoring web server and WordPress logs for suspicious access patterns targeting the order_info endpoint is recommended. Enforce strong email verification and multi-factor authentication (MFA) on user accounts to limit the impact of stolen login cookies. Regularly audit user accounts and session tokens for anomalies. Additionally, organizations should review and tighten REST API permissions in WordPress, ensuring that permission callbacks properly validate user authorization. Conducting penetration testing and vulnerability scanning focused on REST API endpoints can help identify similar authorization issues proactively.
Description
The bSecure plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization within its order_info REST endpoint in versions 1.3.7 through 1.7.9. The plugin registers the /webhook/v2/order_info/ route with a permission_callback that always returns true, effectively bypassing all authentication. This makes it possible for unauthenticated attackers who know any user’s email to obtain a valid login cookie and fully impersonate that account.
References
- wordfence.com/threat-intel/vulnerabilities/id/f8f51029-0748-4943-b0ef-fc822b14614a?source=cve (opens in a new tab)
- wordpress.org/plugins/bsecure/ (opens in a new tab)
- plugins.trac.wordpress.org/browser/bsecure/tags/1.7.9/includes/class-bsecure-checkout.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/bsecure/tags/1.7.9/includes/class-wc-bsecure.php (opens in a new tab)