# CVE-2025-6187: bSecure 1.3.7 - 1.7.9 - Missing Authorization to Unauthenticated Privilege Escalation via order_info REST Endpoint

> Unauthenticated attackers can escalate privileges and impersonate users via the order_info REST endpoint due to missing authorization checks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-qw32-m39m-p626

## What is CVE-2025-6187?

CVE-2025-6187 is a critical missing authorization vulnerability in bsecuretech bSecure – Your Universal Checkout, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-6187?


## How do I fix CVE-2025-6187?

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

## Is CVE-2025-6187 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6187 and fix it if it is affected.

What it is: CVE-2025-6187 is a critical missing authorization vulnerability in bsecuretech bSecure – Your Universal Checkout, published on 22 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-6187 in the wild and no public exploit code.

Affected product: bsecuretech bSecure – Your Universal Checkout. 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-2025-6187/ (Markdown: https://insights.sbomify.com/CVE-2025-6187/index.md)
```

## Sources

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

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