Security readout for executives and security teams
Plain-English summary
CVE-2026-3478 lets anyone on the internet use an affected WordPress site as a proxy to request other URLs. This can expose internal systems or cloud metadata reachable from the web server. The issue affects Content Syndication Toolkit versions up to 1.3 according to the provided description. No cited source confirms active exploitation.
Executive priority
Prioritize review of public WordPress sites using this plugin, especially in cloud or internally connected environments. If present, disable or contain it until an official fix or guidance is confirmed.
Technical view
The plugin registers an unauthenticated AJAX proxy action, wp_ajax_nopriv_redux_p. Redux_P::proxy() accepts $_GET['url'], permits all URLs, uses wp_remote_request() rather than wp_safe_remote_request(), and returns the response. This is full-read SSRF with CVSS 7.2 and CWE-918.
Likely exposure
Internet-facing WordPress sites running Content Syndication Toolkit 1.3 or earlier are the primary exposure. Risk is higher where the WordPress server can reach internal applications, management interfaces, or cloud metadata services.
Exploitation context
Attackers need no account or user interaction. The vulnerability can support internal network reconnaissance, reading reachable internal responses, or interacting with services accessible from the WordPress host. KEV is false and the supplied sources do not report exploitation in the wild.
Researcher notes
The source bundle includes code references showing the proxy class and permissive URL handling. The affected metadata appears inconsistent, listing version “0” and defaultStatus “unaffected,” while the description states all versions through 1.3. Validate against the CVE and Wordfence records before final asset scoping.
Mitigation direction
- Disable or remove Content Syndication Toolkit where not business-critical.
- Check vendor, Wordfence, and WordPress plugin sources for a fixed release or official workaround.
- Restrict unauthenticated access to the vulnerable AJAX action if the plugin must remain enabled.
- Limit WordPress server egress to required destinations only.
- Block access from WordPress servers to metadata and internal management endpoints.
Validation and detection
- Inventory WordPress sites for Content Syndication Toolkit and record installed versions.
- Treat version 1.3 or earlier as affected per the provided vulnerability description.
- Review web logs for unauthenticated admin-ajax requests invoking redux_p.
- Look for unusual outbound requests from WordPress servers to internal or metadata addresses.
- Confirm remediation status against vendor or trusted vulnerability advisories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-3478 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/f8381866-d991-4638-ab4d-3b8697acf414?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/content-syndication-toolkit/trunk/inc/ReduxFramework/ReduxCore/inc/class.p.php#L219CVE reference
- https://plugins.trac.wordpress.org/browser/content-syndication-toolkit/tags/1.3/inc/ReduxFramework/ReduxCore/inc/class.p.php#L219CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.