CVE-2024-0580VulnerabilityPublished 18 Jan 2024Updated 2 Jun 2025

CVE-2024-0580: IDMSistemas Sinergia, Sinergia 2.0, and Sinergia Corporativo · Insecure Direct Object Reference

Affects IDMSistemas Sinergia, Sinergia 2.0, and Sinergia CorporativoSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
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 18 Jan 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 2026-10-26.

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

Affected software

Product	Affected	Fixed in
IDMSistemas Sinergia, Sinergia 2.0, and Sinergia Corporativo	Affected =2.0	Fixed in–

AI-suggested

Organizations should implement the following specific mitigation measures: 1) Immediately audit and monitor API access logs for unusual or unauthorized requests targeting the '/qsige.locator/quotePrevious/centers/X' endpoint, focusing on anomalous parameter values. 2) Restrict network access to the affected API endpoints using firewall rules or API gateways to limit exposure to trusted internal users or IP ranges. 3) Enforce strict authentication and authorization controls at the application layer, ensuring that all API requests validate user permissions against the requested resource keys. 4) Engage with IDMSistemas for official patches or updates addressing CVE-2024-0580 and plan prompt deployment once available. 5) If patching is delayed, consider implementing compensating controls such as input validation or API request filtering to block unauthorized parameter values. 6) Conduct security awareness training for users to recognize and report suspicious interactions that could trigger user interaction-based exploitation. 7) Review and enhance overall API security posture, including rate limiting and anomaly detection, to reduce attack surface.

Description

Omission of user-controlled key authorization in the IDMSistemas platform, affecting the QSige product. This vulnerability allows an attacker to extract sensitive information from the API by making a request to the parameter '/qsige.locator/quotePrevious/centers/X', where X supports values 1,2,3, etc.

Impact

For European organizations using IDMSistemas Sinergia products, this vulnerability poses a significant risk to the confidentiality of sensitive business data accessible via the affected API. Since the flaw allows unauthorized extraction of information without authentication, attackers could potentially access confidential operational or financial data, leading to data breaches, competitive disadvantage, or regulatory non-compliance under GDPR. The medium CVSS score reflects that while exploitation requires some user interaction, the lack of required privileges and network accessibility makes exploitation feasible. The impact is heightened for organizations relying heavily on Sinergia 2.0 for critical business processes, especially those handling sensitive personal or corporate data. The absence of integrity or availability impact limits the threat to data leakage rather than system disruption or data manipulation. However, the exposure of sensitive information could lead to secondary attacks such as social engineering or fraud. Given the lack of known exploits, immediate widespread attacks are unlikely but the vulnerability should be considered a moderate risk until patched.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

incibe.es/en/incibe-cert/notices/aviso/omission-key-controlled-authorization-qsige (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 17:11 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats