Skip to main content
CVE-2026-120035VulnerabilityPublished

The RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator plugin for WordPress

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-120035· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 6 Nov 2026, 13:23 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
themeisleRSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds AggregatorAffected
  • <=5.2.13
Fixed in–

AI-suggested

Since the vulnerability requires administrator configuration of a malicious feed URL, administrators should avoid importing feeds from untrusted sources. Monitor vendor advisories for official patches or updates addressing this issue. Until a fix is available, restrict administrative permissions and carefully validate feed sources to mitigate risk.

Description

The RSS Aggregator by Feedzy WordPress plugin is vulnerable to stored cross-site scripting (XSS) via the 'item_title' parameter parsed from feed item titles. This affects all versions up to and including 5.2.13. An attacker can inject malicious scripts into pages viewed by users if an administrator has configured a Feed-to-Post import with a malicious feed URL. The vulnerability arises from insufficient input sanitization and output escaping.

References

Community reviews

Loading reviews…