VulnerabilityPublished 6 Oct 2025

CVE-2025-11322: Mangati NovoSGA · Weak Password Requirements

Affects Mangati NovoSGASource CVE Database V5

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

6.3Medium

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/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: None
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: 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: 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 6 Oct 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

Affected software

Product	Affected	Fixed in
Mangati NovoSGA	Affected 2.2.0 – 2.2.12 13 affected builds	Fixed in–

AI-suggested

These include: 1) Restrict network access to the User Creation Page, limiting it to trusted internal networks or VPNs. 2) Implement external strong password policies and validation mechanisms at the network or application gateway level to enforce complexity on account creation requests. 3) Monitor logs for unusual account creation activity or weak password usage. 4) Conduct regular audits of user accounts to identify and remediate weak passwords. 5) Employ multi-factor authentication (MFA) for all accounts created through NovoSGA to mitigate risks from weak passwords. 6) Engage with Mangati for updates and consider alternative solutions if remediation is delayed. 7) Educate administrators on the risks and ensure strict operational procedures around user management. These targeted actions go beyond generic advice by focusing on access controls, monitoring, and compensating authentication mechanisms.

Description

A flaw has been found in Mangati NovoSGA up to 2.2.12. The impacted element is an unknown function of the file /novosga.users/new of the component User Creation Page. Executing manipulation of the argument Senha/Confirmação da senha can lead to weak password requirements. The attack can be launched remotely. Attacks of this nature are highly complex. The exploitability is regarded as difficult. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using Mangati NovoSGA, this vulnerability poses a risk of unauthorized account creation with weak passwords, potentially leading to credential compromise and unauthorized access to sensitive service management data. This can result in data breaches, disruption of service management workflows, and potential escalation of privileges if attackers leverage weak credentials to move laterally. The medium severity indicates a moderate risk, but the lack of vendor response and patches increases exposure duration. Organizations in sectors relying heavily on service management platforms, such as public administration, utilities, and large enterprises, may face operational and reputational impacts. Confidentiality is the primary concern, but integrity and availability could be indirectly affected if attackers manipulate service management processes. The remote exploitability without authentication increases the threat surface, especially if the User Creation Page is exposed to untrusted networks or the internet.

Summary

CVE-2025-11322 identifies a vulnerability in Mangati NovoSGA, a software product used for service management, affecting all versions up to 2.2.12. The flaw resides in the User Creation Page component, specifically in the handling of the password (Senha) and password confirmation fields. Due to improper validation or enforcement of password complexity requirements, an attacker can remotely manipulate these fields to create user accounts with weak passwords. This undermines the intended security controls designed to enforce strong credential policies. The vulnerability can be exploited remotely without authentication or user interaction, but the attack complexity is high, indicating that a skilled attacker is required. Although the exploit has been published, no known exploits are currently observed in the wild. The vendor was notified but has not issued a patch or response, leaving affected systems exposed. The CVSS 4.0 base score is 6.3 (medium severity), reflecting the network attack vector, high attack complexity, no privileges or user interaction needed, and limited impact on confidentiality. The vulnerability primarily threatens confidentiality by enabling weak credentials that could be leveraged for unauthorized access or lateral movement within affected environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Oct 2025, 05:44 UTC

Technical details

References

Community reviews

Related threats