{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53840 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53840 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53840 is a low-severity vulnerability in icingadb-web, published on 16 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-53840 and fix it if it is affected.\n\nWhat it is: CVE-2025-53840 is a low-severity vulnerability in icingadb-web, published on 16 Jul 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-53840 in the wild and no public exploit code.\n\nAffected product: icingadb-web. 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-53840/ (Markdown: https://insights.sbomify.com/CVE-2025-53840/index.md)","id":"CVE-2025-53840","markdown":"https://insights.sbomify.com/CVE-2025-53840/index.md","name":"CVE-2025-53840","record":{"aliases":["GHSA-q2w7-mrx8-5473"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Icinga DB Web","requires_auth":"high_privilege","summary":"Unauthorized users can view restricted host and service names in dependency maps due to improper filtering, exposing sensitive monitoring data.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icinga_db_web","vendor":"icinga"}],"cvss":{"score":2.4,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Icinga DB Web provides a graphical interface for Icinga monitoring. Starting in version 1.2.0 and prior to version 1.2.2, users with access to Icinga Dependency Views, are allowed to see hosts and services that they weren't meant to on the dependency map. However, the name of an object will not be revealed nor does this grant access to a host's or service's detail view. Please note that this only affects the restrictions `filter/hosts` and `filter/services`. `filter/objects` is not affected by this and restricts objects as it is supposed to. Version 1.2.2 applies these restrictions properly. As a workaround, one may downgrade to version 1.1.3.","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":"Icinga DB Web Exposure of Sensitive Information to an Unauthorized Actor vulnerability","id":"CVE-2025-53840","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Guardicore Platform Agent","id":"CVE-2025-53841"},"packages":[],"prev":{"headline":"DRACOON Branding Service vulnerable to Cross-site Scripting","id":"CVE-2025-53839"},"products":["icingadb-web"],"published":"2025-07-16","related":[{"cvss_score":5.3,"headline":"Icinga DB Web hidden/protected custom variables are prone to filter enumeration","id":"CVE-2025-61789","kev_date_added":null,"published":"2025-10-16"}],"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":"2025-07-18","vendors":["Icinga"]},"summary":"Unauthorized users can view restricted host and service names in dependency maps due to improper filtering, exposing sensitive monitoring data.","url":"https://insights.sbomify.com/CVE-2025-53840/"}