GHSA-xwh2-742g-w3wp — v2
MEDIUMGHSA-xwh2-742g-w3wp is a medium-severity (CVSS 6.5) Server-Side Request Forgery (SSRF) vulnerability in miniflux.app/v2. A fix is available for miniflux.app/v2 — see the affected versions and patch details below.
Miniflux Media Proxy SSRF via /proxy endpoint allows access to internal network resources
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xwh2-742g-w3wp.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-xwh2-742g-w3wp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
miniflux.app/v2Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Miniflux's media proxy endpoint (GET /proxy/{encodedDigest}/{encodedURL}) can be abused to perform Server-Side Request Forgery (SSRF). An authenticated user can cause Miniflux to generate a signed proxy URL for attacker-chosen media URLs embedded in feed entry content, including internal addresses (e.g., localhost, private RFC1918 ranges, or link-local metadata endpoints). Requesting the resulting /proxy/... URL makes Miniflux fetch and return the internal response.
Details
- Vulnerable route:
GET /proxy/{encodedDigest}/{encodedURL}(accessible without authentication, but requires a server-generated HMAC-signed URL) - Handler:
internal/ui/proxy.go((*handler).mediaProxy) - Trigger: entry content is rewritten to proxy media URLs (e.g.,
mediaproxy.RewriteDocumentWithAbsoluteProxyURL(...)), producing signed/proxy/...URLs. - Root cause: the proxy validates the URL scheme and HMAC signature, but does not restrict target hosts/IPs. As a result, requests to loopback/private/link-local addresses are allowed and fetched by the server.
PoC
-
Run Miniflux 2.2.15 with default configuration (media proxy enabled by default:
MEDIA_PROXY_MODE=http-only). -
Log in with any normal user account.
-
Subscribe to a feed you control that contains an entry with an image URL pointing to an internal address reachable from the Miniflux server, e.g.:
<img src="http://<internal-target>/secret">(Note:<internal-target>must be reachable from the Miniflux process/network; in containerized setups,127.0.0.1may not refer to the host.)
-
Open the entry and locate the rewritten media proxy URL (
/proxy/<encodedDigest>/<encodedURL>) in the rendered HTML/page source. -
Request the
/proxy/...URL. Expected (vulnerable): Miniflux fetches the internal URL and returns the internal response (SSRF).
Impact
Type: SSRF (Server-Side Request Forgery) via media proxy
Who is impacted: Miniflux instances with media proxy enabled (default configuration typically enables it for HTTP/mixed content handling).
Impact: attackers with a valid Miniflux account can fetch internal resources reachable from the Miniflux server (e.g., localhost services, private network services, and link-local endpoints such as 169.254.169.254), potentially exposing sensitive data.
Suggested CVSS (v3.1)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N (Base 6.5)
If there any questions or issues reproducing this, please contact: [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | miniflux.app/v2 | all versions | 2.2.16go get miniflux.app/v2@v2.2.16 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for miniflux.app/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update miniflux.app/v2 to 2.2.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwh2-742g-w3wp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xwh2-742g-w3wp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xwh2-742g-w3wp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xwh2-742g-w3wp in your dependencies?
O3 Security finds GHSA-xwh2-742g-w3wp across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.