CVE-2026-16635
Last modified
CVE-2026-16635 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.31% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| pronamic | Pronamic Pay | <= 10.1.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-16635?
How severe is CVE-2026-16635?
How do I fix CVE-2026-16635?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-1663GitLab has remediated an issue in GitLab CE/EE affecting all…4.3
- CVE-2026-16630A security vulnerability has been detected in syncfusion ej2…5.3
- CVE-2026-16631A vulnerability was detected in publint up to 0.1.4. This im…5.3
- CVE-2026-16632A flaw has been found in boazsegev facil.io up to 0.7.4. Aff…7.3
- CVE-2026-16633### Impact If PDF.js is used to load a malicious PDF, and P…8.6
- CVE-2026-16634TOML::XS versions before 0.06 for Perl bundle an unsupported…9.8
- CVE-2026-16636The FluentSMTP – WP SMTP Plugin with Amazon SES, SendGrid, M…7.2
- CVE-2026-16637OPeNDAP Hyrax allows SSRF and credential disclosure via unva…6.5
- CVE-2026-1664Summary An Insecure Direct Object Reference has been found …6.9
- CVE-2026-1665A command injection vulnerability exists in nvm (Node Versio…5.4
- CVE-2026-16653A security flaw has been discovered in boazsegev facil.io up…5.5
- CVE-2026-16655The Fluent Forms – Customizable Contact Forms, Survey, Quiz,…7.2
Are you affected by CVE-2026-16635?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
