CVE-2025-67713
BaseFortify
Publication date: 2025-12-11
Last updated on: 2026-02-02
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| miniflux_project | miniflux | to 2.2.15 (inc) |
| miniflux | miniflux | 2.2.14 |
| miniflux | miniflux | 2.2.15 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-601 | The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Miniflux 2 versions 2.2.14 and below, where the application treats redirect_url as safe if url.Parse(...).IsAbs() returns false. Protocol-relative URLs like //ikotaslabs.com have an empty scheme and pass this check, allowing attackers to craft post-login redirects to malicious sites, enabling phishing attacks after login. The issue is fixed in version 2.2.15.
How can this vulnerability impact me? :
An attacker can exploit this vulnerability to redirect users after login to attacker-controlled websites, potentially leading to phishing attacks. This can compromise user trust, expose users to malicious content, and result in credential theft or other security breaches.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Miniflux to version 2.2.15 or later, as this version fixes the vulnerability related to unsafe handling of redirect_url. Avoid using versions 2.2.14 and below.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if your Miniflux v2 instance is running version 2.2.14 or below, as these versions are vulnerable. Additionally, you can monitor HTTP requests to the login endpoint for the presence of the `redirect_url` parameter containing protocol-relative URLs (e.g., URLs starting with `//`). For example, you can use network traffic inspection tools like tcpdump or Wireshark to filter requests with such parameters. A sample command to capture such HTTP requests using tcpdump might be: `tcpdump -A -s 0 'tcp port 80 or tcp port 443' | grep 'redirect_url=//'`. Alternatively, you can review server logs for login requests containing `redirect_url=//`. There is no specific built-in command provided in the resources, but these general network inspection methods can help detect exploitation attempts. [2]