# CVE-2026-11875: WP Support Plus Responsive Ticket System <= 9.1.2 - Unauthenticated Support Ticket Access via Session Cookie Forgery

> Unauthenticated attackers can forge guest-session cookies to impersonate users and access, reply to, or close support tickets.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-rwf6-mm98-7hfq

## What is CVE-2026-11875?

CVE-2026-11875 is a medium-severity authentication bypass vulnerability in Unknown WP Support Plus Responsive Ticket System, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Support Plus Responsive Ticket System WordPress plugin through 9.1.2 does not sign or verify its guest-session cookie, allowing unauthenticated attackers to forge it and impersonate any ticket owner (identified by email address) to read, reply to, and close that person's support tickets.

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


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

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

## Is CVE-2026-11875 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11875 is a medium-severity authentication bypass vulnerability in Unknown WP Support Plus Responsive Ticket System, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11875 exists.

Affected product: Unknown WP Support Plus Responsive Ticket System. 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-11875/ (Markdown: https://insights.sbomify.com/CVE-2026-11875/index.md)
```

## Sources

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

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