VibeBP <= 1.9.9.8.1 - Authenticated (Subscriber+) Privilege Escalation in set_email_notification_settings()
Strategic Overview
- Status
- Patched in 1.9.9.8.2
- Affected Plugin
- VibeBP
- Affected Version
<= 1.9.9.8.1- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2026-16135
At a glance
CVE-2026-16135 is a high-severity Improper Privilege Management vulnerability in the VibeBP WordPress plugin, affecting versions <= 1.9.9.8.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 1.9.9.8.2; sites on affected versions should update now. Disclosed November 2026, reported by d.v4n_s3c.
Vulnerability Overview
The VibeBP plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.9.9.8.1. This is due to the plugin allowing arbitrary user meta updates through the set_email_notification_settings() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to grant themselves administrator privileges by updating their own 'wp_capabilities' user meta value.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
VibeBP <= 1.9.9.8.1 carries this weakness at wp_capabilities, and reaching it takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For VibeBP the fix is 1.9.9.8.2: builds <= 1.9.9.8.1 are affected, anything from 1.9.9.8.2 onward is not.
Remediation
Update to version 1.9.9.8.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: VibeBP 1.9.9.8.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C