Skip to main content
← All vulnerabilities
CVE-2026-118086EUVD-2026-114314GHSA-PXJ4-565P-H4PR

WordPress WP BASE Booking plugin <= 6.5.2 - Privilege Escalation vulnerability

WP BASE Booking plugin versions 6.5.2 and earlier are affected on sites where users can hold Subscriber accounts. No vendor rating or fixed version is listed in the checked facts.

Published
Last modified
published
Not listed in CISA KEV
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Subscriber Privilege Escalation in WP BASE Booking <= 6.5.2 versions.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • wp-base-booking-of-appointments-services-and-events

    through 6.5.2

References 1

patchstack.com

FAQ

Questions about CVE-2026-118086

What does this mean?

A user with low privileges can become an administrator and gain full control of the site. The flaw lets a Subscriber-level account raise its own privileges.Source: patchstack.com

Am I affected, and how do I check?

Versions 6.5.2 and earlier of the WP BASE Booking plugin are listed as vulnerable. The condition is that the attacker holds a Subscriber account on the site. To check a site, look up the installed plugin version on the WordPress Plugins page.Source: patchstack.com

What should I do about it?

The checked facts do not name a fixed version. Update to a release newer than 6.5.2 once the vendor publishes one, and check the plugin's official page for the current release.Source: patchstack.com

Is it 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: cve.now feed data

What if there's no patch?

The checked facts give no workaround. The one setup condition they name is the Subscriber account requirement, so reviewing which users hold Subscriber accounts is the only limit the facts support until a fix is released.Source: patchstack.com