Skip to main content
Menu
CVEs

InstaWP Connect SQL injection leads to data theft in WordPress plugin

Affects the InstaWP Connect WordPress plugin version 0.1.4.4 and earlier. Fixed in 0.1.4.5.

CVE-2026-128915Published November 20, 2026, updated

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.1.4.5
Who is exposed
Specific setups only

Summary

The InstaWP Connect plugin for WordPress has a blind SQL injection flaw that lets an attacker with a low-privilege account run database queries and extract sensitive data. The flaw can be reached remotely over the network, and no user action is needed.

Written by a model

Original description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InstaWP InstaWP Connect instawp-connect allows Blind SQL Injection.This issue affects InstaWP Connect: from n/a through 0.1.4.4.

Who should check

Sites running the WordPress InstaWP Connect plugin (instawp-connect) version 0.1.4.4 or earlier, where Contributor-level accounts exist.

“WordPress InstaWP Connect Plugin <= 0.1.4.4 is vulnerable to SQL Injection”

patchstack.com

What to do

  1. Check whether your setup matches what the bug needs.

    InstaWP Connect plugin version 0.1.4.4 or earlier
  2. Upgrade to a fixed version: 0.1.4.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128915 (WordPress InstaWP Connect plugin <= 0.1.4.4 - SQL Injection vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128915 (entry last updated 2026-11-20):
Affected:
- InstaWP InstaWP Connect: fixed in 0.1.4.5
Fixed versions: 0.1.4.5.
Conditions (all must be true for the bug to be hit):
- InstaWP Connect plugin version 0.1.4.4 or earlier (source: https://patchstack.com/database/wordpress/plugin/instawp-connect/vulnerability/wordpress-instawp-connect-plugin-0-1-4-4-sql-injection-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-128915 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128915 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/instawp-connect/vulnerability/wordpress-instawp-connect-plugin-0-1-4-4-sql-injection-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-128915
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128915
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128915"}.

Affected versions

cve.now Index

17Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

Questions about CVE-2026-128915

Is CVE-2026-128915 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

This SQL injection flaw in the InstaWP Connect WordPress plugin can let an attacker read, modify, or delete the entire database, including user accounts and private data.

Source: patchstack.com, cve.org

Which versions are affected by CVE-2026-128915?

instawp-connect: through 0.1.4.4 (fixed in 0.1.4.5).

Source: cve.now feed data

Am I affected, and how do I check?

The vulnerable versions are InstaWP Connect plugin 0.1.4.4 and earlier. The installed version appears on the Plugins screen of the WordPress admin dashboard.

Source: patchstack.com, cve.org

How do I fix CVE-2026-128915?

Update the InstaWP Connect plugin to at least version 0.1.4.5, which is the fixed version named in the advisory.

Source: patchstack.com, cve.org

No corrections so far. Something wrong on this page? Report an error.