# CVE-2026-95870: wpForo Forum <= 3.2.1 - Unauthenticated SQL Injection via 'data' Parameter

Status: published. Published: 2026-11-07. Updated: 2026-11-07.

The wpForo Forum plugin for WordPress is vulnerable to generic SQL Injection via the 'data' parameter in all versions up to, and including, 3.2.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires that a searchable topic form field of type checkbox, or a select/autocomplete field with isMultiChoice enabled, is registered in the forum configuration.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- tomdever / wpForo Forum: ≥ 0; ≤ 3.2.1 (affected, semver). Source: CNA: Wordfence

## Severity and prioritization

- CVSS 3.1: 7.5 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N; source: CNA: Wordfence

- CVSS 3.1: 7.5 (high); CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N; source: NVD: security@wordfence.com

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-89

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.wordfence.com/threat-intel/vulnerabilities/id/983524ad-8696-4239-bee0-f0ef80d7180c?source=cve (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.7/classes/PostMeta.php#L379 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.7/wpforo.php#L1105 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.7/wpforo.php#L707 (CNA: Wordfence)

- https://wordpress.org/plugins/wpforo/#developers (CNA: Wordfence)

- https://plugins.trac.wordpress.org/changeset?reponame=&new=3717441%40wpforo%2Ftags%2F3.2.2&old=3706608%40wpforo%2Ftags%2F3.1.7 (CNA: Wordfence)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.7/classes/PostMeta.php#L379 (security@wordfence.com)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.7/wpforo.php#L1105 (security@wordfence.com)

- https://plugins.trac.wordpress.org/browser/wpforo/tags/3.1.7/wpforo.php#L707 (security@wordfence.com)

- https://plugins.trac.wordpress.org/changeset?reponame=&new=3717441%40wpforo%2Ftags%2F3.2.2&old=3706608%40wpforo%2Ftags%2F3.1.7 (security@wordfence.com)

- https://wordpress.org/plugins/wpforo/#developers (security@wordfence.com)

- https://www.wordfence.com/threat-intel/vulnerabilities/id/983524ad-8696-4239-bee0-f0ef80d7180c?source=cve (security@wordfence.com)

## Provenance

- CNA: Wordfence: https://www.cve.org/CVERecord?id=CVE-2026-95870; retrieved 2026-11-07; source updated 2026-11-07

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95870; retrieved 2026-11-07; source updated 2026-11-07

Revision: 7729a49ac72975c961d74b9265953d1d09917b9b4c2fa2cf2e8af94cd2941436

Canonical: https://y2.dev/cve/CVE-2026-95870

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.