{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-25160 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-25160 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-25160 is a medium-severity code injection vulnerability in TOKUHIROM HTTP::Session2, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-25160 and fix it if it is affected.\n\nWhat it is: CVE-2018-25160 is a medium-severity code injection vulnerability in TOKUHIROM HTTP::Session2, published on 27 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-25160 in the wild and no public exploit code.\n\nAffected product: TOKUHIROM HTTP::Session2. 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-2018-25160/ (Markdown: https://insights.sbomify.com/CVE-2018-25160/index.md)","id":"CVE-2018-25160","markdown":"https://insights.sbomify.com/CVE-2018-25160/index.md","name":"CVE-2018-25160","record":{"aliases":["GHSA-hg4g-pqvm-c557"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Perl session library","requires_auth":"none","summary":"Attackers can inject code via session IDs in HTTP::Session2 if the backend allows it, requiring specific session storage configurations.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"http\\","vendor":"tokuhirom"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"HTTP::Session2 versions through 1.09 for Perl does not validate the format of user provided session ids, enabling code injection or other impact depending on session backend.\n\nFor example, if an application uses memcached for session storage, then it may be possible for a remote attacker to inject memcached commands in the session id value.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in HTTP::Session2","id":"CVE-2018-25160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Warranty Tracking System 11.06.3 SQL Injection via SearchCustomer.php","id":"CVE-2018-25161"},"packages":[],"prev":{"headline":"Epross AVCON6 OGNL Remote Code Execution via login.action","id":"CVE-2018-25159"},"products":["HTTP::Session2"],"published":"2026-02-27","related":[{"cvss_score":6.5,"headline":"HTTP::Session2 versions before 1.12 for Perl may generate weak session ids using the rand() function","id":"CVE-2026-3255","kev_date_added":null,"published":"2026-02-27"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-03","vendors":["TOKUHIROM"]},"summary":"Attackers can inject code via session IDs in HTTP::Session2 if the backend allows it, requiring specific session storage configurations.","url":"https://insights.sbomify.com/CVE-2018-25160/"}