The Booking Manager WordPress plugin before 2.1.21 does not verify that a request to modify a user's Booking Manager WordPress plugin before 2.1.21-specific settings targets the requesting user's own account, allowing any authenticated user with subscriber-level access and above to create or overwrite the Booking Manager WordPress plugin before 2.1.21's per-user settings on arbitrary users, including administrators.
CVE-2026-91025
Score 4.3 from GitHub Security Advisory published 2026-09-23. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; 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.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (1)
Auto-updated Sep 23, 2026Booking Manager < 2.1.21 – Subscriber+ Arbitrary User Plugin Meta Modification via IDOR | CVE 2026-91025 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/6e010e3e-78e8-4bfc-b880-d9a85cff2c2a/Vendor Advisories for CVE-2026-91025(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 13× in last 7d / 13× 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-24 16:52 UTCEG score recompute
- 2026-09-24 16:52 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 18:19 UTCEG score recompute
- 2026-09-23 18:19 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 11:23 UTCGHSA enrichment
- 2026-09-23 11:01 UTCEG score recompute▲ 4.30
- 2026-09-23 11:01 UTCGHSA enrichment
- 2026-09-23 11:01 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
- 2026-09-23 06:17 UTCNVD update
- 2026-09-23 06:06 UTCEG score recompute
- 2026-09-23 06:06 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-91025?
When was CVE-2026-91025 disclosed?
Is CVE-2026-91025 actively exploited?
What is the CVSS score of CVE-2026-91025?
How do I remediate CVE-2026-91025?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-91025
Is Your Infrastructure Affected by CVE-2026-91025?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.