dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-3478

HIGH · 7.2 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Content Syndication Toolkit WordPress plugin (versions up to 1.3) contains an unauthenticated SSRF vulnerability in its bundled ReduxFramework library. The redux_p AJAX action endpoint (wp_ajax_nopriv_redux_p) accepts a URL parameter directly from $_GET without validation and passes it to wp_remote_request(), allowing attackers to make arbitrary HTTP requests from the server and exfiltrate internal data.

MitigationUpdate to a patched version of the Content Syndication Toolkit plugin that addresses the SSRF in the ReduxFramework library, or disable the plugin until a fix is available. The fix requires implementing URL allowlist validation and replacing wp_remote_request() with wp_safe_remote_request().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Content Syndication Toolkit plugin is installed
    Navigate to WP Admin > Plugins and locate 'Content Syndication Toolkit' in the list, or check the /wp-content/plugins/ directory for the plugin folder
    Affected if The plugin folder 'content-syndicator-toolkit' or similar exists in /wp-content/plugins/
  2. Check installed plugin version
    In WP Admin > Plugins, click on the plugin to view details and note the version number, or inspect the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version is 1.3 or lower (including any version prior to 1.3)
  3. Confirm ReduxFramework is bundled and active
    Check /wp-content/plugins/<plugin-folder>/redux-framework/ or /wp-content/plugins/redux-framework/ directory exists, and inspect if the plugin loads Redux classes
    Affected if The ReduxFramework library is bundled within the Content Syndication Toolkit plugin folder
  4. Verify the vulnerable AJAX endpoint is accessible
    Send a request to wp-admin/admin-ajax.php?action=redux_p&url=http://example.com (no authentication required due to nopriv)
    Affected if The server responds to the AJAX request and appears to process the URL parameter without requiring authentication

If the Content Syndication Toolkit plugin (version 1.3 or below) is installed with its bundled ReduxFramework and the redux_p AJAX endpoint responds without auth, the environment is affected by this SSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the Content Syndication Toolkit plugin that addresses the SSRF in the ReduxFramework library, or disable the plugin until a fix is available. The fix requires implementing URL allowlist validation and replacing wp_remote_request() with wp_safe_remote_request().

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3478 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3478 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data