dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-25007

HIGH · 8.5 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Element Invader ElementInvader Addons for Elementor elementinvader-addons-for-elementor allows Blind SQL Injection.This issue affects ElementInvader Addons for Elementor: from n/a through <= 1.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 · moderate confidence

This is a blind SQL injection vulnerability in the ElementInvader Addons for Elementor WordPress plugin (versions up to 1.4.2). The vulnerability allows authenticated or unauthenticated attackers to inject malicious SQL queries through unsanitized user input in certain addon components, potentially enabling data exfiltration from the WordPress database.

MitigationUpdate to the latest version of ElementInvader Addons for Elementor when a patch is released. Until then, restrict access to affected endpoints or disable the plugin if possible.

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
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify ElementInvader Addons plugin is installed
    Check the WordPress plugin directory for 'elementor-element-invader' or 'elementinvader' folder, or query the wp_options table for 'active_plugins'
    Affected if The plugin appears in the list of active WordPress plugins
  2. Determine the installed plugin version
    Inspect the main plugin file (usually elementor-element-invader.php or invader-addons.php) and look for the 'Version:' header in the file comment, or check the WordPress plugins admin page
    Affected if The reported version is 1.4.2 or any version below it (the advisory covers versions up to 1.4.2)
  3. Identify exposed addon endpoints
    Review the plugin directory structure for addon folders (commonly in /addons/ or /modules/) and identify PHP files that handle $_GET, $_POST, or $_REQUEST parameters without proper sanitization, particularly those making database queries
    Affected if The plugin exposes any addon component that processes user input into SQL queries without prepared statements or sanitization
  4. Inspect HTTP traffic and access logs for SQL injection attempts
    Review web server access logs (Apache/nginx) and WordPress debug logs for unusual query patterns containing SQL keywords (UNION, SELECT, SLEEP, BENCHMARK, IF, WHERE) in URL parameters targeting addon-related paths
    Affected if Logs show SQL injection patterns targeting plugin addon URLs or parameters
  5. Check database for unauthorized changes or data access
    Query the wp_options table and other critical tables for unexpected modifications, or review MySQL general/slow query logs for suspicious long-running queries originating from the web server user
    Affected if Database shows unexpected records, modified settings, or unusual query patterns that align with blind SQL injection time-based or conditional responses

A WordPress site is affected if ElementInvader Addons for Elementor version 1.4.2 or lower is installed and the plugin exposes vulnerable addon components that accept unsanitized user input into SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of ElementInvader Addons for Elementor when a patch is released. Until then, restrict access to affected endpoints or disable the plugin if possible.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25007 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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