Read the docs
TI-2026-11162 Aliases CVE-2026-13145GHSA-29jr-2w77-7q4c

WP Travel < 11.8.1 - Subscriber+ Booking PII Disclosure via IDOR

Priority MEDIUM 53CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-639.

Summary

The WP Travel WordPress plugin before 11.8.1 does not verify that the booking requested on its customer account dashboard belongs to the current user, allowing any logged-in user to read another customer's booking details, including billing address information, by supplying an arbitrary booking identifier.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.0027 19th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed WP Travel (Unknown): 11.8.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownWP Travelbefore 11.8.111.8.1Patch availableCNA
  • WP Travel VendorUnknown Affected before 11.8.1 Fixed in 11.8.1 Patch available CNA

Remediation

  • Fix · CNA WP Travel (Unknown) Fixed in 11.8.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    WP Travel 11.8.1

    2 records Highest priority Priority MEDIUM 2 MEDIUM

    Other records, highest priority first

    • TI-2026-11160 WP Travel < 11.8.1 - Unauthenticated Payment Bypass via Forged PayPal IPNPriority MEDIUM 63
    Show all 2 records →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-13145
  2. 2026-10-03 Alias added: GHSA-29jr-2w77-7q4c

References

Exploit 1

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences