{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10718 exists.","fix":"No fix has been published for CVE-2024-10718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-10718 is a medium-severity vulnerability in Phpipam Phpipam, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-10718 and fix it if it is affected.\n\nWhat it is: CVE-2024-10718 is a medium-severity vulnerability in Phpipam Phpipam, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-10718 exists.\n\nAffected product: Phpipam Phpipam. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-10718/ (Markdown: https://insights.sbomify.com/CVE-2024-10718/index.md)","id":"CVE-2024-10718","markdown":"https://insights.sbomify.com/CVE-2024-10718/index.md","name":"CVE-2024-10718","record":{"aliases":["GHSA-mj67-2mvx-f778"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IPAM web application","requires_auth":"none","summary":"Attackers can intercept sensitive session cookies transmitted over unencrypted HTTP connections, leading to potential session hijacking or data exposure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"phpipam","vendor":"phpipam"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-614","name":"Sensitive Cookie in HTTPS Session Without 'Secure' Attribute"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cookie without Secure attribute in phpipam/phpipam","id":"CVE-2024-10718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"phpipam:phpipam","products":["phpipam:phpipam"],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Stored Cross-site Scripting (XSS) in phpipam/phpipam","id":"CVE-2024-10719"},"packages":[],"prev":{"headline":"Styler for Ninja Forms \u003c= 3.3.4 - Authenticated (Subscriber+) Arbitrary Option Deletion via deactivate_license","id":"CVE-2024-10717"},"products":["phpipam/phpipam"],"published":"2025-03-20","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2022-41443","kev_date_added":null,"published":"2022-10-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16692","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16693","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16694","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16695","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-16696","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-1000869","kev_date_added":null,"published":"2018-12-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-20","vendors":["phpipam"]},"summary":"Attackers can intercept sensitive session cookies transmitted over unencrypted HTTP connections, leading to potential session hijacking or data exposure.","url":"https://insights.sbomify.com/CVE-2024-10718/"}