CVE-2026-40745
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in bdthemes Element Pack Elementor Addons bdthemes-element-pack-lite allows Blind SQL Injection.This issue affects Element Pack Elementor Addons: from n/a through <= 8.4.2.
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 confidenceSQL Injection vulnerability in bdthemes Element Pack Elementor Addons plugin allows blind SQL injection via improper neutralization of special elements in SQL commands. This affects versions through 8.4.2 and could allow attackers to extract data from the database by observing application behavior differences.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L
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.
-
Locate the Element Pack plugin installationCheck your WordPress wp-content/plugins directory for a folder named 'bdthemes-element-pack-lite' or 'element-pack'. Alternatively, run 'wp plugin list --name=element-pack' if WP-CLI is available.Affected if The plugin folder does not exist in the expected location
-
Determine the installed versionOpen the main plugin file (usually index.php or element-pack-lite.php) in the plugin folder and locate the 'Version:' header in the plugin comment block. Or run 'wp plugin list --name=element-pack --format=json' to query the version programmatically.Affected if The version read from the plugin header cannot be determined or is missing
-
Compare version to affected rangeCompare your installed version number to the affected range: any version through 8.4.2 (e.g., 8.4.2, 8.4.1, 8.4.0, 8.3.0, etc.). Version 8.4.2 is the highest version in the affected range.Affected if Your installed version is 8.4.2 or any earlier version (e.g., 8.4.1, 8.3.5, 8.0.0, etc.)
-
Verify if the plugin is activeCheck the WordPress admin under Plugins > Installed Plugins to confirm whether Element Pack is activated. Alternatively, query the database table wp_options for option_name='active_plugins' and check if the plugin path is present.Affected if The plugin is not active in your WordPress installation
You are affected if the bdthemes Element Pack plugin is installed, active, and running version 8.4.2 or any earlier version, since the SQL injection vulnerability exists in all versions through 8.4.2.
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 bdthemes-element-pack-lite to the latest version immediately. Before updating, backup the WordPress site and verify compatibility with other Elementor plugins and the active theme.
- Consultation2.0 h
- Implementation1.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 $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40745 — 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-40745 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