← back

CVE-2026-16635

HIGH · 8.8
hype MOSTLY HYPE · 32 hack

Day-zero advisory churn; no PoC, KEV, or exploitation signal; early amplification only.

What: Pronamic Pay WordPress plugin (≤10.1.0) privilege escalation via unvalidated role assignment in Gravity Forms integration; CVSS 8.8 (HIGH).

Why it matters: Authenticated subscriber-level users can escalate to Administrator if admin has configured the "Update User Role" feature. No KEV listing yet, but CVE published same-day with technical details; no public PoC or in-the-wild reports confirmed in social chatter yet.

Where it's seen: Vulnerability aggregators (Hacker Wire, Patchstack) and security news feeds amplifying the NVD advisory within hours of publication; no vendor urgency signaling, defender triage questions, or PoC links observed yet.

RISK: HIGH — Authenticated privilege escalation to admin in commonly-used WordPress plugin if feature configured.

Generated by claude-haiku-4-5 from public posts and authoritative metadata. AI can make mistakes — verify against vendor advisories before acting. 8/1/2026, 11:13:16 AM

Description

The Pronamic Pay plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 10.1.0 This is due to the `maybe_update_user_role()` function passing an attacker-controlled Gravity Forms field value (`$lead[$feed->user_role_field_id]`) directly into `WP_User::set_role()` without any allowlist validation, capability comparison, or permission check to constrain which roles can be assigned. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate their own WordPress account to Administrator by tampering with the role field value in a form submission. Exploitation requires that an administrator has already configured a Pronamic Pay payment feed in Gravity Forms with the **Update User Role** option enabled and mapped to a form field; once that configuration is in place, no further preconditions exist to prevent an authenticated attacker from exploiting this vulnerability.

CVSS 3.1 breakdown

Exploitability 2.8 · Impact 5.9
vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weaknesses