# CVE-2026-11399: Missing authorization in Helpdesk Support Ticket System for WooCommerce

> Authenticated subscribers can delete arbitrary ticket responses belonging to other users due to missing authorization checks on the ID parameter.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-vv97-3hr9-5prm

## What is CVE-2026-11399?

CVE-2026-11399 is a medium-severity missing authorization vulnerability in wpcodefactory Helpdesk Support Ticket System for WooCommerce, published on 3 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Helpdesk Support Ticket System for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.1.6 via the 'id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary ticket responses belonging to other users by supplying any stsw_responses row ID to the deletion handler after obtaining the nonce from the admin footer.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-11399 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11399 is a medium-severity missing authorization vulnerability in wpcodefactory Helpdesk Support Ticket System for WooCommerce, published on 3 Oct 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-11399 in the wild and no public exploit code.

Affected product: wpcodefactory Helpdesk Support Ticket System for WooCommerce. 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-11399/ (Markdown: https://insights.sbomify.com/CVE-2026-11399/index.md)
```

## Sources

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

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