{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-26596 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-26596 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-26596 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Mar 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-26596 and fix it if it is affected.\n\nWhat it is: CVE-2021-26596 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Mar 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-26596 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-2021-26596/ (Markdown: https://insights.sbomify.com/CVE-2021-26596/index.md)","id":"CVE-2021-26596","markdown":"https://insights.sbomify.com/CVE-2021-26596/index.md","name":"CVE-2021-26596","record":{"aliases":["GHSA-3fmq-prxr-gqfw"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Nokia NetAct","requires_auth":"low_privilege","summary":"Attackers can inject JavaScript via filename parameters in Nokia NetAct, leading to script execution in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"netact","vendor":"nokia"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"An issue was discovered in Nokia NetAct 18A. A malicious user can change a filename of an uploaded file to include JavaScript code, which is then stored and executed by a victim's web browser. The most common mechanism for delivering malicious content is to include it as a parameter in a URL that is posted publicly or e-mailed directly to victims. Here, the /netact/sct filename parameter is used.","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 scripting in n/a","id":"CVE-2021-26596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2021-26597"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2021-26595"},"products":["n/a"],"published":"2021-03-25","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2022-28863","kev_date_added":null,"published":"2023-07-24"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2022-28864","kev_date_added":null,"published":"2023-07-24"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-30280","kev_date_added":null,"published":"2023-07-24"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2023-26059","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2023-26060","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2023-26061","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":6.5,"headline":"XML external entity in n/a","id":"CVE-2023-26057","kev_date_added":null,"published":"2023-04-25"}],"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-03","vendors":["n/a"]},"summary":"Attackers can inject JavaScript via filename parameters in Nokia NetAct, leading to script execution in victim browsers.","url":"https://insights.sbomify.com/CVE-2021-26596/"}