# CVE-2026-88930: Social Web Suite <= 4.1.12 - Unauthenticated Blind SQLi via Unset Shared Secret

> Unauthenticated attackers can perform blind SQL injection attacks on Social Web Suite WordPress plugin due to missing shared secret validation and improper input sanitization.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-8r7c-grp8-rwmq

## What is CVE-2026-88930?

CVE-2026-88930 is a high-severity SQL injection vulnerability in Unknown Social Web Suite, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Social Web Suite  WordPress plugin through 4.1.12 does not require its shared secret to be set before accepting requests authorised by it, and does not sanitise and escape a parameter before using it in an SQL statement, allowing unauthenticated users to perform SQL injection attacks.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


## How do I fix CVE-2026-88930?

No fix has been published for CVE-2026-88930 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-88930 being exploited?

There is no known exploitation of CVE-2026-88930 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88930 and fix it if it is affected.

What it is: CVE-2026-88930 is a high-severity SQL injection vulnerability in Unknown Social Web Suite, published on 11 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88930 in the wild and no public exploit code.

Affected product: Unknown Social Web Suite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88930/ (Markdown: https://insights.sbomify.com/CVE-2026-88930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88930
- OSV: https://osv.dev/vulnerability/CVE-2026-88930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88930/
Summaries are generated and may contain mistakes; the official description above is the record.