CVE-2026-87840

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-20. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/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 computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

September 20, 2026

Last Modified

September 21, 2026

Advisory Details (1)

Auto-updated Sep 20, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Tripzzy < 1.5.1 – Unauthenticated Booking Data Tampering | CVE 2026-87840 | Plugin Vulnerabilities

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

Vendor Advisories for CVE-2026-87840(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 22× in last 7d / 22× 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.

  1. 2026-09-25 10:45 UTCEG score recompute
  2. 2026-09-25 10:45 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 11:26 UTCEG score recompute
  5. 2026-09-24 11:26 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-23 12:11 UTCEG score recompute
  8. 2026-09-23 12:11 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-22 12:56 UTCEG score recompute
  11. 2026-09-22 12:56 UTCGHSA enrichment
  12. 2026-09-21 21:09 UTCEPSS rescore
  13. 2026-09-21 13:41 UTCEG score recompute
  14. 2026-09-21 13:41 UTCGHSA enrichment
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-20 14:29 UTCGHSA enrichment
  17. 2026-09-20 13:56 UTCEG score recompute▲ 5.30
  18. 2026-09-20 13:56 UTCGHSA enrichment
  19. 2026-09-20 13:56 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  20. 2026-09-20 07:20 UTCNVD update
  21. 2026-09-20 06:25 UTCEG score recompute
  22. 2026-09-20 06:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-87840?
CVE-2026-87840 is a medium vulnerability published on September 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…
When was CVE-2026-87840 disclosed?
CVE-2026-87840 was first published in the National Vulnerability Database on September 20, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87840 actively exploited?
CVE-2026-87840 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-87840?
CVE-2026-87840 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-87840?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87840, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-87840

Explore →

Is Your Infrastructure Affected by CVE-2026-87840?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs