# CVE-2026-119745: Sender WordPress Plugin < 2.11.3 Broken Access Control via admin_post_sender_debug_download


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-78vr-8fpj-r56x

## What is CVE-2026-119745?

CVE-2026-119745 is a medium-severity vulnerability in Sender – Newsletter, SMS and Email Marketing Automation for WooCommerce, published on 4 Nov 2026. 

### Official description

Sender plugin for WordPress before 2.11.3 contains a missing authorization vulnerability that allows any authenticated user, including Subscribers, to access a sensitive diagnostic dump by requesting the admin_post_sender_debug_download action handled by downloadDebugFile() without any capability, nonce, or referer check. Attackers can exploit this flaw via wp-admin/admin-post.php?action=sender_debug_download to retrieve WordPress, PHP, WooCommerce, and server version details, the full active plugin inventory, active theme information, and plugin settings including the connected Sender account resource key and account metadata.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-119745 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119745 is a medium-severity vulnerability in Sender – Newsletter, SMS and Email Marketing Automation for WooCommerce, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119745 in the wild and no public exploit code.

Affected product: Sender – Newsletter, SMS and Email Marketing Automation 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-119745/ (Markdown: https://insights.sbomify.com/CVE-2026-119745/index.md)
```

## Sources

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

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