{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46310 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46310 is a medium-severity cross-site scripting vulnerability in gVectors Team wpDiscuz, published on 4 Jun 2024. 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-46310 and fix it if it is affected.\n\nWhat it is: CVE-2023-46310 is a medium-severity cross-site scripting vulnerability in gVectors Team wpDiscuz, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-46310 in the wild and no public exploit code.\n\nAffected product: gVectors Team wpDiscuz. 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-46310/ (Markdown: https://insights.sbomify.com/CVE-2023-46310/index.md)","id":"CVE-2023-46310","markdown":"https://insights.sbomify.com/CVE-2023-46310/index.md","name":"CVE-2023-46310","record":{"aliases":["GHSA-69h4-r42q-6wmv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can inject malicious scripts into the wpDiscuz plugin, potentially executing code in the context of other users.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"wpdiscuz","vendor":"gvectors"}],"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-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"}],"description":"Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) vulnerability in gVectors Team wpDiscuz allows Code Injection.This issue affects wpDiscuz: from n/a through 7.6.10.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress wpDiscuz plugin \u003c= 7.6.10 - Content Injection vulnerability","id":"CVE-2023-46310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress wpDiscuz Plugin \u003c= 7.6.3 is vulnerable to Insecure Direct Object References (IDOR)","id":"CVE-2023-46311"},"packages":[],"prev":{"headline":"WordPress wpDiscuz plugin \u003c= 7.6.10 - Broken Access Control vulnerability","id":"CVE-2023-46309"},"products":["wpDiscuz"],"published":"2024-06-04","related":[{"cvss_score":10,"headline":"File upload in n/a","id":"CVE-2020-24186","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":9.8,"headline":"Comments – wpDiscuz \u003c= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider","id":"CVE-2024-9488","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-13640","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":9.2,"headline":"wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions()","id":"CVE-2026-22193","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.8,"headline":"Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage","id":"CVE-2026-22192","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.7,"headline":"wpDiscuz before 7.6.47 - Unauthenticated Email Notification Flood via wpdCheckNotificationType","id":"CVE-2026-22182","kev_date_added":null,"published":"2026-03-13"},{"cvss_score":8.7,"headline":"Voltronic Power SNMP Web Pro 1.1 Path Traversal via upload.cgi","id":"CVE-2026-22199","kev_date_added":null,"published":"2026-03-13"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["gVectors Team"]},"summary":"An attacker can inject malicious scripts into the wpDiscuz plugin, potentially executing code in the context of other users.","url":"https://insights.sbomify.com/CVE-2023-46310/"}