CVE-2026-9180

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-07-03. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

The MotoPress Appointment Booking plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to, and including, 2.4.4. This is due to the POST /motopress/appointment/v1/bookings REST endpoint being registered with 'permission_callback' => '__return_true', allowing unauthenticated access, while the createBooking handler in BookingsRestController.php accepts an attacker-supplied payment_details.booking_id value and loads the referenced booking via findById() without verifying that the caller owns or has any rights to that booking. This makes it possible for unauthenticated attackers to overwrite the customer name, email address, phone number, and customer_id of any non-confirmed victim booking by submitting a request with no reservation items, causing BookingService::createBooking() to load the existing victim booking object and persist it with attacker-controlled customer data. Victim booking IDs can be harvested prior to exploitation without authentication by querying the also-publicly-accessible GET /motopress/appointment/v1/bookings/reservations endpoint with a guessable service_id and date range, and only bookings whose status is not STATUS_CONFIRMED (e.g., pending or auto-draft) are valid targets.

CVSS v3
5.3
EG Score
5.3(high)
EPSS
26.2%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 6, 2026

Vendor Advisories for CVE-2026-9180(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 11× in last 7d / 11× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 09:25 UTCEG score recompute
  3. 2026-07-06 09:24 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 08:26 UTCEG score recompute
  6. 2026-07-05 08:26 UTCGHSA enrichment
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-04 07:29 UTCEG score recompute
  9. 2026-07-04 07:29 UTCGHSA enrichment
  10. 2026-07-03 06:32 UTCEG score recompute
  11. 2026-07-03 06:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-9180?
CVE-2026-9180 is a medium vulnerability published on July 3, 2026. The MotoPress Appointment Booking plugin for WordPress is vulnerable to Authorization Bypass Through User-Controlled Key in all versions up to, and including, 2.4.4. This is due to the POST /motopress/appointment/v1/bookings REST endpoint being registered with 'permissioncallback' => 'returntrue',…
When was CVE-2026-9180 disclosed?
CVE-2026-9180 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9180 actively exploited?
CVE-2026-9180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9180?
CVE-2026-9180 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-9180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9180, 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-9180

Explore →

Is Your Infrastructure Affected by CVE-2026-9180?

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