{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2001-1537 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2001-1537 yet. Limit exposure of the affected software until one is available.","what":"CVE-2001-1537 is a high-severity vulnerability in n/a, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2001-1537 and fix it if it is affected.\n\nWhat it is: CVE-2001-1537 is a high-severity vulnerability in n/a, published on 14 Jul 2005. 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-2001-1537 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2001-1537/ (Markdown: https://insights.sbomify.com/CVE-2001-1537/index.md)","id":"CVE-2001-1537","markdown":"https://insights.sbomify.com/CVE-2001-1537/index.md","name":"CVE-2001-1537","record":{"aliases":["GHSA-f465-339w-2vhm"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"TWIG webmail","requires_auth":"none","summary":"Default settings store cleartext credentials in cookies, allowing attackers to steal authentication information and gain unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"twig","vendor":"symfony"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"The default \"basic\" security setting' in config.php for TWIG webmail 2.7.4 and earlier stores cleartext usernames and passwords in cookies, which could allow attackers to obtain authentication information and gain privileges.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2001-1537","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2001"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2001-1538"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2001-1536"},"products":["n/a"],"published":"2005-07-14","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2018-13818","kev_date_added":null,"published":"2018-07-10"},{"cvss_score":8.7,"headline":"Twig: PHP code injection via `{% use %}` template name","id":"CVE-2026-46633","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.7,"headline":"Twig: Arbitrary PHP code execution via `_self.(\u003cstring\u003e)` macro-reference compilation","id":"CVE-2026-46640","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.7,"headline":"Twig 2.16.x \u0026 3.9.0-3.25.x Sandbox Bypass via SourcePolicyInterface","id":"CVE-2026-24425","kev_date_added":null,"published":"2026-05-20"},{"cvss_score":8.6,"headline":"Twig has a possible sandbox bypass","id":"CVE-2024-45411","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":7.7,"headline":"Twig: `template_from_string()` escapes a SourcePolicy-driven sandbox via synthesized template name","id":"CVE-2026-46634","kev_date_added":null,"published":"2026-07-14"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Default settings store cleartext credentials in cookies, allowing attackers to steal authentication information and gain unauthorized access.","url":"https://insights.sbomify.com/CVE-2001-1537/"}