{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-28562 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-28562 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28562 is a high-severity SQL injection vulnerability in gVectors Team wpForo Forum, published on 28 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-28562 and fix it if it is affected.\n\nWhat it is: CVE-2026-28562 is a high-severity SQL injection vulnerability in gVectors Team wpForo Forum, published on 28 Feb 2026. 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-2026-28562 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-28562/ (Markdown: https://insights.sbomify.com/CVE-2026-28562/index.md)","id":"CVE-2026-28562","markdown":"https://insights.sbomify.com/CVE-2026-28562/index.md","name":"CVE-2026-28562","record":{"aliases":["GHSA-fm3m-r2wp-895q"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract database credentials via SQL injection in the wpForo Forum plugin's topic ordering parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"wpforo_forum","vendor":"gvectors"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"wpForo 2.4.14 contains an unauthenticated SQL injection vulnerability in Topics::get_topics() where the ORDER BY clause relies on ineffective esc_sql() sanitization on unquoted identifiers. Attackers exploit the wpfob parameter with CASE WHEN payloads to perform blind boolean extraction of credentials from the WordPress database.","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 SQL Injection via Topics ORDER BY Parameter","id":"CVE-2026-28562","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Apache Airflow: DAG authorization bypass","id":"CVE-2026-28563"},"packages":[],"prev":{"headline":"wpForo Forum 2.4.14 Stored XSS via Unescaped Forum Description in Templates","id":"CVE-2026-28561"},"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":"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["gVectors Team"]},"summary":"Unauthenticated attackers can extract database credentials via SQL injection in the wpForo Forum plugin's topic ordering parameter.","url":"https://insights.sbomify.com/CVE-2026-28562/"}