Security readout for executives and security teams
Plain-English summary
This affects the WordPress RSS Aggregator by Feedzy plugin through version 3.4.2. If an administrator is tricked into clicking a malicious link or visiting a hostile page while logged in, an attacker may change Feedzy-related post metadata. The documented impact is limited integrity change, not data theft or service outage.
Executive priority
Treat as a routine but real WordPress maintenance issue. Prioritize affected public sites with active administrators, but do not escalate as emergency ransomware-level risk based on the provided evidence.
Technical view
The issue is CWE-352 CSRF caused by missing or incorrect nonce validation in save_feedzy_post_type_meta(). The CVSS 3.1 score is 4.3 with network attack vector, no attacker privileges, required user interaction, and low integrity impact. Sources indicate a code change in the Feedzy plugin; active exploitation is not supported by KEV.
Likely exposure
Exposure is likely limited to WordPress sites running RSS Aggregator by Feedzy at version 3.4.2 or earlier, especially where administrators remain logged in while browsing external content.
Exploitation context
The attacker must convince a logged-in site administrator to perform an action such as clicking a crafted link. The source bundle does not show KEV listing or confirmed active exploitation.
Researcher notes
The evidence supports CSRF with low integrity impact against Feedzy post metadata. The bundle does not establish exploit-in-the-wild activity, broad compromise, or a specific business-data exposure path beyond unauthorized metadata updates.
Mitigation direction
- Inventory WordPress sites for the Feedzy plugin and installed version.
- Update Feedzy to a version newer than 3.4.2 where available.
- If immediate update is impossible, disable the plugin until vendor guidance is reviewed.
- Remind administrators not to browse untrusted links while logged into WordPress.
- Review Wordfence, Nintechnet, and plugin changelog guidance for site-specific direction.
Validation and detection
- Confirm whether RSS Aggregator by Feedzy is installed and active.
- Check whether the installed plugin version is 3.4.2 or earlier.
- Review relevant post metadata for unexpected changes after administrator browsing events.
- Confirm nonce validation exists around save_feedzy_post_type_meta() in the deployed code.
- Check that CVE-2020-36758 is not listed in KEV before claiming active exploitation.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2020-36758 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:R/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/e3b916dc-3b94-4319-a805-0ea99d14429f?source=cveCVE reference
- https://blog.nintechnet.com/25-wordpress-plugins-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/more-wordpress-plugins-and-themes-vulnerable-to-csrf-attacks/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-3/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-2/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-1/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-5/CVE reference
- https://blog.nintechnet.com/multiple-wordpress-plugins-fixed-csrf-vulnerabilities-part-4/CVE reference
- https://plugins.trac.wordpress.org/changeset/2369394/feedzy-rss-feeds/trunk/includes/admin/feedzy-rss-feeds-admin.phpCVE 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.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.