# CVE-2026-16600: SmartAIPress <= 1.2.0 - Subscriber+ Server-Side Request Forgery via smartaipress_openai_upload_and_set_featured_image

> Subscribers can exploit missing capability checks and URL validation in SmartAIPress to perform Server-Side Request Forgery and read internal or external data.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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:** 29 Aug 2026
- **Updated:** 30 Aug 2026
- **Also known as:** GHSA-6m7h-pqmp-qmm7

## What is CVE-2026-16600?

CVE-2026-16600 is a high-severity server-side request forgery vulnerability in Unknown SmartAIPress, published on 29 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SmartAIPress WordPress plugin through 1.2.0 does not perform a capability check on one of its AJAX actions and does not validate a user-supplied URL before fetching it server-side, allowing users with subscriber-level access and above to make the site retrieve arbitrary internal or external URLs and read the response, resulting in a full-read Server-Side Request Forgery.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-16600 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16600 is a high-severity server-side request forgery vulnerability in Unknown SmartAIPress, published on 29 Aug 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-16600 in the wild and no public exploit code.

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

## Sources

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

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