# CVE-2026-15293: Missing authorization in WP Business Intelligence Lite

> Authenticated subscribers can modify SQL queries to escalate privileges via arbitrary SQL execution when viewed by administrators.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-85wm-6f94-p7hm

## What is CVE-2026-15293?

CVE-2026-15293 is a high-severity missing authorization vulnerability in joeyoungblood WP Business Intelligence Lite, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The WP Business Intelligence Lite plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.2.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify stored SQL queries, which can lead to privilege escalation via arbitrary SQL execution when the modified query is viewed by an administrator.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-15293 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15293 is a high-severity missing authorization vulnerability in joeyoungblood WP Business Intelligence Lite, published on 10 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-15293 in the wild and no public exploit code.

Affected product: joeyoungblood WP Business Intelligence Lite. 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-15293/ (Markdown: https://insights.sbomify.com/CVE-2026-15293/index.md)
```

## Sources

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

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