VulnerabilityPublished 6 Aug 2025

CVE-2025-46660: Insecure Storage of Sensitive Information

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 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 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 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 immediately assess whether they are using 4C Strategies Exonaut 21.6 and confirm if their password storage mechanism lacks salting. Specific mitigation steps include: 1) Coordinating with 4C Strategies to obtain patches or updates that implement salted password hashing using strong algorithms such as bcrypt, Argon2, or PBKDF2. 2) If patches are unavailable, plan for a secure password reset for all users combined with migration to a more secure password storage scheme. 3) Implement additional security controls around the database storing password hashes, including strict access controls, encryption at rest, and monitoring for unauthorized access attempts. 4) Conduct regular audits of password policies and enforce strong password complexity requirements to reduce the risk of password cracking. 5) Employ multi-factor authentication (MFA) to mitigate the risk of compromised passwords leading to account takeover. 6) Monitor threat intelligence sources for any emerging exploits targeting this vulnerability. 7) Educate users about phishing and credential security to reduce the risk of credential theft through social engineering.

Description

An issue was discovered in 4C Strategies Exonaut 21.6. Passwords, stored in the database, are hashed without a salt.

Impact

For European organizations using 4C Strategies Exonaut 21.6, this vulnerability poses a significant risk to the confidentiality and integrity of user credentials. If attackers obtain the password hashes, they can potentially recover passwords more easily due to the lack of salting, leading to unauthorized access to sensitive systems and data. This could result in data breaches, unauthorized data manipulation, and disruption of business operations. Given that Exonaut is a platform used for project and risk management, compromised accounts could allow attackers to access sensitive project information, strategic plans, or personal data of employees and partners. The impact is heightened in sectors with strict data protection regulations such as GDPR, where data breaches can lead to substantial fines and reputational damage. Additionally, compromised credentials could be used for lateral movement within networks, increasing the scope of potential damage. Although no active exploits are reported, the vulnerability represents a latent threat that could be exploited if attackers gain database access through other means.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Aug 2025, 20:47 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats