CVE-2026-18057

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
8.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: 8.1Exploit: Elevated riskExposed: 0

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

The Events Manager WordPress plugin before 7.4.1 does not sanitise and escape a user-controlled value before using it in a SQL statement, allowing users with a subscriber account and above to perform SQL injection attacks and tamper with booking consent records belonging to other people.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
52(Track*)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 12, 2026

Advisory Details (1)

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

Events Manager < 7.4.1 – Subscriber+ Booking Consent Record Tampering via SQL Injection | CVE 2026-18057 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/e2685778-936f-4920-9b5c-0fcbb9da6d26/

Vendor Advisories for CVE-2026-18057(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 29× 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-20 10:36 UTCGHSA enrichment
  2. 2026-08-19 23:46 UTCEG score recompute
  3. 2026-08-19 23:46 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 12:55 UTCGHSA enrichment
  6. 2026-08-19 02:04 UTCGHSA enrichment
  7. 2026-08-18 15:13 UTCEG score recompute
  8. 2026-08-18 15:13 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 03:30 UTCGHSA enrichment
  11. 2026-08-17 16:39 UTCEG score recompute
  12. 2026-08-17 16:39 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 05:49 UTCGHSA enrichment
  15. 2026-08-16 18:59 UTCEG score recompute
  16. 2026-08-16 18:59 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 08:01 UTCEG score recompute
  19. 2026-08-16 08:01 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 21:11 UTCGHSA enrichment
  22. 2026-08-15 10:20 UTCEG score recompute
  23. 2026-08-15 10:20 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 23:29 UTCGHSA enrichment
Show 17 more
  1. 2026-08-14 12:39 UTCGHSA enrichment
  2. 2026-08-14 01:48 UTCEG score recompute
  3. 2026-08-14 01:48 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 14:58 UTCGHSA enrichment
  6. 2026-08-13 04:08 UTCEG score recompute
  7. 2026-08-13 04:08 UTCGHSA enrichment
  8. 2026-08-12 17:17 UTCEG score recompute
  9. 2026-08-12 17:17 UTCGHSA enrichment
  10. 2026-08-12 16:21 UTCEG score recompute 8.10
  11. 2026-08-12 16:21 UTCGHSA enrichment
  12. 2026-08-12 16:20 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-12 06:31 UTCGHSA enrichment
  15. 2026-08-12 06:30 UTCNVD update
  16. 2026-08-12 06:06 UTCEG score recompute
  17. 2026-08-12 06:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18057?
CVE-2026-18057 is a high vulnerability published on August 12, 2026. The Events Manager WordPress plugin before 7.4.1 does not sanitise and escape a user-controlled value before using it in a SQL statement, allowing users with a subscriber account and above to perform SQL injection attacks and tamper with booking consent records belonging to other people.
When was CVE-2026-18057 disclosed?
CVE-2026-18057 was first published in the National Vulnerability Database on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18057 actively exploited?
CVE-2026-18057 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 87.0% of all scored CVEs.
What is the CVSS score of CVE-2026-18057?
CVE-2026-18057 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-18057?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18057, 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-18057

Explore →

Is Your Infrastructure Affected by CVE-2026-18057?

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