VulnerabilityPublished 28 Feb 2024Updated 15 Nov 2024

CVE-2024-26559: Insecure Storage of Sensitive Information

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% 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 28 Feb 2024
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 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

1. Immediately restrict network access to uverif 2.0 instances by implementing firewall rules or network segmentation to limit exposure to trusted internal networks only. 2. Employ strict access control policies and monitor access logs for unusual or unauthorized attempts to query uverif services. 3. Disable or limit any unnecessary remote interfaces or services associated with uverif to reduce attack vectors. 4. Conduct thorough inventory and asset management to identify all deployments of uverif 2.0 within the organization. 5. Prepare for rapid deployment of patches or updates once the vendor releases a fix; subscribe to vendor advisories and CVE databases for updates. 6. Consider deploying intrusion detection or prevention systems (IDS/IPS) with signatures or heuristics to detect anomalous queries targeting uverif. 7. Educate security teams about this vulnerability to ensure timely response and incident handling if exploitation attempts are detected. 8. If feasible, implement encryption and additional authentication layers around uverif services to mitigate unauthorized data access.

Description

An issue in uverif v.2.0 allows a remote attacker to obtain sensitive information.

Impact

The primary impact of CVE-2024-26559 is unauthorized disclosure of sensitive information, which can compromise confidentiality for organizations using uverif 2.0. This exposure could lead to leakage of credentials, configuration details, or other sensitive data, enabling attackers to escalate privileges or conduct further targeted attacks. Although the vulnerability does not affect system integrity or availability, the confidentiality breach alone can have significant consequences, including regulatory non-compliance, reputational damage, and financial loss. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on uverif for verification or authentication processes are particularly at risk. The remote and unauthenticated nature of the exploit increases the attack surface, especially if uverif services are exposed to untrusted networks or the internet. Without available patches, the risk persists until mitigations are applied or updates are released.

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

syst1m.cn/2024/01/22/U%E9%AA%8C%E8%AF%81%E7%BD%91%E7%BB%9C%E7%94%A8%E6%88%B7%E7%AE%A1%E7%90%86%E7%B3%BB%E7%BB%9F_%E4%BB%BB%E6%84%8F%E6%96%87%E4%BB%B6%E8%AF%BB%E5%8F%96%E6%BC%8F%E6%B4%9E/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 10:06 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats