# CVE-2026-12689: ProfileGrid < 5.9.9.7 - Subscriber+ Cross-User Private Message Thread Deletion and Tampering via Missing Authorization

> Authenticated subscribers can delete or tamper with other users' private message threads due to missing authorization checks in ProfileGrid.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A: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:** 24 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-gv3q-r4q9-h53h

## What is CVE-2026-12689?

CVE-2026-12689 is a medium-severity missing authorization vulnerability in Unknown ProfileGrid, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ProfileGrid  WordPress plugin before 5.9.9.7 does not perform any authorization or ownership check on some of its private-message thread actions, allowing authenticated users with Subscriber-level access and above to soft-delete, tamper with the metadata of, and mark as read other users' private message threads.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12689 is a medium-severity missing authorization vulnerability in Unknown ProfileGrid, published on 24 Jul 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-2026-12689 exists.

Affected product: Unknown ProfileGrid. 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-12689/ (Markdown: https://insights.sbomify.com/CVE-2026-12689/index.md)
```

## Sources

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

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