{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59784 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59784 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59784 is a medium-severity vulnerability in 2N Access Commander, published on 4 Mar 2026. 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-59784 and fix it if it is affected.\n\nWhat it is: CVE-2025-59784 is a medium-severity vulnerability in 2N Access Commander, published on 4 Mar 2026. 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-59784 in the wild and no public exploit code.\n\nAffected product: 2N Access Commander. 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-59784/ (Markdown: https://insights.sbomify.com/CVE-2025-59784/index.md)","id":"CVE-2025-59784","markdown":"https://insights.sbomify.com/CVE-2025-59784/index.md","name":"CVE-2025-59784","record":{"aliases":["GHSA-whr8-xqgw-9f74"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Access control system","requires_auth":"none","summary":"Authenticated administrators can inject control characters into logs via API parameters, potentially corrupting log integrity.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"2N","cpe":[{"product":"access_commander","vendor":"2n"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"2N Access Commander version 3.4.1 and prior is vulnerable to log pollution. Certain parameters sent over API may be included in the logs without prior validation or sanitisation.\nThis vulnerability can only be exploited after authenticating with administrator privileges.","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":"Log Pollution - Control Characters Not Escaped","id":"CVE-2025-59784","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"API - Insufficient Input Validation","id":"CVE-2025-59785"},"packages":[],"prev":{"headline":"OS Command Injection over API","id":"CVE-2025-59783"},"products":["2N Access Commander"],"published":"2026-03-04","related":[{"cvss_score":8.8,"headline":"OS Command Injection over API","id":"CVE-2025-59783","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.2,"headline":"Path traversal in 2N Access Commander","id":"CVE-2024-47253","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":6.3,"headline":"Privilege escalation in 2N Access Commander","id":"CVE-2024-47254","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":6,"headline":"Cookies are not Invalidated upon Logout and Password Change","id":"CVE-2025-59786","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":5.3,"headline":"API - Insufficient Input Validation","id":"CVE-2025-59785","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":5.3,"headline":"HTTP 5XX Internal Server Errors","id":"CVE-2025-59787","kev_date_added":null,"published":"2026-03-04"}],"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":"2026-03-04","vendors":["2N Telekomunikace a.s."]},"summary":"Authenticated administrators can inject control characters into logs via API parameters, potentially corrupting log integrity.","url":"https://insights.sbomify.com/CVE-2025-59784/"}