{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22853 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22853 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22853 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Feb 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-22853 and fix it if it is affected.\n\nWhat it is: CVE-2022-22853 is a medium-severity cross-site scripting vulnerability in n/a, published on 16 Feb 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-22853 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-22853/ (Markdown: https://insights.sbomify.com/CVE-2022-22853/index.md)","id":"CVE-2022-22853","markdown":"https://insights.sbomify.com/CVE-2022-22853/index.md","name":"CVE-2022-22853","record":{"aliases":["GHSA-q4rv-vj4r-gqx2"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Hospital Patient Record System","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary scripts via stored XSS in the Name field of the Hospital Patient Record Management System.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hospital\\'s_patient_records_management_system","vendor":"hospital\\'s_patient_records_management_system_project"}],"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":"A stored cross-site scripting (XSS) vulnerability in Hospital Patient Record Management System v1.0 allows attackers to execute arbitrary web scripts or HTML via a crafted payload inserted into the Name field.","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-2022-22853","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-22854"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-22852"},"products":["n/a"],"published":"2022-02-16","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-32337","kev_date_added":null,"published":"2022-06-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-32352","kev_date_added":null,"published":"2022-06-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-25003","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-25004","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2022-22854","kev_date_added":null,"published":"2022-02-14"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2022-24232","kev_date_added":null,"published":"2022-02-24"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2022-32338","kev_date_added":null,"published":"2022-06-14"}],"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 execute arbitrary scripts via stored XSS in the Name field of the Hospital Patient Record Management System.","url":"https://insights.sbomify.com/CVE-2022-22853/"}