The Hydra Booking — Appointment Scheduling & Booking Calendar WordPress plugin before 1.2.3 does not verify that the host record being modified belongs to the user making the request, allowing authenticated users holding a Hydra Booking — Appointment Scheduling & Booking Calendar WordPress plugin before 1.2.3-assigned host role to modify other hosts' profile data and reassign ownership of another host's record to themselves.
CVE-2026-92421
Score 4.7 from GitHub Security Advisory published 2026-09-19. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(high)
- EG Risk
- 21(Track)EG Risk 21/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 computedSeverity47% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
September 19, 2026
Last Modified
September 19, 2026
Advisory Details (1)
Auto-updated Sep 19, 2026Hydra Booking 1.1.0 – < 1.2.3 – Hydra Host+ Host Profile Takeover via IDOR | CVE 2026-92421 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/3ba305b9-5f3b-47eb-a5d7-ddbeeeefd0a4/Vendor Advisories for CVE-2026-92421(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 10× in last 7d / 10× 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-09-20 20:16 UTCEPSS rescore
- 2026-09-20 13:30 UTCEG score recompute
- 2026-09-20 13:30 UTCGHSA enrichment
- 2026-09-19 14:27 UTCGHSA enrichment
- 2026-09-19 13:25 UTCEG score recompute▲ 4.70
- 2026-09-19 13:25 UTCGHSA enrichment
- 2026-09-19 13:24 UTCMITRE cvelistV5CVSS v3 → 4.7 · severity → MEDIUM
- 2026-09-19 07:17 UTCNVD update
- 2026-09-19 06:26 UTCEG score recompute
- 2026-09-19 06:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
Frequently asked(5)
What is CVE-2026-92421?
When was CVE-2026-92421 disclosed?
Is CVE-2026-92421 actively exploited?
What is the CVSS score of CVE-2026-92421?
How do I remediate CVE-2026-92421?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-92421
Is Your Infrastructure Affected by CVE-2026-92421?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.