CVE-2024-10718
Phpipam ≤ 1.7.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-10718 is a high-severity Sensitive Cookie in HTTPS Session Without 'Secure' Attribute (CWE-614) vulnerability in Phpipam Phpipam. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-10718 is a vulnerability in phpipam/phpipam version 1.5.1, an open-source IP address management application. The issue arises because the Secure attribute is not set on sensitive cookies during HTTPS sessions, which can lead user agents to transmit those cookies in plaintext over HTTP connections, potentially exposing sensitive information. This flaw corresponds to CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute) and CWE-319 (Cleartext Transmission of Sensitive Information), with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
The vulnerability can be exploited by any network attacker with low complexity and no privileges or user interaction required. An adversary positioned to observe traffic could capture sensitive cookies if a victim's browser downgrades to an HTTP session, such as through interception on unsecured networks. Successful exploitation enables high-impact confidentiality violations by disclosing cookie contents, which may include session tokens or other sensitive data.
Mitigation is provided in phpipam/phpipam version 1.7.0, where the Secure attribute is properly implemented, as detailed in the fix commit at https://github.com/phpipam/phpipam/commit/ddf70ef6801442eb8b0be5eea829e470e653c70e. Security practitioners should upgrade affected installations to version 1.7.0 or later. Further details are available in the Huntr.dev bounty report at https://huntr.com/bounties/725bce8f-328f-4fbc-acf5-46ea920cd3c1.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-7079
Vulnerability Data
In phpipam/phpipam version 1.5.1, the Secure attribute for sensitive cookies in HTTPS sessions is not set. This could cause the user agent to send those cookies in plaintext over an HTTP session, potentially exposing sensitive information. The issue is fixed…
more
in version 1.7.0.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.1
Mitigating Controls (NIST 800-53 r5) AI
SC-8 directly requires protecting confidentiality of transmitted information, which structurally eliminates cleartext transmission of sensitive data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Setting the Secure attribute is a direct mechanism for protecting sensitive session data in transit over HTTPS.
Enforcing hardened configuration baselines includes requiring the Secure flag on sensitive cookies.
Secure SDLC practices explicitly require correct use of security attributes such as the cookie Secure flag.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Mandating cryptographic protection and stronger authentication on public networks stops the transmission of plaintext sensitive information.