CVE-2024-10718
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 in version 1.7.0.
Scoring
- Severity
- MEDIUM
- CVSS base score
- 5.3
- CVSS vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS probability
- 0.33%
- CWE
- CWE-614
- Published
- 2025-03-20
- Last modified
- 2026-03-13
Affected products
- phpipam phpipam/phpipam
Weakness type
Related vulnerabilities
- CVE-2026-65655 — Temporal UI Server may set OAuth credential cookies without Secure behind a TLS-terminating reverse proxy
- CVE-2026-15656 — IBM MAS uses axios-1.15.2, protobufjs-8.0.1 and undici-7.26 which is vulnerable to multiple CVEs, and contains vulnerabilities related to missing Secure attribute on mas-redirect-uri cookie and weak HMAC Session Secret
- CVE-2026-48058 — nebula-mesh: Session and OIDC state cookies lack the Secure attribute
- CVE-2026-56581 — HCL MyCloud was affected with Cookie Attribute Path Not Set
- CVE-2024-23572 — HCL Aftermarket EPC is vulnerable to attack as cookie appears to contain a session token, which may...
- CVE-2026-57948 — Pinpoint - Insecure Session Cookie Attributes in pinpointJwt
- CVE-2026-46550 — NocoDB: Refresh Token Cookie Set Without `Secure` and `SameSite` Flags
- CVE-2026-53661 — boruta-server sent sensitive session cookies without the Secure attribute