How severe is GHSA-mqqg-xjhj-wfgw?

GHSA-mqqg-xjhj-wfgw has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-mqqg-xjhj-wfgw?

GHSA-mqqg-xjhj-wfgw affects the following packages: miniflux.app/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-mqqg-xjhj-wfgw?

Update miniflux.app/v2 to 2.0.43 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqqg-xjhj-wfgw is resolved across your whole dependency graph.

How do I detect GHSA-mqqg-xjhj-wfgw in my Go dependencies?

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.

How do I mitigate GHSA-mqqg-xjhj-wfgw if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-mqqg-xjhj-wfgw actively exploited in the wild?

No public exploit code has been indexed for GHSA-mqqg-xjhj-wfgw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-mqqg-xjhj-wfgw?

GHSA-mqqg-xjhj-wfgw has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mqqg-xjhj-wfgw?

GHSA-mqqg-xjhj-wfgw is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-mqqg-xjhj-wfgw published, and has it been updated?

GHSA-mqqg-xjhj-wfgw was published on April 2, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

Stored XSS in Miniflux when opening a broken image due to unescaped ServerError in proxy handlerGHSA-mqqg-xjhj-wfgw

Q: What is GHSA-mqqg-xjhj-wfgw?

### Impact Since [v2.0.25](https://github.com/miniflux/v2/releases/tag/2.0.25), Miniflux will automatically [proxy](https://miniflux.app/docs/configuration.html#proxy-images) images served over HTTP to prevent mixed content errors. When an outbound request made by the Go HTTP client fails, the `html.ServerError` is [returned](https://github.com/miniflux/v2/blob/b2fd84e0d376a3af6329b9bb2e772ce38a25c31c/ui/proxy.go#L76) unescaped without the expected Content Security Policy [header](https://github.com/miniflux/v2/blob/b2fd84e0d376a3af6329b9bb2e772ce38a25c31c/ui/proxy.go#L90) added to valid res

MEDIUMFix: miniflux/v2#1746

GHSA-mqqg-xjhj-wfgw is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in miniflux.app/v2. A fix is available for miniflux.app/v2 — see the affected versions and patch details below.

Also known asCVE-2023-27592

Published

Apr 2, 2025

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mqqg-xjhj-wfgw.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹miniflux.app/v2

Real-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

Impact

Since v2.0.25, Miniflux will automatically proxy images served over HTTP to prevent mixed content errors.

When an outbound request made by the Go HTTP client fails, the html.ServerError is returned unescaped without the expected Content Security Policy header added to valid responses.

By creating an RSS feed item with the inline description containing an <img> tag with a srcset attribute pointing to an invalid URL like http:a<script>alert(1)</script>, we can coerce the proxy handler into an error condition where the invalid URL is returned unescaped and in full.

This results in JavaScript execution on the Miniflux instance as soon as the user is convinced (e.g. by a message in the alt text) to open the broken image.

An attacker can execute arbitrary JavaScript in the context of a victim Miniflux user when they open a broken image in a crafted RSS feed. This can be used to perform actions on the Miniflux instance as that user and gain administrative access to the Miniflux instance if it is reachable and the victim is an administrator.

Patches

PR #1746 fixes the problem. Available in Miniflux >= 2.0.43.

Workarounds

Disable image proxy (default value is http-only).

References

https://miniflux.app/docs/configuration.html#proxy-images

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`miniflux.app/v2`	≥ 2.0.25&&< 2.0.43	2.0.43`go get miniflux.app/v2@v2.0.43`

Affected Products

1 product · 1 configurations

Application

minifluxminiflux_project

≥ 2.0.25 && < 2.0.43

range

Detection & mitigation playbook

Open-source dependency

Detect
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.0.43 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mqqg-xjhj-wfgw is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Since [v2.0.25](https://github.com/miniflux/v2/releases/tag/2.0.25), Miniflux will automatically [proxy](https://miniflux.app/docs/configuration.html#proxy-images) images served over HTTP to prevent mixed content errors. When an outbound request made by the Go HTTP client fails, the `html.ServerError` is [returned](https://github.com/miniflux/v2/blob/b2fd84e0d376a3af6329b9bb2e772ce38a25c31c/ui/proxy.go#L76) unescaped without the expected Content Security Policy [header](https://github.com/miniflux/v2/blob/b2fd84e0d376a3af6329b9bb2e772ce38a25c31c/ui/proxy.go#L90) added to valid res