{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-28561 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-28561 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28561 is a medium-severity cross-site scripting vulnerability in gVectors Team wpForo Forum, published on 28 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-28561 and fix it if it is affected.\n\nWhat it is: CVE-2026-28561 is a medium-severity cross-site scripting vulnerability in gVectors Team wpForo Forum, published on 28 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-28561 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-2026-28561/ (Markdown: https://insights.sbomify.com/CVE-2026-28561/index.md)","id":"CVE-2026-28561","markdown":"https://insights.sbomify.com/CVE-2026-28561/index.md","name":"CVE-2026-28561","record":{"aliases":["GHSA-4595-c58r-mv75"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Administrators can inject persistent JavaScript via forum descriptions, allowing attackers to execute code in victim browsers.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"wpforo_forum","vendor":"gvectors"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"wpForo Forum 2.4.14 contains a stored cross-site scripting vulnerability that allows administrators to inject persistent JavaScript via forum description fields echoed without output escaping across multiple theme template files. On multisite installations or with a compromised admin account, attackers set a forum description containing HTML event handlers that execute when any user views the forum listing.","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":"wpForo Forum 2.4.14 Stored XSS via Unescaped Forum Description in Templates","id":"CVE-2026-28561","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wpForo Forum 2.4.14 SQL Injection via Topics ORDER BY Parameter","id":"CVE-2026-28562"},"packages":[],"prev":{"headline":"wpForo Forum 2.4.14 Stored XSS via Unsafe JSON Encoding in Inline Script","id":"CVE-2026-28560"},"products":["wpForo Forum"],"published":"2026-02-28","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-05-11","vendors":["gVectors Team"]},"summary":"Administrators can inject persistent JavaScript via forum descriptions, allowing attackers to execute code in victim browsers.","url":"https://insights.sbomify.com/CVE-2026-28561/"}