dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-8157

HIGH · 8.8 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Vitepos WordPress plugin before 3.4.2 does not properly restrict the roles that can be assigned when creating new users via one of its REST API endpoints, allowing authenticated users with a custom Vitepos WordPress plugin before 3.4.2 role to escalate privileges to administrator.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Vitepos WordPress plugin before 3.4.2 contains a privilege escalation vulnerability in its REST API user creation endpoint. The plugin fails to properly restrict or validate the roles that can be assigned when creating new users, allowing authenticated users with a custom Vitepos role to create administrator-level accounts and gain full site access.

MitigationUpdate the Vitepos plugin to version 3.4.2 or later. Audit existing user accounts for unauthorized administrator accounts created prior to patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Vitepos plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate Vitepos and note the version number displayed. Compare this to version 3.4.2.
    Affected if Installed version is lower than 3.4.2
  2. Identify custom Vitepos user roles
    Go to WordPress admin > Users > Roles or inspect the wp_options table for entries related to vitepos_roles. Note any custom roles created by the plugin.
    Affected if Custom Vitepos roles exist in the installation
  3. Review user accounts for unauthorized administrators
    Navigate to WordPress admin > Users and examine all accounts with Administrator role. Identify any accounts that were not созданные вами or that appeared during the period Vitepos was active.
    Affected if Administrator accounts exist that you did not create or that were created via API
  4. Check for REST API user creation activity
    Review WordPress audit logs, activity logs, or security plugin logs for user creation events via the REST API endpoint. Look for POST requests to user creation endpoints with administrator role assigned.
    Affected if User creation events via REST API are logged, especially with administrator role
  5. Verify REST API route accessibility
    Access the endpoint /wp-json/vitepos/v1/ or query the WordPress REST API routes to confirm the Vitepos user creation endpoint is registered and accessible.
    Affected if Vitepos REST API routes are active and accessible

You are affected if the Vitepos plugin version is below 3.4.2 AND either custom Vitepos user roles exist in your installation OR unexpected administrator accounts are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Vitepos plugin to version 3.4.2 or later. Audit existing user accounts for unauthorized administrator accounts created prior to patching.

Recommended fix Moderate confidence

Vitepos plugin version 3.4.2 or later

  1. 1. Identify the currently installed Vitepos plugin version in the WordPress installation
  2. 2. If the installed version is before 3.4.2, navigate to Plugins > Installed Plugins in WordPress admin
  3. 3. Update the Vitepos plugin to version 3.4.2 or later
  4. 4. Verify the update was successful by checking the plugin version
  5. 5. Test that the REST API endpoint properly enforces role restrictions for non-administrator users

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8157 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data