# CVE-2026-17522: Newsletters < 4.17 - Arbitrary Plugin Option Update via CSRF

> Attackers can trick administrators into updating arbitrary plugin settings, including API credentials, via Cross-Site Request Forgery.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Aug 2026
- **Updated:** 30 Aug 2026
- **Also known as:** GHSA-mx7c-44xm-6gm6

## What is CVE-2026-17522?

CVE-2026-17522 is a medium-severity vulnerability in Unknown Newsletters, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Newsletters WordPress plugin before 4.17 does not perform any nonce or capability check when saving one of its settings screens, and writes every submitted parameter into its own options, allowing attackers to make a logged in administrator overwrite arbitrary Newsletters WordPress plugin before 4.17 settings, including the credential protecting its API, via a Cross-Site Request Forgery attack.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-17522 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17522 is a medium-severity vulnerability in Unknown Newsletters, published on 29 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-17522 in the wild and no public exploit code.

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

## Sources

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

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