VulnerabilityPublished 25 Feb 2026

CVE-2026-3189: feiyuchuixue sz-boot-parent · Server-Side Request Forgery

Affects feiyuchuixue sz-boot-parentSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.3 Low.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
feiyuchuixuesz-boot-parent	Affected =1.3.2-beta	Fixed in–
GitHubfeiyuchuixue/sz-boot-parent`pkg:github/feiyuchuixue/sz-boot-parent`Other threats	Affected =1.3.2-beta	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade feiyuchuixue sz-boot-parent to version 1.3.3-beta or later, which includes a patch enforcing a strict URL protocol whitelist allowing only http and https protocols. Until the upgrade can be applied, administrators should implement network-level controls to restrict outbound HTTP/HTTPS requests from the application server to only trusted destinations. Additionally, review and restrict access to the /api/admin/common/files/download endpoint to trusted and authenticated users only. Employ application-layer firewalls or web application firewalls (WAFs) to detect and block suspicious SSRF patterns targeting the vulnerable parameter. Conduct thorough logging and monitoring of outbound requests from the server to detect anomalous behavior indicative of SSRF exploitation attempts. Finally, perform regular security assessments and code reviews to identify and remediate similar input validation weaknesses.

Description

A weakness has been identified in feiyuchuixue sz-boot-parent up to 1.3.2-beta. This vulnerability affects unknown code of the file /api/admin/common/files/download. Executing a manipulation of the argument url can lead to server-side request forgery. The attack can be executed remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. Upgrading to version 1.3.3-beta is able to resolve this issue. This patch is called aefaabfd7527188bfba3c8c9eee17c316d094802. Upgrading the affected component is advised. The project was informed beforehand and acted very professional: "We have added a URL protocol whitelist validation to the file download interface, allowing only http and https protocols."

Impact

The primary impact of this SSRF vulnerability is the potential for attackers to make unauthorized requests from the vulnerable server to internal or external systems. This can lead to information disclosure about internal network infrastructure or access to otherwise inaccessible resources. However, the impact is limited by the high complexity of exploitation and the vendor's mitigation measures. Since the vulnerability requires low privileges and no user interaction, it could be leveraged by authenticated users with limited access, potentially elevating their ability to perform reconnaissance or pivot attacks. The low CVSS score reflects the limited confidentiality, integrity, and availability impacts. Organizations running affected versions may face risks of internal network exposure or indirect attacks on internal services if the vulnerability is exploited. However, no direct code execution or data modification is indicated, limiting the severity of the threat.

Summary

CVE-2026-3189 identifies a server-side request forgery (SSRF) vulnerability in the feiyuchuixue sz-boot-parent software, specifically affecting versions up to 1.3.2-beta. The vulnerability exists in the /api/admin/common/files/download endpoint, where the 'url' parameter is insufficiently validated, allowing an attacker to craft requests that cause the server to make unintended HTTP or HTTPS requests to arbitrary locations. SSRF vulnerabilities can be leveraged to access internal systems, bypass firewalls, or perform reconnaissance on internal networks. However, in this case, the exploitability is rated as difficult due to the complexity of crafting a successful attack and the requirement for low-level privileges (PR:L). The vendor responded professionally by releasing version 1.3.3-beta, which introduces a URL protocol whitelist that restricts allowed protocols to http and https, effectively mitigating the vulnerability. The CVSS 4.0 vector indicates network attack vector (AV:N), high attack complexity (AC:H), no privileges required (PR:L), no user interaction (UI:N), and low impact on confidentiality, integrity, and availability (VC:L, VI:N, VA:N). No known exploits have been reported in the wild, and the vulnerability was responsibly disclosed and patched promptly.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Feb 2026, 20:56 UTC

Technical details

References

Community reviews

Related threats