Answer in brief
CVE-2026-87840 records a Unknown severity vulnerability in Tripzzy < 1.5.1 - Unauthenticated Booking Data Tampering. The current sources do not mark it as known exploited. The current feed maps Unknown/Tripzzy (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Unknown/Tripzzy (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Unknown/Tripzzygeneric | >=1.3.4 <1.5.1 | 1.5.1 |
Published upstream
Sep 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.