CVE-2026-87840: Tripzzy < 1.5.1 - Unauthenticated Booking Data Tampering

Published Sep 20, 2026
·
Updated

The Tripzzy WordPress plugin before 1.5.1 does not perform any capability or ownership checks on its administrative booking-management actions, which are additionally exposed to unauthenticated users and gated only by a token the Tripzzy WordPress plugin before 1.5.1 issues to any anonymous visitor on request, allowing unauthenticated attackers to alter the contents, stored totals and notes of arbitrary bookings.

Affected Software

1 affected component
WordPress plugin Tripzzy<1.5.1

Event History

Sep 20, 2026
CVE Published
via MITRE·06:00 AM
Data Sourced
via MITRE·06:00 AM
DescriptionWeakness

Frequently Asked Questions

1

Who can exploit this issue?

Any unauthenticated remote visitor can exploit it. The affected administrative booking-management actions are exposed without capability or booking-ownership checks, and the required token can be requested by an anonymous visitor.

2

What booking data can be changed?

An attacker can alter arbitrary bookings, including their contents, stored totals, and notes.

3

Are installations running version 1.5.1 affected?

The issue affects Tripzzy versions before 1.5.1. The provided information does not identify any affected configuration requirements beyond running a version earlier than 1.5.1.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203