CVE-2025-11128: CWE-918 Server-Side Request Forgery (SSRF) in themeisle RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator
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.
AI Analysis
Technical Summary
CVE-2025-11128 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the WordPress plugin 'RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator' developed by themeisle. The vulnerability exists in all versions up to and including 5.1.0 within the 'feedzy_sanitize_feeds' function. This function fails to properly validate or sanitize user-supplied input that controls URLs for feed fetching, allowing authenticated users with as low as Subscriber-level privileges to induce the server to make arbitrary HTTP requests. Because the requests originate from the server, attackers can potentially access internal network resources that are otherwise inaccessible externally, such as internal APIs, metadata services, or private endpoints. The vulnerability does not require user interaction beyond authentication and has a CVSS 3.1 base score of 5.0, reflecting medium severity with network attack vector, low attack complexity, and privileges required. No known public exploits have been reported yet. The scope is limited to WordPress sites running this plugin, but the impact can be significant if internal services contain sensitive information. The vulnerability primarily threatens confidentiality, as it can be used to gather information from internal systems, but does not directly affect integrity or availability of the WordPress site or backend services.
Potential Impact
The primary impact of CVE-2025-11128 is unauthorized information disclosure from internal network resources accessible to the vulnerable WordPress server. Attackers with Subscriber-level access can leverage the SSRF to probe internal services, potentially exposing sensitive data such as internal APIs, cloud metadata endpoints, or private databases. This can lead to further attacks like privilege escalation or lateral movement if sensitive information is obtained. While the vulnerability does not directly compromise data integrity or availability, the information gained can facilitate more severe attacks. Organizations running WordPress sites with this plugin are at risk of internal network reconnaissance and data leakage. The medium CVSS score reflects moderate risk, but the ease of exploitation by low-privilege users increases the threat. The lack of known exploits in the wild currently limits immediate widespread impact, but the vulnerability should be addressed promptly to prevent future exploitation.
Mitigation Recommendations
1. Update the 'RSS Aggregator by Feedzy' plugin to a patched version once available from the vendor to eliminate the SSRF vulnerability. 2. Until a patch is released, restrict user roles and permissions to minimize the number of users with Subscriber-level or higher access, especially on sites with untrusted users. 3. Implement web application firewall (WAF) rules to detect and block suspicious outbound HTTP requests originating from the WordPress server, particularly those targeting internal IP ranges or unusual endpoints. 4. Monitor server logs for unusual outbound requests or patterns indicative of SSRF exploitation attempts. 5. Harden internal network services by restricting access to sensitive endpoints and metadata services, using network segmentation and access controls to limit exposure if SSRF occurs. 6. Employ security plugins or custom code to sanitize and validate all user inputs related to feed URLs beyond the vulnerable function. 7. Conduct regular security audits and vulnerability scans on WordPress installations and plugins to detect outdated or vulnerable components.
Affected Countries
United States, India, Germany, United Kingdom, Canada, Australia, France, Brazil, Japan, Netherlands, Italy, Spain
CVE-2025-11128: CWE-918 Server-Side Request Forgery (SSRF) in themeisle RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-11128 is a Server-Side Request Forgery (SSRF) vulnerability classified under CWE-918, found in the WordPress plugin 'RSS Aggregator by Feedzy – Feed to Post, Autoblogging, News & YouTube Video Feeds Aggregator' developed by themeisle. The vulnerability exists in all versions up to and including 5.1.0 within the 'feedzy_sanitize_feeds' function. This function fails to properly validate or sanitize user-supplied input that controls URLs for feed fetching, allowing authenticated users with as low as Subscriber-level privileges to induce the server to make arbitrary HTTP requests. Because the requests originate from the server, attackers can potentially access internal network resources that are otherwise inaccessible externally, such as internal APIs, metadata services, or private endpoints. The vulnerability does not require user interaction beyond authentication and has a CVSS 3.1 base score of 5.0, reflecting medium severity with network attack vector, low attack complexity, and privileges required. No known public exploits have been reported yet. The scope is limited to WordPress sites running this plugin, but the impact can be significant if internal services contain sensitive information. The vulnerability primarily threatens confidentiality, as it can be used to gather information from internal systems, but does not directly affect integrity or availability of the WordPress site or backend services.
Potential Impact
The primary impact of CVE-2025-11128 is unauthorized information disclosure from internal network resources accessible to the vulnerable WordPress server. Attackers with Subscriber-level access can leverage the SSRF to probe internal services, potentially exposing sensitive data such as internal APIs, cloud metadata endpoints, or private databases. This can lead to further attacks like privilege escalation or lateral movement if sensitive information is obtained. While the vulnerability does not directly compromise data integrity or availability, the information gained can facilitate more severe attacks. Organizations running WordPress sites with this plugin are at risk of internal network reconnaissance and data leakage. The medium CVSS score reflects moderate risk, but the ease of exploitation by low-privilege users increases the threat. The lack of known exploits in the wild currently limits immediate widespread impact, but the vulnerability should be addressed promptly to prevent future exploitation.
Mitigation Recommendations
1. Update the 'RSS Aggregator by Feedzy' plugin to a patched version once available from the vendor to eliminate the SSRF vulnerability. 2. Until a patch is released, restrict user roles and permissions to minimize the number of users with Subscriber-level or higher access, especially on sites with untrusted users. 3. Implement web application firewall (WAF) rules to detect and block suspicious outbound HTTP requests originating from the WordPress server, particularly those targeting internal IP ranges or unusual endpoints. 4. Monitor server logs for unusual outbound requests or patterns indicative of SSRF exploitation attempts. 5. Harden internal network services by restricting access to sensitive endpoints and metadata services, using network segmentation and access controls to limit exposure if SSRF occurs. 6. Employ security plugins or custom code to sanitize and validate all user inputs related to feed URLs beyond the vulnerable function. 7. Conduct regular security audits and vulnerability scans on WordPress installations and plugins to detect outdated or vulnerable components.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-27T21:52:08.932Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68fa270960d00e69dc99fa69
Added to database: 10/23/2025, 1:00:57 PM
Last enriched: 2/27/2026, 6:46:30 PM
Last updated: 3/24/2026, 9:18:44 PM
Views: 227
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.