🛡️ CVE-2024-50618 — cipace

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability none.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
• Integrity impact: None.
• Availability impact: None.

Weakness class

CVE-2024-50618 is classified as CWE-308: Use of Single-factor Authentication. The product uses an authentication algorithm that uses a single factor (e.g., a password) in a security context that should require more than one factor.

Affected software

CVE-2024-50618 is recorded against 1 package.

• cipace (fixed in 9.17)

Timeline and source

Published on 11 February 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

cipplanner.com

Other advisories for this package

cipace has other advisories on record. If you are patching this one, these are worth checking on the same host:

• CVE-2024-50617 (7.5 High, published 11 Feb 2026)
• CVE-2024-50620 (8.8 High, published 11 Feb 2026)
• CVE-2024-50619 (8.8 High, published 11 Feb 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-308: Use of Single-factor Authentication) in other software:

• CVE-2026-67611 (8.1 High, published 3 Aug 2026)
• CVE-2026-15616 (9.1 Critical, published 23 Jul 2026)
• CVE-2026-56022 (5.3 Medium, published 18 Jun 2026)
• CVE-2024-27928 (published 17 Jun 2026)
• CVE-2026-45749 (8.1 High, published 5 Jun 2026)
• CVE-2026-33550 (2.0 Low, published 22 Mar 2026)
• CVE-2025-42959 (8.1 High, published 8 Jul 2025)
• CVE-2024-47652 (8.1 High, published 4 Oct 2024)

Details

Affected Packages

References