Timetable and Event Schedule by MotoPress <= 2.4.16 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Exposure via action_get_event_data Function
Strategic Overview
- Status
- Patched in 2.4.17
- Affected Plugin
- Timetable and Event Schedule by MotoPress
- Affected Version
<= 2.4.16- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-9228
At a glance
CVE-2026-9228 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Timetable and Event Schedule by MotoPress WordPress plugin, affecting versions <= 2.4.16. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.4.17; sites on affected versions should update now. Disclosed May 2026, reported by AlexHenry.
Vulnerability Overview
The Timetable and Event Schedule by MotoPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.4.16 via the action_get_event_data due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to enumerate timeslot IDs and read the full WP_Post object — including post_content, post_excerpt, post_status, and post_author — of draft, pending, and private mp-event posts belonging to other users, along with their associated raw timeslot descriptions.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Timetable and Event Schedule by MotoPress <= 2.4.16 takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Timetable and Event Schedule by MotoPress the fix is 2.4.17: builds <= 2.4.16 are affected, anything from 2.4.17 onward is not.
Remediation
Update to version 2.4.17, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Timetable and Event Schedule by MotoPress 2.4.17 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Timetable and Event Schedule by MotoPress
- 9.9CVE-2024-3342: Timetable and Event Schedule by MotoPress SQL Injection
CVE-2024-3342 - 7.3CVE-2020-36840: Timetable and Event Schedule… Missing Authorization
CVE-2020-36840 - 6.6CVE-2024-39630: Timetable and Event Schedule PHP Object Injection
CVE-2024-39630 - 6.5CVE-2021-24585: Timetable and Event… Arbitrary User's Hashed
CVE-2021-24585 - 6.4CVE-2021-24584: Timetable… Unauthorised Event TimeSlot Update
CVE-2021-24584 - 5.4CVE-2021-24724: Timetable and Event Schedule… Author+ Stored XSS
CVE-2021-24724 - 4.3CVE-2021-24583: Timetable… Unauthorised Event TimeSlot Deletion
CVE-2021-24583
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C