# CVE-2026-65547: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

> A subscriber can exploit SQL injection in the Creative Mail plugin to read or modify database contents.

- **Severity:** Not scored
- **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:** 6 Aug 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-3jfp-8ffg-83g9

## What is CVE-2026-65547?

CVE-2026-65547 is a SQL injection vulnerability, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Duplicate to CVE-2026-3985.

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


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

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

## Is CVE-2026-65547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65547 is a SQL injection vulnerability, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65547 in the wild and no public exploit code.

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-65547/ (Markdown: https://insights.sbomify.com/CVE-2026-65547/index.md)
```

## Sources

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

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