CVE-2026-81796

HIGHPre-NVD 7.37.3—
EchelonGraph scoreHIGH confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. a secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

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

Unauthenticated Broken Authentication in WP Travel <= 12.0.3 versions.

CVSS v3
7.3
EG Score
7.3(high)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
Patch available.
generic Patch Available

Broken Authentication in WordPress WP Travel Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/wp-travel/vulnerability/wordpress-wp-travel-plugin-12-0-3-broken-authentication-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-81796(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 26× in last 7d / 43× 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-19 22:09 UTCEG score recompute
  2. 2026-09-19 22:09 UTCGHSA enrichment
  3. 2026-09-19 10:45 UTCGHSA enrichment
  4. 2026-09-18 23:20 UTCEG score recompute
  5. 2026-09-18 23:20 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 11:56 UTCGHSA enrichment
  8. 2026-09-18 00:32 UTCEG score recompute
  9. 2026-09-18 00:32 UTCGHSA enrichment
  10. 2026-09-17 13:07 UTCGHSA enrichment
  11. 2026-09-17 01:43 UTCGHSA enrichment
  12. 2026-09-16 14:18 UTCEG score recompute
  13. 2026-09-16 14:18 UTCGHSA enrichment
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 02:53 UTCGHSA enrichment
  17. 2026-09-15 15:28 UTCGHSA enrichment
  18. 2026-09-15 04:03 UTCEG score recompute
  19. 2026-09-15 04:03 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 16:38 UTCGHSA enrichment
  23. 2026-09-14 05:13 UTCGHSA enrichment
  24. 2026-09-13 17:49 UTCEG score recompute
  25. 2026-09-13 17:49 UTCGHSA enrichment
Show 18 more
  1. 2026-09-13 06:24 UTCGHSA enrichment
  2. 2026-09-12 19:00 UTCEG score recompute
  3. 2026-09-12 19:00 UTCGHSA enrichment
  4. 2026-09-12 07:35 UTCGHSA enrichment
  5. 2026-09-11 20:09 UTCEG score recompute
  6. 2026-09-11 20:09 UTCGHSA enrichment
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 08:44 UTCGHSA enrichment
  10. 2026-09-10 21:19 UTCEG score recompute
  11. 2026-09-10 21:19 UTCGHSA enrichment
  12. 2026-09-10 21:05 UTCEG score recompute
  13. 2026-09-10 21:05 UTCGHSA enrichment
  14. 2026-09-10 15:57 UTCEG score recompute
  15. 2026-09-10 15:57 UTCGHSA enrichment
  16. 2026-09-10 15:20 UTCEG score recompute
  17. 2026-09-10 14:35 UTCEG score recompute
  18. 2026-09-10 14:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81796?
CVE-2026-81796 is a high vulnerability published on September 10, 2026. Unauthenticated Broken Authentication in WP Travel <= 12.0.3 versions.
When was CVE-2026-81796 disclosed?
CVE-2026-81796 was first published in the National Vulnerability Database on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81796 actively exploited?
CVE-2026-81796 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 86.5% of all scored CVEs.
What is the CVSS score of CVE-2026-81796?
CVE-2026-81796 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-81796?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81796, 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-81796

Explore →

Is Your Infrastructure Affected by CVE-2026-81796?

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

Start Free Scan →Browse All CVEs