CVE-2026-94228 TrueBooker CVE debrief

Who should care

Defenders responsible for WordPress installations with the TrueBooker plugin should assess exposure and verify the plugin version. This includes WordPress administrators, security teams, and IT personnel who manage plugin updates and configurations. These individuals should review the plugin's configuration for any unexpected changes and ensure that the plugin is updated to version 1.3.0 or later.

Why it matters

Defenders should care about CVE-2026-94228 because it allows unauthenticated visitors to overwrite the TrueBooker WordPress plugin's configuration, potentially leading to unauthorized changes or loss of plugin functionality. WordPress administrators and security teams should verify the plugin version and review configuration for unexpected changes.

• Potential unauthorized configuration changes to the plugin
• Possible loss of plugin settings or functionality

Technical summary

The TrueBooker WordPress plugin before 1.3.0 does not perform any capability check on one of its setup handlers, and the token it does check is issued to unauthenticated visitors, allowing anyone to overwrite the plugin's entire configuration and to discard any setting they do not supply. This vulnerability is a result of inadequate access control and validation of user input, which could lead to unauthorized changes to the plugin's configuration. Defenders should prioritize verifying the version of the TrueBooker WordPress plugin and ensuring it is updated to 1.3.0 or later.

Defensive priority

Defenders should prioritize verifying the version of the TrueBooker WordPress plugin and ensuring it is updated to 1.3.0 or later.

Recommended defensive actions

• Verify the version of the TrueBooker WordPress plugin and update to 1.3.0 or later
• Review plugin configuration for potential unauthorized changes
• Monitor plugin settings for unexpected modifications
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability, with the primary source being the WPScan reference. The vulnerability was reported by WPScan and assigned a CVE by the CVE Program. The NVD entry provides additional details based on the CVE metadata. However, the exact scope and impact of the vulnerability are not explicitly stated, and defenders should verify the plugin version and configuration to assess exposure.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.