CVE-2026-15293
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WP Business Intelligence Lite WordPress plugin versions up to 3.2.0 lack proper authorization checks, allowing authenticated users with Subscriber-level permissions to modify stored SQL queries. When an administrator views these modified queries, arbitrary SQL executes, enabling privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WP Business Intelligence Lite plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Business Intelligence Lite' or check the /wp-content/plugins/ directory for the plugin folderAffected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin Plugins list, find WP Business Intelligence Lite and note the version number displayed, or read the main plugin PHP file header for 'Version:' tagAffected if Version is 3.2.0 or lower (or version field is empty/unreadable and the plugin appears to be the Lite version)
-
Confirm the SQL query storage feature existsLook for plugin functionality related to saved queries, data sources, or custom SQL within the plugin settings menu (typically under WP Business Intelligence menu items)Affected if The plugin has stored SQL query or data source functionality that can be accessed
-
Check for existing stored SQL queries in the databaseQuery the WordPress database tables for records related to the plugin (search tables with 'wp_biwi' or 'wp_business_intelligence' prefix for query-related entries)Affected if Any stored queries exist in the database associated with the plugin
-
Audit WordPress user roles with Subscriber-level accessIn WordPress admin, go to Users and review which users have the Subscriber role, or query wp_usermeta for users with wp_capabilities containing 'subscriber'Affected if Any Subscriber-level user accounts exist in the WordPress installation
A user is affected if WP Business Intelligence Lite plugin version 3.2.0 or lower is installed AND the plugin has stored SQL query functionality that could be accessed by Subscriber-level users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate WP Business Intelligence Lite to a version beyond 3.2.0 when available, or disable the plugin and remove it until a patched version can be installed.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15293 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data