{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-11709 exists.","fix":"No fix has been published for CVE-2018-11709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11709 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-11709 and fix it if it is affected.\n\nWhat it is: CVE-2018-11709 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Jun 2018. An attacker can exploit it over the internet without logging in, 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-2018-11709 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-2018-11709/ (Markdown: https://insights.sbomify.com/CVE-2018-11709/index.md)","id":"CVE-2018-11709","markdown":"https://insights.sbomify.com/CVE-2018-11709/index.md","name":"CVE-2018-11709","record":{"aliases":["GHSA-5w83-cxc7-jm5w"],"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":"Unauthenticated attackers can execute arbitrary scripts in victim browsers via reflected XSS in the wpForo Forum plugin for WordPress.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wpforo_forum","vendor":"gvectors"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"wpforo_get_request_uri in wpf-includes/functions.php in the wpForo Forum plugin before 1.4.12 for WordPress allows Unauthenticated Reflected Cross-Site Scripting (XSS) via the URI.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2018/CVE-2018-11709.yaml","stars":null,"title":"WordPress wpForo Forum \u003c= 1.4.11 - Cross-Site Scripting"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2018-11709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-11710"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-11707"},"products":["n/a"],"published":"2018-06-04","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Unauthenticated attackers can execute arbitrary scripts in victim browsers via reflected XSS in the wpForo Forum plugin for WordPress.","url":"https://insights.sbomify.com/CVE-2018-11709/"}