Skip to main content
VulnerabilityPublished Updated

CVE-2024-0628: WP RSS Aggregator – RSS Import, News Feeds, Feed to Post, and Autoblogging · Server-Side Request Forgery (SSRF)

Affects WP RSS Aggregator – RSS Import, News Feeds, Feed to Post, and AutobloggingSource CVE Database V5

0

Not known to be exploited · CVSS 3.8 Low.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
3.8Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
jeangalea WP RSS Aggregator – RSS Import, News Feeds, Feed to Post, and AutobloggingAffected
  • =4.23.5
Fixed in–

AI-suggested

  1. Upgrade the WP RSS Aggregator plugin to a version that patches this vulnerability once available.
  2. Restrict administrator access to trusted personnel only and enforce strong authentication methods such as multi-factor authentication (MFA) to reduce the risk of compromised admin accounts.
  3. Implement network segmentation and firewall rules to limit the WordPress server's ability to access sensitive internal services, minimizing the impact of SSRF exploitation.
  4. Monitor and audit administrative actions within WordPress to detect unusual configuration changes or feed source modifications.
  5. Use Web Application Firewalls (WAFs) with SSRF detection capabilities to block suspicious outbound requests originating from the WordPress server.
  6. Regularly review and harden plugin configurations to avoid unnecessary exposure of internal resources.
  7. Employ internal service authentication and authorization controls to prevent unauthorized access even if SSRF occurs.
  8. Consider disabling or limiting the use of RSS feed imports if not essential to reduce attack surface.

Description

The WP RSS Aggregator plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.23.5 via the RSS feed source in admin settings. This makes it possible for authenticated attackers, with administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

References

Community reviews

Loading reviews…