CVE-2026-119164 — WordPress
HIGHCVE-2026-119164 is a high-severity (CVSS 7.5) Improper Privilege Management vulnerability. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
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`…
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.
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
The records we use list no fixed release for CVE-2026-119164. Check the upstream advisory for a patched version, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2026-119164 in your dependencies?
Find it across your dependency tree, including transitive dependencies.