{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-28448 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-28448 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28448 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2022. 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-2022-28448 and fix it if it is affected.\n\nWhat it is: CVE-2022-28448 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Apr 2022. 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-2022-28448 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-28448/ (Markdown: https://insights.sbomify.com/CVE-2022-28448/index.md)","id":"CVE-2022-28448","markdown":"https://insights.sbomify.com/CVE-2022-28448/index.md","name":"CVE-2022-28448","record":{"aliases":["GHSA-r3cc-j9xh-27gw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"nopCommerce e-commerce","requires_auth":"low_privilege","summary":"An authenticated customer can inject JavaScript into name fields, potentially leading to session hijacking or malicious actions against other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nopcommerce","vendor":"nopcommerce"}],"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":"nopCommerce 4.50.1 is vulnerable to Cross Site Scripting (XSS). An attacker (role customer) can inject javascript code to First name or Last name at Customer Info.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in n/a","id":"CVE-2022-28448","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-28449"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2022-28445"},"products":["n/a"],"published":"2022-04-26","related":[{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2019-19683","kev_date_added":null,"published":"2019-12-09"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-65593","kev_date_added":null,"published":"2025-12-16"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2019-19684","kev_date_added":null,"published":"2019-12-09"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-19685","kev_date_added":null,"published":"2019-12-09"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2022-33077","kev_date_added":null,"published":"2022-10-19"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2022-28451","kev_date_added":null,"published":"2022-05-01"},{"cvss_score":7.1,"headline":"CVE-2025-11699","id":"CVE-2025-11699","kev_date_added":null,"published":"2025-12-01"}],"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":"An authenticated customer can inject JavaScript into name fields, potentially leading to session hijacking or malicious actions against other users.","url":"https://insights.sbomify.com/CVE-2022-28448/"}