CVE-2026-1044 json
Tennis Court Bookings <= 1.2.7 - Authenticated (Administrator+) Stored Cross-Site Scripting via Admin Settings and Calendar Parameters
published 2026-02-19 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8225
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
The Tennis Court Bookings plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.2.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- renoiriii Tennis Court Bookings
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/99b91fb6-9e60-447d-ab43-2be231052140?source=cve
- downloads.wordpress.org /plugin/tennis-court-bookings.zip
- wordpress.org /plugins/tennis-court-bookings/
- plugins.trac.wordpress.org /browser/tennis-court-bookings/tags/1.2.7/views/setting.php#L65
- plugins.trac.wordpress.org /browser/tennis-court-bookings/tags/1.2.7/views/calendar_form.php#L43
- plugins.trac.wordpress.org /browser/tennis-court-bookings/tags/1.2.7/views/calendar_form.php#L201
Sources
- CVE List CVE-2026-1044
- NVD CVE-2026-1044
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.