VulnerabilityPublished 3 Nov 2025

CVE-2025-12623: fushengqian fuint · Authorization Bypass

Affects fushengqian fuintSource CVE Database V5

Public exploit available · CVSS 2.3 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

2.3Low

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% 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:P

Base metrics

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

Threat metrics

Exploit Maturity: POC

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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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

AI-suggested

European organizations should implement the following specific mitigations: 1) Conduct a thorough audit of all authentication and authorization mechanisms within fushengqian fuint deployments, focusing on token handling and API access controls. 2) Restrict network exposure of the affected ClientSignController endpoints by applying network segmentation and firewall rules to limit access to trusted sources only. 3) Monitor logs and authentication events for unusual access patterns or failed authorization attempts that could indicate exploitation attempts. 4) Engage with the vendor or community to obtain the latest patches or updates addressing this vulnerability, and apply them promptly despite the rolling release model. 5) Implement additional compensating controls such as multi-factor authentication (MFA) on affected services to reduce the risk of unauthorized access. 6) If possible, deploy Web Application Firewalls (WAFs) with custom rules to detect and block suspicious token manipulation or unauthorized API calls. 7) Educate development and security teams about the vulnerability to ensure secure coding practices and rapid response to future disclosures.

Description

A vulnerability was identified in fushengqian fuint up to 41e26be8a2c609413a0feaa69bdad33a71ae8032. Affected by this issue is some unknown functionality of the file fuint-application/src/main/java/com/fuint/module/clientApi/controller/ClientSignController.java of the component Authentication Token Handler. Such manipulation leads to authorization bypass. The attack may be launched remotely. Attacks of this nature are highly complex. The exploitation is known to be difficult. The exploit is publicly available and might be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.

Impact

For European organizations, the impact of this vulnerability is generally low due to the high complexity of exploitation and limited scope of impact. However, organizations relying on fushengqian fuint for critical authentication or client API services could face unauthorized access risks if attackers successfully exploit the flaw. This could lead to exposure of sensitive data or unauthorized operations within the application, potentially violating data protection regulations such as GDPR. The rolling release nature of the product means that unpatched instances may persist, increasing exposure. Sectors with high reliance on secure authentication, such as finance, healthcare, or government services, could be more affected. Additionally, organizations with internet-facing APIs using this product are at greater risk. While no active exploitation is currently known, the availability of public exploit code raises the possibility of future targeted attacks, especially against high-value targets in Europe.

Summary

CVE-2025-12623 is an authorization bypass vulnerability identified in the fushengqian fuint software, specifically within the Authentication Token Handler component implemented in the ClientSignController.java file. The vulnerability allows an attacker to manipulate authentication tokens or related authorization mechanisms to gain unauthorized access to protected resources or functionality. The attack vector is remote, and while no user interaction is required, the attack complexity is high, meaning exploitation demands significant skill or specific conditions. The vulnerability affects a particular commit version (41e26be8a2c609413a0feaa69bdad33a71ae8032) of the software, but due to the product’s rolling release nature, exact affected versions are not clearly delineated. The CVSS 4.0 base score is 2.3, indicating a low severity primarily because the impact on confidentiality, integrity, and availability is limited, and exploitation is difficult. No known exploits have been observed in the wild, but public exploit code exists, increasing the risk of future attacks. The vulnerability arises from insufficient authorization checks in the token handling logic, potentially allowing attackers with limited privileges to bypass controls and access restricted API endpoints or functions. This could lead to unauthorized data access or actions within the application context.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 3 Nov 2025, 08:21 UTC

Technical details

References

Community reviews

Related threats