Security readout for executives and security teams
Plain-English summary
A flaw in the TrueBooker WordPress plugin can let an unauthenticated internet user change another user's email address, including an administrator's. The attacker could then use WordPress password recovery to take control of that account, potentially compromising the entire website and its data.
Executive priority
Treat this as an immediate remediation priority on internet-facing WordPress systems. An unauthenticated attacker could obtain administrator control with low complexity. Inventory affected sites, contain vulnerable installations, and investigate account changes promptly, while recognizing that the supplied sources do not confirm active exploitation.
Technical view
TrueBooker versions through 1.2.6 expose an AJAX handler without authentication or capability checks. The handler accepts a user-controlled truebooker_wp_user_id value and passes it to wp_update_user, enabling arbitrary account email changes. CVE-2026-18315 is rated CVSS 9.8 and categorized as CWE-639.
Likely exposure
WordPress sites running TrueBooker 1.2.6 or earlier are potentially exposed, particularly when the vulnerable AJAX functionality is publicly reachable. The bundle's structured affected-version entry is inconsistent with its title and description, so asset owners should confirm applicability against vendor or Wordfence guidance.
Exploitation context
The weakness is remotely reachable, requires no account or user interaction, and can lead to administrator takeover through normal password recovery. The source bundle marks the CVE as absent from KEV and provides no other evidence of active exploitation; exploitation in the wild is therefore unconfirmed.
Researcher notes
The core issue is authorization failure in admin_user_create_cus: no authentication or capability validation precedes an update selected by truebooker_wp_user_id. The supplied references include a later plugin changeset, but the bundle does not explicitly identify a fixed version or describe its changes. Avoid asserting remediation completeness without vendor confirmation.
Mitigation direction
- Identify every WordPress site running TrueBooker and record its installed version.
- Disable or remove affected versions until a vendor-confirmed fixed release is available.
- Check Wordfence and the plugin vendor's guidance for the confirmed remediation version.
- Restrict unnecessary access to WordPress AJAX endpoints as temporary defense-in-depth.
- Reset affected administrator credentials and review recovery email addresses if compromise is suspected.
Validation and detection
- Confirm whether TrueBooker is installed and whether its version is 1.2.6 or earlier.
- Verify the vulnerable plugin is disabled, removed, or updated to a vendor-confirmed fixed version.
- Review administrator accounts for unexpected email-address or password changes.
- Examine logs for unusual AJAX requests, password-reset activity, and account recovery events.
- Confirm all privileged accounts retain approved email addresses and expected access levels.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-18315 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9WordfenceVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Vendor Notified
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/73251a74-5be3-446b-8e0a-ff2d1484c467?source=cveCVE reference, Wordfence
- https://plugins.svn.wordpress.org/truebooker-appointment-booking/tags/1.2.6/main/function_ajax.phpCVE reference, Wordfence
- https://plugins.svn.wordpress.org/truebooker-appointment-booking/tags/1.2.6/main/config/truebooker-style.phpCVE reference, Wordfence
- https://plugins.svn.wordpress.org/truebooker-appointment-booking/tags/1.2.6/templates/login-register.phpCVE reference, Wordfence
- https://plugins.trac.wordpress.org/changeset/3640018/truebooker-appointment-bookingCVE reference, Wordfence
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.