{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-31862 exists.","fix":"No fix has been published for CVE-2023-31862 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31862 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 May 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-31862 and fix it if it is affected.\n\nWhat it is: CVE-2023-31862 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 May 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-31862 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-31862/ (Markdown: https://insights.sbomify.com/CVE-2023-31862/index.md)","id":"CVE-2023-31862","markdown":"https://insights.sbomify.com/CVE-2023-31862/index.md","name":"CVE-2023-31862","record":{"aliases":["GHSA-g4xp-6mr2-c9p8"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"jizhicms CMS","requires_auth":"low_privilege","summary":"Attackers can inject malicious JavaScript into published articles due to missing backend filtering, potentially leading to code execution or account takeover.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jizhicms","vendor":"jizhicms"}],"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":"jizhicms v2.4.6 is vulnerable to Cross Site Scripting (XSS). The content of the article published in the front end is only filtered in the front end, without being filtered in the background, which allows attackers to publish an article containing malicious JavaScript scripts by modifying the request package.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2023-31862","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2023-31867"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-31861"},"products":["n/a"],"published":"2023-05-19","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-50229","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-25784","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-32161","kev_date_added":null,"published":"2024-04-17"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2023-51154","kev_date_added":null,"published":"2024-01-04"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-36484","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36578","kev_date_added":null,"published":"2022-08-19"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-27429","kev_date_added":null,"published":"2022-04-25"}],"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-01-21","vendors":["n/a"]},"summary":"Attackers can inject malicious JavaScript into published articles due to missing backend filtering, potentially leading to code execution or account takeover.","url":"https://insights.sbomify.com/CVE-2023-31862/"}