Skip to main content
← Vulnerabilities

wpForo Forum <= 3.2.2 - Authenticated (Subscriber+) Privilege Escalation to 'data[secondary_groupids]' CSV Parameter

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
0.51% · 43rd percentile
16/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The wpForo Forum plugin for WordPress has a flaw that lets an attacker with a low-privilege account, such as a Subscriber, gain wpForo Administrator rights over the network, enabling them to change forum-wide access policies and edit content owned by other users. The attacker must first log in with that low-privilege account and reach the forum's profile update function.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

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.now Index

16Pcve.now Index 16 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • tomdever wpForo Forum

    through 3.2.2

Evidence 7

  1. Link
  2. Link
  3. Link
  4. Link
  5. Link
Show all 7 sourcesShow fewer sources
  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119164

Is CVE-2026-119164 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-119164?

wpForo Forum: through 3.2.2.Source: cve.now feed data