{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43479 exists.","fix":"No fix has been published for CVE-2022-43479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-43479 is a medium-severity vulnerability in SHIRASAGI, published on 5 Dec 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-43479 and fix it if it is affected.\n\nWhat it is: CVE-2022-43479 is a medium-severity vulnerability in SHIRASAGI, published on 5 Dec 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-43479 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-43479/ (Markdown: https://insights.sbomify.com/CVE-2022-43479/index.md)","id":"CVE-2022-43479","markdown":"https://insights.sbomify.com/CVE-2022-43479/index.md","name":"CVE-2022-43479","record":{"aliases":["GHSA-5vx9-xqhh-f79w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SHIRASAGI CMS","requires_auth":"none","summary":"Remote attackers can redirect users to malicious sites for phishing, affecting SHIRASAGI CMS users.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"shirasagi","vendor":"ss-proj"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","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-601","name":"URL Redirection to Untrusted Site"}],"description":"Open redirect vulnerability in SHIRASAGI v1.14.4 to v1.15.0 allows a remote unauthenticated attacker to redirect users to an arbitrary web site and conduct a phishing attack.","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":"Open redirect in SHIRASAGI","id":"CVE-2022-43479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"WordPress Homepage Pop-up Plugin \u003c= 1.2.5 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2022-43480"},"packages":[],"prev":{"headline":"Information disclosure in Intel Unison software","id":"CVE-2022-43477"},"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":"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":"Remote attackers can redirect users to malicious sites for phishing, affecting SHIRASAGI CMS users.","url":"https://insights.sbomify.com/CVE-2022-43479/"}