CVE-2025-11128 MEDIUM

CVE-2025-11128: Feedzy RSS Feeds Lite <= 5.1.0 - Authenticated (Subscriber+) Server-Side Request Forgery

Vendor Themeisle
Product RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator
Weakness CWE-918 · SSRF
Published October 23, 2025
Last update April 8, 2026

CVSS base score

5.0/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity None

CVSS vector

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

What the vulnerability does

01Description

The RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.1.0 via the 'feedzy_sanitize_feeds' function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query information from internal services.

Explanation of Vulnerability in Simple Terms

02Summary

RSS Aggregator by Feedzy contains a server-side request forgery vulnerability that allows authenticated users to make the site send HTTP requests to internal or external systems on the attacker's behalf. An attacker with low-level WordPress access can probe internal networks or interact with services restricted to the site's server. The vulnerability affects all versions up to 5.1.0.

What an attacker can do

03Attacker Capabilities

Make the site send HTTP requests to internal networks or external services under the site's identity.

Potential impact on your site

04Site Impact

Attackers with WordPress accounts can probe your internal network, access restricted services, or exfiltrate data via the site's outbound requests.

Conditions required to exploit

05Prerequisites

Attacker must have a low-level WordPress user account (e.g., contributor or subscriber with plugin access).

Key dates

06Disclosure timeline

October 23, 2025 CVE published
April 8, 2026 Record updated