{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2018-19525 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19525 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19525 is a medium-severity vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-19525 and fix it if it is affected.\n\nWhat it is: CVE-2018-19525 is a medium-severity vulnerability in n/a, published on 17 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-19525 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-19525/ (Markdown: https://insights.sbomify.com/CVE-2018-19525/index.md)","id":"CVE-2018-19525","markdown":"https://insights.sbomify.com/CVE-2018-19525/index.md","name":"CVE-2018-19525","record":{"aliases":["GHSA-jr59-m722-rvrv"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Systrome ISG firewall","requires_auth":"none","summary":"Attackers can exploit CSRF to inject XSS payloads on Systrome ISG devices, potentially executing code or bypassing security controls.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cumilon_isg-600c_firmware","vendor":"systrome"},{"product":"cumilon_isg-600h_firmware","vendor":"systrome"},{"product":"cumilon_isg-800w_firmware","vendor":"systrome"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An issue was discovered on Systrome ISG-600C, ISG-600H, and ISG-800W 1.1-R2.1_TRUNK-20180914.bin devices. There is CSRF via /ui/?g=obj_keywords_add and /ui/?g=obj_keywords_addsave with resultant XSS because of a lack of csrf token validation.","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":"Cross-site request forgery in n/a","id":"CVE-2018-19525","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19527"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-19524"},"products":["n/a"],"published":"2019-03-17","related":[{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2019-7383","kev_date_added":null,"published":"2019-03-17"}],"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-08-05","vendors":["n/a"]},"summary":"Attackers can exploit CSRF to inject XSS payloads on Systrome ISG devices, potentially executing code or bypassing security controls.","url":"https://insights.sbomify.com/CVE-2018-19525/"}