{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43499 exists.","fix":"No fix has been published for CVE-2022-43499 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-43499 is a medium-severity cross-site scripting vulnerability in SHIRASAGI, published on 5 Dec 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-43499 and fix it if it is affected.\n\nWhat it is: CVE-2022-43499 is a medium-severity cross-site scripting vulnerability in SHIRASAGI, published on 5 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43499 exists.\n\nAffected product: SHIRASAGI. 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-43499/ (Markdown: https://insights.sbomify.com/CVE-2022-43499/index.md)","id":"CVE-2022-43499","markdown":"https://insights.sbomify.com/CVE-2022-43499/index.md","name":"CVE-2022-43499","record":{"aliases":["GHSA-j2c7-5g87-4vx7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SHIRASAGI CMS","requires_auth":"low_privilege","summary":"An authenticated administrator can inject arbitrary scripts into SHIRASAGI, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"shirasagi","vendor":"ss-proj"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","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":"Stored cross-site scripting vulnerability in SHIRASAGI versions prior to v1.16.2 allows a remote authenticated attacker with an administrative privilege to inject an arbitrary script.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site scripting in SHIRASAGI","id":"CVE-2022-43499","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in WordPress","id":"CVE-2022-43500"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2022-43498"},"products":["SHIRASAGI"],"published":"2022-12-05","related":[{"cvss_score":8.8,"headline":"Path traversal in SHIRASAGI","id":"CVE-2023-39448","kev_date_added":null,"published":"2023-09-05"},{"cvss_score":8.6,"headline":"Path traversal in SHIRASAGI","id":"CVE-2024-46898","kev_date_added":null,"published":"2024-10-15"},{"cvss_score":6.1,"headline":"Cross-site scripting in SHIRASAGI","id":"CVE-2023-36492","kev_date_added":null,"published":"2023-09-05"},{"cvss_score":6.1,"headline":"Open redirect in SHIRASAGI","id":"CVE-2022-43479","kev_date_added":null,"published":"2022-12-05"},{"cvss_score":6.1,"headline":"Cross-site scripting in SHIRASAGI","id":"CVE-2022-29485","kev_date_added":null,"published":"2022-06-14"},{"cvss_score":6.1,"headline":"Open redirect in SHIRASAGI","id":"CVE-2020-5607","kev_date_added":null,"published":"2020-07-10"},{"cvss_score":6.1,"headline":"Open redirect in SHIRASAGI","id":"CVE-2019-6009","kev_date_added":null,"published":"2019-09-12"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-24","vendors":["SHIRASAGI Project"]},"summary":"An authenticated administrator can inject arbitrary scripts into SHIRASAGI, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2022-43499/"}