# CVE-2026-3478: Content Syndication Toolkit <= 1.3 - Unauthenticated Server-Side Request Forgery via 'url' Parameter

> Unauthenticated attackers can exploit an SSRF vulnerability in the Content Syndication Toolkit plugin to access internal services and cloud metadata.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-97j6-f74w-c455

## What is CVE-2026-3478?

CVE-2026-3478 is a high-severity server-side request forgery vulnerability in benmoody Content Syndication Toolkit, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Content Syndication Toolkit plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.3 via the redux_p AJAX action in the bundled ReduxFramework library. The plugin registers a proxy endpoint (wp_ajax_nopriv_redux_p) that is accessible to unauthenticated users. The proxy() method in the Redux_P class takes a URL directly from $_GET['url'] without any validation (the regex is set to /.*/ which matches all URLs) and passes it to wp_remote_request(), which does not have built-in SSRF protection like wp_safe_remote_request(). There is no authentication check, no nonce verification, and no URL restriction. The response from the requested URL is then returned to the attacker, making this a full-read SSRF. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application, which can be used to query and modify information from internal services, scan internal network ports, or interact with cloud metadata endpoints.

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

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


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

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

## Is CVE-2026-3478 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3478 is a high-severity server-side request forgery vulnerability in benmoody Content Syndication Toolkit, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3478 in the wild and no public exploit code.

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

## Sources

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

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