CVE-2024-42759VulnerabilityPublished 9 Sep 2024Updated 10 Sep 2024

CVE-2024-42759: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 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:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: 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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Sep 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

AI-suggested

1. Restrict access to the /api/usuario/cadastrodesuplente endpoint to only the most trusted and necessary users or systems, using network segmentation and strict access control lists. 2. Implement robust monitoring and logging of API calls to detect unusual or unauthorized privilege escalation attempts promptly. 3. Conduct a thorough audit of user roles and privileges to ensure the principle of least privilege is enforced, minimizing the number of users with high-level access. 4. Apply compensating controls such as multi-factor authentication (MFA) for accounts with high privileges to reduce the risk of account compromise. 5. Engage with the Ellevo vendor or software provider to obtain patches or updates addressing this vulnerability as soon as they become available. 6. Perform regular security assessments and penetration testing focusing on authorization controls around critical API endpoints. 7. Educate internal teams about the risks of privilege escalation and the importance of safeguarding privileged credentials. 8. Consider implementing Web Application Firewalls (WAFs) or API gateways that can enforce additional authorization checks and rate limiting on sensitive endpoints.

Description

An issue in Ellevo v.6.2.0.38160 allows a remote attacker to escalate privileges via the /api/usuario/cadastrodesuplente endpoint.

Impact

The vulnerability allows an attacker with existing high privileges to escalate their access, potentially gaining unauthorized control over sensitive user management functions. This can lead to unauthorized disclosure of confidential information, unauthorized modification of user data or system configurations, and potential disruption of normal operations, although availability impact is low. Organizations relying on Ellevo for critical user management or identity services could face significant risks, including insider threats or attackers leveraging compromised accounts to deepen their foothold. The breach of confidentiality and integrity could result in regulatory non-compliance, reputational damage, and operational disruptions. Since exploitation requires local access with high privileges, the threat is more relevant to organizations with multiple privilege tiers or complex user roles. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially if attackers develop exploits post-disclosure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 07:29 UTC

WeaknessesCWE-592

Technical details

References

Community reviews

Related threats