CVE-2026-90650: MotoPress Hotel Booking (WordPress plugin) · Cross-site Scripting
Affects MotoPress Hotel Booking (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 30 Oct 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jetmonstersMotoPress Hotel Booking | Affected
| Fixed in– |
AI-suggested
As a mitigation, administrators should ensure the Stripe signing secret is configured to enable webhook signature verification, preventing acceptance of forged webhooks. Until a patch is available, disabling the premium Stripe webhook listener or restricting access to payment logs may reduce risk.
Description
The MotoPress Hotel Booking plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Stripe Webhook event object 'id' in all versions up to, and including, 6.2.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The premium Stripe webhook listener only verifies the webhook signature when an optional Stripe signing secret has been configured; because that secret is empty by default, a forged webhook is accepted without cryptographic verification, and the attacker-controlled event object 'id' (e.g. a forged 'refund.created' refund id) is written unescaped into the payment log and later echoed unsanitized when an administrator views the payment. An attacker must know a valid Stripe PaymentIntent ID for an existing payment to route the forged webhook to a payment record. Note: The vulnerable webhook handler (webhook-listener.php) is part of the premium Stripe gateway integration and is not present in the lite plugin directory.
References
- wordfence.com/threat-intel/vulnerabilities/id/ed8cb22d-cd8c-482e-a295-4717717d6b83?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/motopress-hotel-booking-lite/tags/6.2.4/includes/admin/edit-cpt-pages/payment-edit-cpt-page.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/motopress-hotel-booking-lite/tags/6.2.4/includes/entities/payment.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/motopress-hotel-booking-lite/tags/6.2.4/includes/payments/gateways/abstract-notification-listener.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3694788/ (opens in a new tab)