VulnerabilityPublished 23 Feb 2026

CVE-2026-2971: a466350665 Smart-SSO · Cross-site Scripting

Affects a466350665 Smart-SSOSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score

5.3Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to 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 23 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 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
a466350665Smart-SSO	Affected =2.1.0 =2.1.1	Fixed in–

AI-suggested

To mitigate CVE-2026-2971, organizations should implement strict input validation and output encoding on the redirectUri parameter to prevent injection of malicious scripts. Employing Content Security Policy (CSP) headers can reduce the impact of XSS by restricting the execution of unauthorized scripts. Web Application Firewalls (WAFs) should be configured to detect and block suspicious payloads targeting the redirectUri parameter. Educate users to be cautious about clicking unsolicited links, especially those related to login pages. Conduct thorough security testing of the Smart-SSO deployment to identify any other potential injection points. Monitor logs for unusual access patterns or attempts to exploit this vulnerability. Finally, maintain communication with the vendor for any future updates or patches and plan for an upgrade once a fix is released.

Description

A vulnerability was found in a466350665 Smart-SSO up to 2.1.1. Affected by this issue is some unknown functionality of the file smart-sso-server/src/main/resources/templates/login.html of the component Login. Performing a manipulation of the argument redirectUri results in cross site scripting. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2026-2971 is the potential compromise of user sessions and credentials through cross-site scripting attacks. Successful exploitation can lead to session hijacking, allowing attackers to impersonate legitimate users and access sensitive resources. It can also facilitate phishing attacks by injecting malicious scripts that alter the login page or redirect users to fraudulent sites. For organizations relying on Smart-SSO for centralized authentication, this vulnerability undermines trust in their identity management infrastructure and could lead to unauthorized access to multiple connected systems. The medium CVSS score reflects moderate risk, but the real-world impact depends on the deployment scale of Smart-SSO and the sensitivity of protected resources. Since the vulnerability requires user interaction, social engineering is a likely attack vector. The absence of vendor patches increases exposure time, potentially inviting targeted attacks against organizations using affected versions. Overall, the vulnerability poses a significant risk to confidentiality and integrity of authentication processes and user data.

Summary

CVE-2026-2971 is a cross-site scripting vulnerability identified in the Smart-SSO product by a466350665, specifically affecting versions 2.1.0 and 2.1.1. The vulnerability resides in the login.html template file within the smart-sso-server component, where the redirectUri parameter is improperly sanitized. An attacker can craft a malicious URL containing a manipulated redirectUri argument that, when visited by a user, executes arbitrary JavaScript in the victim's browser context. This type of reflected XSS attack can be performed remotely without requiring authentication, but it does require user interaction, such as clicking a malicious link. The vulnerability impacts the confidentiality and integrity of user sessions by enabling potential session hijacking, credential theft, or phishing attacks. The vendor was contacted early but did not respond or provide a patch, leaving the vulnerability unmitigated. The CVSS 4.0 vector indicates low attack complexity and no privileges or user interaction required for the attacker, except that the victim must interact with the malicious link. No known exploits have been observed in the wild, but proof-of-concept exploits have been publicly disclosed. The lack of vendor response increases the urgency for organizations to implement their own mitigations. This vulnerability highlights the importance of proper input validation and output encoding in web applications, especially in authentication-related components like single sign-on systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Mar 2026, 06:35 UTC

Technical details

References

Community reviews

Related threats