The WP Travel Engine – Tour Booking Plugin – Tour Operator Software plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 6.8.4. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to view private booking billing details — including the victim customer's first name, last name, email address, street address, city, and phone number — rendered as default values in checkout form fields by binding an arbitrary booking ID to the attacker's session. The only access control on the endpoint is a frontend nonce that is publicly emitted to all visitors via the wteL10n global on trip pages, meaning it provides CSRF protection only and does not restrict unauthenticated access.
CVE-2026-17087
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-16. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
August 16, 2026
Last Modified
August 20, 2026
References (12)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12/includes/classes/Abstracts/AjaxController.php#L52
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12/includes/classes/Builders/FormFields/BillingFormFields.php#L87
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12/includes/classes/Core/Controllers/Ajax/AddToCart.php#L232
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12/includes/classes/Core/Controllers/Ajax/AddToCart.php#L31
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.7.12/includes/classes/Legacy/Cart.php#L373
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/includes/classes/Abstracts/AjaxController.php#L52
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/includes/classes/Builders/FormFields/BillingFormFields.php#L87
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/includes/classes/Core/Controllers/Ajax/AddToCart.php#L232
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/includes/classes/Core/Controllers/Ajax/AddToCart.php#L31
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-travel-engine/tags/6.8.3/includes/classes/Legacy/Cart.php#L373
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?reponame=&old=3632552%40wp-travel-engine&new=3632552%40wp-travel-engine
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/9dc4a6f9-b663-4573-9a6d-0c96ee25308d?source=cve
Vendor Advisories for CVE-2026-17087(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 01:20 UTCEG score recompute
- 2026-08-21 01:20 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 13:00 UTCGHSA enrichment
- 2026-08-20 07:09 UTCGHSA enrichment
- 2026-08-19 18:49 UTCEG score recompute
- 2026-08-19 18:49 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 06:29 UTCGHSA enrichment
- 2026-08-18 18:10 UTCEG score recompute
- 2026-08-18 18:09 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 05:47 UTCGHSA enrichment
- 2026-08-17 17:28 UTCEG score recompute
- 2026-08-17 17:28 UTCGHSA enrichment
- 2026-08-17 17:11 UTCEG score recompute
- 2026-08-17 17:11 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 08:08 UTCGHSA enrichment
- 2026-08-16 19:49 UTCEG score recompute
- 2026-08-16 19:49 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:29 UTCEG score recompute
- 2026-08-16 06:54 UTCEG score recompute
- 2026-08-16 06:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-17087?
When was CVE-2026-17087 disclosed?
Is CVE-2026-17087 actively exploited?
What is the CVSS score of CVE-2026-17087?
How do I remediate CVE-2026-17087?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17087
Is Your Infrastructure Affected by CVE-2026-17087?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.