# CVE-2026-39521: WordPress Nelio Content plugin <= 4.3.1 - Server Side Request Forgery (SSRF) vulnerability

> An attacker can exploit a Server-Side Request Forgery vulnerability in the Nelio Content plugin to make arbitrary requests from the server.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/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:** 8 Apr 2026
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-7vhv-799g-fcfv

## What is CVE-2026-39521?

CVE-2026-39521 is a medium-severity server-side request forgery vulnerability in Nelio Content, published on 8 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in Nelio Software Nelio Content nelio-content allows Server Side Request Forgery.This issue affects Nelio Content: from n/a through <= 4.3.1.

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

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


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

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

## Is CVE-2026-39521 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-39521 is a medium-severity server-side request forgery vulnerability in Nelio Content, published on 8 Apr 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-39521 in the wild and no public exploit code.

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

## Sources

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

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