{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-7166 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-7166 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-7166 is a low-severity cross-site scripting vulnerability in Xxyopen Novel-Plus, published on 29 Dec 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-7166 and fix it if it is affected.\n\nWhat it is: CVE-2023-7166 is a low-severity cross-site scripting vulnerability in Xxyopen Novel-Plus, published on 29 Dec 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-7166 in the wild and no public exploit code.\n\nAffected product: Xxyopen Novel-Plus. 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-7166/ (Markdown: https://insights.sbomify.com/CVE-2023-7166/index.md)","id":"CVE-2023-7166","markdown":"https://insights.sbomify.com/CVE-2023-7166/index.md","name":"CVE-2023-7166","record":{"aliases":["GHSA-3736-rg79-m6vq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Novel-Plus web app","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts via the nickName field in user profile updates, potentially executing code in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"novel-plus","vendor":"xxyopen"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A vulnerability classified as problematic has been found in Novel-Plus up to 4.2.0. This affects an unknown part of the file /user/updateUserInfo of the component HTTP POST Request Handler. The manipulation of the argument nickName leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of the patch is c62da9bb3a9b3603014d0edb436146512631100d. It is recommended to apply a patch to fix this issue. The identifier VDB-249201 was assigned to this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Novel-Plus HTTP POST Request updateUserInfo cross site scripting","id":"CVE-2023-7166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"xxyopen:novel-plus","products":["xxyopen:novel-plus"],"type":"xss","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Persian Fonts \u003c= 1.6 - Admin+ Stored XSS","id":"CVE-2023-7167"},"packages":[],"prev":{"headline":"JetBackup \u003c 2.0.9.9 - Directory Listing Exposing Backups","id":"CVE-2023-7165"},"products":["Novel-Plus"],"published":"2023-12-29","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2025-45890","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-25274","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-24014","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-24018","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-24021","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-24023","kev_date_added":null,"published":"2024-02-08"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-24024","kev_date_added":null,"published":"2024-02-08"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts via the nickName field in user profile updates, potentially executing code in victim browsers.","url":"https://insights.sbomify.com/CVE-2023-7166/"}