CVE-2026-57367

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

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

Subscriber Broken Access Control in WP Booking System < 5.12.8.1 versions.

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

Published

July 23, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 23, 2026
No patch confirmed yet.
generic

Broken Access Control in WordPress WP Booking System Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/wp-booking-system-premium/vulnerability/wordpress-wp-booking-system-plugin-5-12-8-1-broken-access-control-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-57367(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 / 42× 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-08-03 13:02 UTCEG score recompute
  2. 2026-08-03 13:02 UTCGHSA enrichment
  3. 2026-08-03 10:36 UTCEPSS rescore
  4. 2026-08-03 00:29 UTCGHSA enrichment
  5. 2026-08-02 11:56 UTCEG score recompute
  6. 2026-08-02 11:56 UTCGHSA enrichment
  7. 2026-08-02 02:27 UTCEPSS rescore
  8. 2026-08-01 23:23 UTCGHSA enrichment
  9. 2026-08-01 10:50 UTCEG score recompute
  10. 2026-08-01 10:50 UTCGHSA enrichment
  11. 2026-08-01 04:16 UTCEPSS rescore
  12. 2026-07-31 22:17 UTCGHSA enrichment
  13. 2026-07-31 09:43 UTCGHSA enrichment
  14. 2026-07-30 21:08 UTCEG score recompute
  15. 2026-07-30 21:08 UTCGHSA enrichment
  16. 2026-07-30 16:28 UTCEPSS rescore
  17. 2026-07-30 08:03 UTCEG score recompute
  18. 2026-07-30 08:03 UTCGHSA enrichment
  19. 2026-07-30 01:30 UTCEPSS rescore
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-29 19:29 UTCGHSA enrichment
  22. 2026-07-29 06:39 UTCGHSA enrichment
  23. 2026-07-28 18:06 UTCEG score recompute
  24. 2026-07-28 18:06 UTCGHSA enrichment
  25. 2026-07-28 15:37 UTCEPSS rescore
Show 17 more
  1. 2026-07-28 05:31 UTCGHSA enrichment
  2. 2026-07-27 16:58 UTCEG score recompute
  3. 2026-07-27 16:58 UTCGHSA enrichment
  4. 2026-07-27 14:14 UTCEPSS rescore
  5. 2026-07-27 04:25 UTCGHSA enrichment
  6. 2026-07-26 15:49 UTCEG score recompute
  7. 2026-07-26 15:49 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-26 03:16 UTCEG score recompute
  11. 2026-07-26 03:15 UTCGHSA enrichment
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-25 14:18 UTCEPSS rescore
  14. 2026-07-24 14:18 UTCEPSS rescore
  15. 2026-07-24 14:18 UTCEPSS rescore
  16. 2026-07-23 11:47 UTCEG score recompute
  17. 2026-07-23 11:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57367?
CVE-2026-57367 is a high vulnerability published on July 23, 2026. Subscriber Broken Access Control in WP Booking System < 5.12.8.1 versions.
When was CVE-2026-57367 disclosed?
CVE-2026-57367 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57367 actively exploited?
CVE-2026-57367 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 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-57367?
CVE-2026-57367 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-57367?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57367, 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-57367

Explore →

Is Your Infrastructure Affected by CVE-2026-57367?

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

Start Free Scan →Browse All CVEs