Plugins · content-syndication-toolkit · data as of 2026-11-04
Is Content Syndication Toolkit safe? Known vulnerabilities and latest version
- Status
- Closed 2026-03-06
- Known issues on record
- 1
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate content-syndication-toolkit && wp plugin delete content-syndication-toolkit
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 1 record(s) do not state which versions are affected.
high 7.2 CVE-2026-3478 · published 2026-03-21
Server-side request forgery (SSRF) in Content Syndication Toolkit (1.3 and older)
- Affected
- 1.3 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
Recent activity
- 2026-03-06 — closed on wordpress.org (Security Issue).
- 2026-03-21 — Server-side request forgery (SSRF) disclosed (CVE-2026-3478), fix version not stated.
Get an email when Content Syndication Toolkit has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Content Syndication Toolkit (content-syndication-toolkit) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Server-side request forgery (SSRF) (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/content-syndication-toolkit (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/content-syndication-toolkit"><img src="https://laskyr.com/plugins/content-syndication-toolkit/badge.svg" alt="Content Syndication Toolkit vulnerability status"></a>