dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-11128

MEDIUM · 5.0 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Feedzy WordPress plugin contains an SSRF vulnerability in the feedzy_sanitize_feeds function. Authenticated attackers with Subscriber-level access can make arbitrary web requests from the server, potentially reaching internal services.

MitigationUpdate the Feedzy plugin to a version newer than 5.1.0 when available. Until then, restrict subscriber-level access permissions and implement server-level firewall rules to block suspicious outbound requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Feedzy plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Feedzy RSS Feeds' or check the plugin files in /wp-content/plugins/ for feedzy-related directories
    Affected if Feedzy plugin is installed and active
  2. Check installed Feedzy version
    In WordPress admin, go to Plugins > Installed Plugins > Feedzy RSS Feeds and note the version number displayed, or read the version from the plugin header in feedzy.php
    Affected if Version is 5.1.0 or earlier (versions prior to the fix)
  3. Confirm subscriber-level user accounts exist
    In WordPress admin, go to Users and review the role assigned to each account; check for any users with 'Subscriber' role
    Affected if At least one user with Subscriber role exists in the WordPress installation
  4. Verify feed import functionality is accessible
    Check if Feedzy's feed import feature (Feedzy > Import Feeds) is configured and accessible to subscriber-level users through WordPress role capabilities
    Affected if The feed import functionality is enabled and accessible to users with Subscriber role permissions

If Feedzy plugin version 5.1.0 or earlier is installed, active, and the site has subscriber-level accounts with access to the feed import feature, the environment is affected by this SSRF vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Feedzy plugin to a version newer than 5.1.0 when available. Until then, restrict subscriber-level access permissions and implement server-level firewall rules to block suspicious outbound requests.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11128 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data