{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-49187 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-49187 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49187 is a medium-severity vulnerability in SICK Field Analytics, published on 12 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-49187 and fix it if it is affected.\n\nWhat it is: CVE-2025-49187 is a medium-severity vulnerability in SICK Field Analytics, published on 12 Jun 2025. 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-2025-49187 in the wild and no public exploit code.\n\nAffected product: SICK Field Analytics. 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-49187/ (Markdown: https://insights.sbomify.com/CVE-2025-49187/index.md)","id":"CVE-2025-49187","markdown":"https://insights.sbomify.com/CVE-2025-49187/index.md","name":"CVE-2025-49187","record":{"aliases":["GHSA-26xj-r8r2-vvgx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SICK Field Analytics","requires_auth":"none","summary":"Attackers can enumerate valid usernames by observing distinct error messages for failed login attempts in SICK Field Analytics.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SICK AG","cpe":[{"product":"field_analytics","vendor":"sick"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"For failed login attempts, the application returns different error messages depending on whether the login failed due to an incorrect password or a non-existing username. This allows an attacker to guess usernames until they find an existing one.","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":"User enumeration","id":"CVE-2025-49187","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Sensitive Data in URL","id":"CVE-2025-49188"},"packages":[],"prev":{"headline":"No brute-force protection","id":"CVE-2025-49186"},"products":["SICK Field Analytics"],"published":"2025-06-12","related":[{"cvss_score":8.8,"headline":"Backup files can be modified and uploaded","id":"CVE-2025-49199","kev_date_added":null,"published":"2025-06-12"},{"cvss_score":6.5,"headline":"Deprecated TLS version supported","id":"CVE-2025-49196","kev_date_added":null,"published":"2025-06-12"},{"cvss_score":6.5,"headline":"Unencrypted backup contains sensitive information","id":"CVE-2025-49200","kev_date_added":null,"published":"2025-06-12"},{"cvss_score":5.5,"headline":"Stored Cross-Site-Script","id":"CVE-2025-49185","kev_date_added":null,"published":"2025-06-12"},{"cvss_score":5.3,"headline":"Sensitive Data in URL","id":"CVE-2025-49188","kev_date_added":null,"published":"2025-06-12"},{"cvss_score":4.8,"headline":"Dashboards and iFrames can link malicious web content","id":"CVE-2025-49191","kev_date_added":null,"published":"2025-06-12"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-12","vendors":["SICK AG"]},"summary":"Attackers can enumerate valid usernames by observing distinct error messages for failed login attempts in SICK Field Analytics.","url":"https://insights.sbomify.com/CVE-2025-49187/"}