{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-25256 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-25256 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-25256 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Feb 2022. 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-2022-25256 and fix it if it is affected.\n\nWhat it is: CVE-2022-25256 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Feb 2022. 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-2022-25256 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-2022-25256/ (Markdown: https://insights.sbomify.com/CVE-2022-25256/index.md)","id":"CVE-2022-25256","markdown":"https://insights.sbomify.com/CVE-2022-25256/index.md","name":"CVE-2022-25256","record":{"aliases":["GHSA-f94m-q2w2-2g64"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SAS Web Report Studio","requires_auth":"none","summary":"Cross-site scripting in SAS Web Report Studio allows attackers to execute arbitrary JavaScript via malicious URL parameters, potentially leading to session hijacking.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"web_report_studio","vendor":"sas"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/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":"SAS Web Report Studio 4.4 allows XSS. /SASWebReportStudio/logonAndRender.do has two parameters: saspfs_request_backlabel_list and saspfs_request_backurl_list. The first one affects the content of the button placed in the top left. The second affects the page to which the user is directed after pressing the button, e.g., a malicious web page. In addition, the second parameter executes JavaScript, which means XSS is possible by adding a javascript: URL.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2022-03-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-03-07T10:18:41Z","kind":"github_poc","ref":"https://github.com/RobertDra/CVE-2022-25256","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2022-25256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Null dereference in n/a","id":"CVE-2022-25258"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2022-25255"},"products":["n/a"],"published":"2022-02-19","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Cross-site scripting in SAS Web Report Studio allows attackers to execute arbitrary JavaScript via malicious URL parameters, potentially leading to session hijacking.","url":"https://insights.sbomify.com/CVE-2022-25256/"}