CVE-2026-3189
Server-Side Request Forgery in feiyuchuixue sz-boot-parent Download API
Publication date: 2026-02-25
Last updated on: 2026-02-25
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| feiyuchuixue | sz-boot-parent | to 1.3.2-beta (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-3189 is a server-side request forgery (SSRF) vulnerability found in the feiyuchuixue sz-boot-parent project, affecting versions up to 1.3.2-beta. It exists in the file download functionality at the endpoint /api/admin/common/files/download. By manipulating the url argument, an attacker can cause the server to make unauthorized requests to arbitrary URLs. This happens because the server does not adequately validate the requested URL, allowing it to retrieve content from unintended destinations.
The vulnerability can be exploited remotely, but exploitation is considered difficult and no public exploit currently exists. The project fixed this issue by adding a URL protocol whitelist validation, allowing only http and https protocols, and upgrading to version 1.3.3-beta eliminates the vulnerability.
How can this vulnerability impact me? :
This vulnerability allows an attacker to make the server perform unauthorized requests to arbitrary URLs, potentially exposing internal resources or sensitive information. It can lead to unauthorized access to server resources and may allow attackers to read arbitrary files if certain configurations are not set properly.
Although the exploitability is difficult and the severity is rated low to moderate (CVSS v3 base score 3.1), successful exploitation could compromise confidentiality by exposing internal network services or sensitive data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring and analyzing requests made to the endpoint /api/admin/common/files/download, specifically looking for manipulation of the url argument that could indicate attempts to exploit server-side request forgery (SSRF).'}, {'type': 'paragraph', 'content': 'Since the vulnerability involves SSRF through the url parameter, detection can involve inspecting logs or network traffic for unusual or unauthorized outbound requests initiated by the server.'}, {'type': 'paragraph', 'content': 'Suggested commands include using web server access logs or network monitoring tools to filter requests to the vulnerable endpoint. For example, using grep on server logs:'}, {'type': 'list_item', 'content': 'grep "/api/admin/common/files/download" /var/log/nginx/access.log'}, {'type': 'list_item', 'content': 'grep "url=" /var/log/nginx/access.log | grep -E "http|https|file|ftp|gopher"'}, {'type': 'paragraph', 'content': 'Additionally, network monitoring tools like tcpdump or Wireshark can be used to capture outbound HTTP/HTTPS requests from the server that may be triggered by SSRF attempts.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'The primary and recommended mitigation is to upgrade the affected component feiyuchuixue sz-boot-parent to version 1.3.3-beta, which includes a patch that adds a URL protocol whitelist validation allowing only http and https protocols.'}, {'type': 'paragraph', 'content': 'This upgrade effectively prevents exploitation by disallowing potentially dangerous protocols in the url argument.'}, {'type': 'paragraph', 'content': 'If immediate upgrading is not possible, consider restricting access to the vulnerable endpoint /api/admin/common/files/download to trusted users only and monitoring for suspicious activity.'}, {'type': 'paragraph', 'content': 'Also, ensure that the configuration parameter oss.accessMode is set to "private" to prevent arbitrary file read vulnerabilities associated with this issue.'}] [1, 2]