{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46467 exists.","fix":"No fix has been published for CVE-2023-46467 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46467 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Oct 2023. 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-2023-46467 and fix it if it is affected.\n\nWhat it is: CVE-2023-46467 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Oct 2023. 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-2023-46467 exists.\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-2023-46467/ (Markdown: https://insights.sbomify.com/CVE-2023-46467/index.md)","id":"CVE-2023-46467","markdown":"https://insights.sbomify.com/CVE-2023-46467/index.md","name":"CVE-2023-46467","record":{"aliases":["GHSA-34fg-whr2-93rc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"juzawebCMS","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary code via a crafted payload in the registration username field of juzawebCMS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cms","vendor":"juzaweb"}],"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":"Cross Site Scripting vulnerability in juzawebCMS v.3.4 and before allows a remote attacker to execute arbitrary code via a crafted payload to the username parameter of the registration page.","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 n/a","id":"CVE-2023-46467","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"juzawebCMS Injection vulnerability","id":"CVE-2023-46468"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2023-46456"},"products":["n/a"],"published":"2023-10-28","related":[{"cvss_score":5.3,"headline":"juzaweb CMS Import Page imports improper authorization","id":"CVE-2025-6735","kev_date_added":null,"published":"2025-06-26"},{"cvss_score":5.3,"headline":"juzaweb CMS Add New Themes Page install improper authorization","id":"CVE-2025-6736","kev_date_added":null,"published":"2025-06-26"},{"cvss_score":5.3,"headline":"juzaweb CMS Plugin Editor Page editor access control","id":"CVE-2025-5421","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":5.3,"headline":"juzaweb CMS Email Logs Page email access control","id":"CVE-2025-5422","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":5.3,"headline":"juzaweb CMS General Setting Page general access control","id":"CVE-2025-5423","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":5.3,"headline":"juzaweb CMS Media Page media access control","id":"CVE-2025-5424","kev_date_added":null,"published":"2025-06-02"}],"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":"2024-09-09","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via a crafted payload in the registration username field of juzawebCMS.","url":"https://insights.sbomify.com/CVE-2023-46467/"}