{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-47869 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-47869 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-47869 is a medium-severity cross-site scripting vulnerability in gVectors Team wpForo Forum, published on 9 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-47869 and fix it if it is affected.\n\nWhat it is: CVE-2023-47869 is a medium-severity cross-site scripting vulnerability in gVectors Team wpForo Forum, published on 9 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-47869 in the wild and no public exploit code.\n\nAffected product: gVectors Team wpForo Forum. 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-47869/ (Markdown: https://insights.sbomify.com/CVE-2023-47869/index.md)","id":"CVE-2023-47869","markdown":"https://insights.sbomify.com/CVE-2023-47869/index.md","name":"CVE-2023-47869","record":{"aliases":["GHSA-4qgc-h55q-cm8r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts via XSS in the wpForo Forum plugin, potentially leading to code execution and bypassing access controls.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"wpforo_forum","vendor":"gvectors"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 wpForo Forum allows Code Injection.This issue affects wpForo Forum: from n/a through 2.2.5.","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 wpForo plugin \u003c= 2.2.5 - Broken Access Control + CSRF vulnerability","id":"CVE-2023-47869","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 wpForo Forum Plugin \u003c= 2.2.6 is vulnerable to Broken Access Control and Cross Site Request Forgery (CSRF)","id":"CVE-2023-47870"},"packages":[],"prev":{"headline":"WordPress wpForo plugin \u003c= 2.2.3 - Privilege Escalation vulnerability","id":"CVE-2023-47868"},"products":["wpForo Forum"],"published":"2024-12-09","related":[{"cvss_score":9.9,"headline":"wpForo Forum \u003c= 2.3.3 - Authenticated (Contributor+) SQL Injection","id":"CVE-2024-3200","kev_date_added":null,"published":"2024-06-01"},{"cvss_score":9.9,"headline":"WordPress wpForo Forum plugin \u003c= 2.0.9 - Auth. Arbitrary File Upload vulnerability","id":"CVE-2022-40200","kev_date_added":null,"published":"2022-11-17"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-16613","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":8.8,"headline":"wpForo Forum 2.4.14 SQL Injection via Topics ORDER BY Parameter","id":"CVE-2026-28562","kev_date_added":null,"published":"2026-02-28"},{"cvss_score":8.8,"headline":"Server-side request forgery in wpForo Forum","id":"CVE-2023-2249","kev_date_added":null,"published":"2023-06-09"},{"cvss_score":8.8,"headline":"WordPress wpForo Forum plugin \u003c= 2.0.5 - Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2022-38144","kev_date_added":null,"published":"2022-09-09"},{"cvss_score":7.5,"headline":"WordPress wpForo Forum plugin \u003c= 2.3.4 - Unauthenticated Sensitive Data Exposure vulnerability","id":"CVE-2024-43289","kev_date_added":null,"published":"2024-08-26"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["gVectors Team"]},"summary":"Attackers can inject malicious scripts via XSS in the wpForo Forum plugin, potentially leading to code execution and bypassing access controls.","url":"https://insights.sbomify.com/CVE-2023-47869/"}