# CVE-2016-20063: Single Personal Message 1.0.3 WordPress Plugin SQL Injection

> Authenticated attackers can inject SQL via the message parameter to extract sensitive database information from the Single Personal Message WordPress plugin.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-w9r3-v9m2-5vxp

## What is CVE-2016-20063?

CVE-2016-20063 is a high-severity SQL injection vulnerability in Md. Shamim Shahnewaz Single Personal Message, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Single Personal Message 1.0.3 contains an SQL injection vulnerability that allows authenticated users to execute arbitrary SQL queries by injecting malicious code through the message parameter. Attackers can access the admin interface and supply crafted SQL statements in the message parameter to extract sensitive database information including user credentials and site configuration data.

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

## Which versions are affected by CVE-2016-20063?


## How do I fix CVE-2016-20063?

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

## Is CVE-2016-20063 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20063 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20063 and fix it if it is affected.

What it is: CVE-2016-20063 is a high-severity SQL injection vulnerability in Md. Shamim Shahnewaz Single Personal Message, published on 9 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20063 exists.

Affected product: Md. Shamim Shahnewaz Single Personal Message. 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-2016-20063/ (Markdown: https://insights.sbomify.com/CVE-2016-20063/index.md)
```

## Sources

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

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