{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-54972 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-54972 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-54972 is a low-severity vulnerability in Fortinet FortiMail, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-54972 and fix it if it is affected.\n\nWhat it is: CVE-2025-54972 is a low-severity vulnerability in Fortinet FortiMail, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-54972 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiMail. 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-2025-54972/ (Markdown: https://insights.sbomify.com/CVE-2025-54972/index.md)","id":"CVE-2025-54972","markdown":"https://insights.sbomify.com/CVE-2025-54972/index.md","name":"CVE-2025-54972","record":{"aliases":["GHSA-prjc-xc24-cv4p"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiMail","requires_auth":"none","summary":"Attackers can inject headers into responses via crafted links, potentially altering email handling or bypassing security controls in FortiMail.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortimail","vendor":"fortinet"}],"cvss":{"score":3.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"An improper neutralization of crlf sequences ('crlf injection') vulnerability in Fortinet FortiMail 7.6.0 through 7.6.3, FortiMail 7.4.0 through 7.4.5, FortiMail 7.2 all versions, FortiMail 7.0 all versions may allow an attacker to inject headers in the response via convincing a user to click on a specifically crafted link","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":"Other in FortiMail","id":"CVE-2025-54972","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in FortiAnalyzer","id":"CVE-2025-54973"},"packages":[],"prev":{"headline":"Information disclosure in FortiADC","id":"CVE-2025-54971"},"products":["FortiMail"],"published":"2025-11-18","related":[{"cvss_score":9.8,"headline":"Fortinet FortiMail Path Traversal","id":"CVE-2026-104286","kev_date_added":"2026-10-01","published":"2026-10-01"},{"cvss_score":9.8,"headline":"Auth bypass in Fortinet FortiMail","id":"CVE-2021-36166","kev_date_added":null,"published":"2022-03-01"},{"cvss_score":9.8,"headline":"SQL injection in Fortinet FortiMail","id":"CVE-2021-24007","kev_date_added":null,"published":"2021-07-09"},{"cvss_score":9.8,"headline":"Auth bypass in FortiMail","id":"CVE-2020-9294","kev_date_added":null,"published":"2020-04-27"},{"cvss_score":9,"headline":"Auth bypass in FortiMail","id":"CVE-2023-47539","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":8.8,"headline":"Path traversal in Fortinet FortiMail","id":"CVE-2021-24013","kev_date_added":null,"published":"2021-07-12"},{"cvss_score":8.8,"headline":"Memory corruption in Fortinet FortiMail","id":"CVE-2021-22129","kev_date_added":null,"published":"2021-07-09"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-14","vendors":["Fortinet"]},"summary":"Attackers can inject headers into responses via crafted links, potentially altering email handling or bypassing security controls in FortiMail.","url":"https://insights.sbomify.com/CVE-2025-54972/"}