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

CVE-2025-11467

MEDIUM · 5.8 CVSS v3.1 Published 2025-12-11

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

67/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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

Technical summary

dbcve analysis · moderate confidence

The Feedzy plugin for WordPress contains a blind Server-Side Request Forgery (SSRF) vulnerability in the feedzy_lazy_load function, allowing unauthenticated attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This can be exploited to probe internal services, bypass network segmentation, and potentially access sensitive information from internal systems.

MitigationUpdate the Feedzy plugin to version 5.1.2 or later when available. If no patch is immediately available, consider deploying a WAF rule to filter outgoing requests from the application or temporarily disable the affected functionality.

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

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Confirm Feedzy plugin is installed

In WordPress admin, go to Plugins > Installed Plugins and look for 'Feedzy RSS Feeds', or check if the directory /wp-content/plugins/feedzy-rss-feeds/ exists on the server

Affected if Feedzy RSS Feeds plugin is not present on the WordPress installation
Determine installed Feedzy version

In WordPress admin, go to Plugins > Feedzy RSS Feeds and view the version number, or open feedzy-rss-feeds/feedzy.php and read the Version header in the plugin comment block

Affected if Version is lower than 5.1.2 or the version cannot be determined
Check if lazy load functionality is in use

Search WordPress posts, pages, or widgets for the [feedzy-rss] shortcode, or check Feedzy settings at /wp-admin/admin.php?page=feedzy-settings for lazy load configuration

Affected if Lazy load is enabled and feedzy shortcodes or feeds are actively used on the site

The environment is affected if Feedzy RSS Feeds plugin is installed with a version prior to 5.1.2 and the lazy load feature (feedzy_lazy_load function) is enabled or in use on the site.

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update the Feedzy plugin to version 5.1.2 or later when available. If no patch is immediately available, consider deploying a WAF rule to filter outgoing requests from the application or temporarily disable the affected functionality.

Recommended fix Moderate confidence

Version 5.1.2 or later (latest stable release)

Log in to the WordPress admin dashboard
Navigate to Plugins > Installed Plugins
Locate 'RSS Aggregator by Feedzy' in the plugin list
Check the current version installed
If the installed version is 5.1.1 or below, click 'Update Now' to upgrade to the latest version
Alternatively, download the latest version from wordpress.org/plugins/feedzy-rss-feeds/ and upload manually via Plugins > Add New > Upload Plugin
After updating, verify the version number reflects the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-11467 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-11467?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 5.8 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

Need this fixed?

Have this fixed 6 hrs · Moderate

Typical engagement from $1,060

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-11467 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References