{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16157 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16157 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16157 is a medium-severity vulnerability in Fortinet Fortiweb, published on 13 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16157 and fix it if it is affected.\n\nWhat it is: CVE-2019-16157 is a medium-severity vulnerability in Fortinet Fortiweb, published on 13 Mar 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-16157 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortiweb. 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-2019-16157/ (Markdown: https://insights.sbomify.com/CVE-2019-16157/index.md)","id":"CVE-2019-16157","markdown":"https://insights.sbomify.com/CVE-2019-16157/index.md","name":"CVE-2019-16157","record":{"aliases":["GHSA-jxwq-w6v2-6v7q"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiWeb","requires_auth":"low_privilege","summary":"Authenticated users can view sensitive information in logs via diagnose debug commands in Fortinet FortiWeb.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiweb","vendor":"fortinet"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An information exposure vulnerability in Fortinet FortiWeb 6.2.0 CLI and earlier may allow an authenticated user to view sensitive information being logged via diagnose debug commands.","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 Fortinet FortiWeb","id":"CVE-2019-16157","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortiweb","products":["fortinet:fortiweb"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-16159"},"packages":[],"prev":{"headline":"Cross-site scripting in Fortinet FortiWeb","id":"CVE-2019-16156"},"products":["Fortinet FortiWeb"],"published":"2020-03-13","related":[{"cvss_score":9.6,"headline":"Fortinet FortiWeb SQL Injection","id":"CVE-2025-25257","kev_date_added":"2025-07-18","published":"2025-07-17"},{"cvss_score":9.4,"headline":"Fortinet FortiWeb Path Traversal","id":"CVE-2025-64446","kev_date_added":"2025-11-14","published":"2025-11-14"},{"cvss_score":6.7,"headline":"Fortinet FortiWeb OS Command Injection","id":"CVE-2025-58034","kev_date_added":"2025-11-18","published":"2025-11-18"},{"cvss_score":9.8,"headline":"SQL injection in Fortinet FortiWeb","id":"CVE-2020-29015","kev_date_added":null,"published":"2021-01-14"},{"cvss_score":9.8,"headline":"Memory corruption in Fortinet FortiWeb","id":"CVE-2020-29016","kev_date_added":null,"published":"2021-01-14"},{"cvss_score":9.3,"headline":"Memory corruption in FortiWeb","id":"CVE-2021-42756","kev_date_added":null,"published":"2023-02-16"},{"cvss_score":9.1,"headline":"Auth bypass in FortiWeb","id":"CVE-2025-59719","kev_date_added":null,"published":"2025-12-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":"2024-10-25","vendors":["Fortinet"]},"summary":"Authenticated users can view sensitive information in logs via diagnose debug commands in Fortinet FortiWeb.","url":"https://insights.sbomify.com/CVE-2019-16157/"}