{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16977 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16977 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16977 is a medium-severity vulnerability in n/a, published on 12 Sep 2018. 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-16977 and fix it if it is affected.\n\nWhat it is: CVE-2018-16977 is a medium-severity vulnerability in n/a, published on 12 Sep 2018. 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-16977 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-2018-16977/ (Markdown: https://insights.sbomify.com/CVE-2018-16977/index.md)","id":"CVE-2018-16977","markdown":"https://insights.sbomify.com/CVE-2018-16977/index.md","name":"CVE-2018-16977","record":{"aliases":["GHSA-87h5-4h68-r79h"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Monstra CMS","requires_auth":"none","summary":"Monstra CMS exposes sensitive server configuration details like paths and admin emails in error messages, allowing attackers to gather reconnaissance data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"monstra","vendor":"monstra"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Monstra CMS V3.0.4 has an information leakage risk (e.g., PATH, DOCUMENT_ROOT, and SERVER_ADMIN) in libraries/Gelato/ErrorHandler/Resources/Views/Errors/exception.php.","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":"Information disclosure in n/a","id":"CVE-2018-16977","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-16978"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2018-16976"},"products":["n/a"],"published":"2018-09-12","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-40940","kev_date_added":null,"published":"2022-06-15"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2021-36548","kev_date_added":null,"published":"2021-10-28"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-25414","kev_date_added":null,"published":"2021-06-17"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-13384","kev_date_added":null,"published":"2020-05-22"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2018-16608","kev_date_added":null,"published":"2018-09-10"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-9037","kev_date_added":null,"published":"2018-04-10"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-6383","kev_date_added":null,"published":"2018-01-29"}],"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-09-16","vendors":["n/a"]},"summary":"Monstra CMS exposes sensitive server configuration details like paths and admin emails in error messages, allowing attackers to gather reconnaissance data.","url":"https://insights.sbomify.com/CVE-2018-16977/"}