sales@hackhalt.com

Home / Threats / CVE-2026-119164

Wpforo - Security Vulnerability (CVE-2026-119164)

CVE-2026-119164

The wpForo Forum plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.2.2 via the `data[secondary_groupids]` parameter of the `wpforo_action_profile_update` POST handler. This is due to a type-confusion flaw in the secondary_groupids authorization guard within the `Members::update()` function in `classes/Members.php`, where casting a scalar CSV string (e.g. `"0,1"`) with `(array)` before `array_map('intval', …)` and `array_filter()` produces an empty array — causing the guard's outer conditional, and the else-branch that would otherwise strip the field from the update, to be bypassed entirely — while `encode()`/`decode()` downstream correctly explodes the original CSV and persists the attacker-supplied group IDs to `wp_wpforo_profiles.secondary_groupids`. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate their forum privileges to wpForo Administrator by injecting the privileged Admin group ID, granting access to the Forum Accesses editor and the ability to rewrite forum-wide capability policies for all members and edit arbitrary content owned by other users. Exploitation requires the attacker to have at least 3 approved wpForo posts to satisfy the plugin's default `min_number_posts_to_edit_account` antispam gate, along with a valid wpforo nonce obtained from their own account profile form.

CVE-2026-119164

HIGH CVSS 7.5 Published 2026-11-07 Updated 2026-11-08
AI Risk High (76/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P2 Urgent
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Components 2
Reference Links 7
AI Risk Engine High (76/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-11-07 CVE published and first recorded in the threat feed.
  2. 2026-11-08 Record updated with latest vulnerability metadata.
  3. 2026-11-08 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 4 days ago

AI enriched 4 days ago (2026-11-08 19:03 UTC)

Technical Summary

The wpForo Forum plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 3.2.2 via the `data[secondary_groupids]` parameter of the `wpforo_action_profile_update` POST handler. This is due to a type-confusion flaw in the secondary_groupids authorization guard within the `Members::update()` function in `classes/Members.php`, where casting a scalar CSV string (e.g. `"0,1"`) with `(array)` before `array_map('intval', …)` and `array_filter()` produces an empty array — causing the guard's outer conditional, and the else-branch that would otherwise strip the field…

Potential Impact

Severity is HIGH (CVSS 7.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 76/100 (High, High) with priority P2 Urgent. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Wpforo PLUGIN · wpforo Affected: <= 3.2.2 Fixed version not specified
wpForo Forum PLUGIN · wpforo-forum Affected: <= 3.2.2 Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Wpforo to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Unauthorised administrator detection in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Alert when a new administrator appears or a role is escalated. Creating a hidden admin is the most common persistence step after a WordPress compromise.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Wpforo, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Wpforo.

How do I fix it?

Update Wpforo to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Unauthorised administrator detection in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Privilege Escalation flaw. An attacker who exploits it can raise a low-privilege account, or none at all, to administrator.