{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41889 exists.","fix":"No fix has been published for CVE-2023-41889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-41889 is a medium-severity vulnerability in shirasagi, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41889 and fix it if it is affected.\n\nWhat it is: CVE-2023-41889 is a medium-severity vulnerability in shirasagi, published on 15 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-41889 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-2023-41889/ (Markdown: https://insights.sbomify.com/CVE-2023-41889/index.md)","id":"CVE-2023-41889","markdown":"https://insights.sbomify.com/CVE-2023-41889/index.md","name":"CVE-2023-41889","record":{"aliases":["GHSA-xr45-c2jv-2v9r"],"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":"Attackers can bypass security checks in SHIRASAGI CMS by exploiting late Unicode normalization, allowing malicious inputs to pass validation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"shirasagi","vendor":"ss-proj"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"},{"id":"CWE-176","name":"Improper Handling of Unicode Encoding"}],"description":"SHIRASAGI is a Content Management System. Prior to version 1.18.0, SHIRASAGI is vulnerable to a Post-Unicode normalization issue. This happens when a logical validation or a security check is performed before a Unicode normalization. The Unicode character equivalent of a character would resurface after the normalization. The fix is initially performing the Unicode normalization and then strip for all whitespaces and then checking for a blank string. This issue has been fixed in version 1.18.0.","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":"Late-Unicode normalization vulnerability in SHIRASAGI","id":"CVE-2023-41889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Sustainsys.Saml2 Insufficient Identity Provider Issuer Validation","id":"CVE-2023-41890"},"packages":[],"prev":{"headline":"Phishing through a login page malicious URL in GLPI","id":"CVE-2023-41888"},"products":["shirasagi"],"published":"2023-09-15","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-25","vendors":["shirasagi"]},"summary":"Attackers can bypass security checks in SHIRASAGI CMS by exploiting late Unicode normalization, allowing malicious inputs to pass validation.","url":"https://insights.sbomify.com/CVE-2023-41889/"}