# CVE-2021-24584: Timetable and Event Schedule by MotoPress < 2.4.2 - Unauthorised Event TimeSlot Update

> Contributors can modify arbitrary event timeslots without authorization or CSRF protection, potentially altering event schedules.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-2v92-7cf3-4vm5

## What is CVE-2021-24584?

CVE-2021-24584 is a medium-severity missing authorization vulnerability in Unknown Timetable and Event Schedule by MotoPress, published on 20 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Timetable and Event Schedule WordPress plugin before 2.4.2 does not have proper access control when updating a timeslot, allowing any user with the edit_posts capability (contributor+) to update arbitrary timeslot from any events. Furthermore, no CSRF check is in place as well, allowing such attack to be perform via CSRF against a logged in with such capability. In versions before 2.3.19, the lack of sanitisation and escaping in some of the fields, like the descritption could also lead to Stored XSS issues

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-24584?

It affects 1 product.


Products: Motopress Timetable and Event Schedule.

## How do I fix CVE-2021-24584?

No fix has been published for CVE-2021-24584 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-24584 being exploited?

There is no known exploitation of CVE-2021-24584 in the wild and no public exploit code.

## Other vulnerabilities in Unknown Timetable and Event Schedule by MotoPress

- [CVE-2020-36840](https://insights.sbomify.com/CVE-2020-36840/): Timetable and Event Schedule by MotoPress <= 2.3.8 - Missing Authorization (high 7.3)
- [CVE-2021-24585](https://insights.sbomify.com/CVE-2021-24585/): Timetable and Event Schedule by MotoPress < 2.4.0 - Arbitrary User's Hashed Password/Email/Username Disclosure (medium 6.5)
- [CVE-2021-24724](https://insights.sbomify.com/CVE-2021-24724/): Timetable and Event Schedule by MotoPress < 2.3.19 - Author+ Stored Cross-Site Scripting (medium 5.4)
- [CVE-2021-24583](https://insights.sbomify.com/CVE-2021-24583/): Timetable and Event Schedule by MotoPress < 2.4.2 - Unauthorised Event TimeSlot Deletion (medium 4.3)
- [CVE-2022-2843](https://insights.sbomify.com/CVE-2022-2843/): MotoPress Timetable and Event Schedule Quick Edit admin-ajax.php cross site scripting (low 3.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24584 and fix it if it is affected.

What it is: CVE-2021-24584 is a medium-severity missing authorization vulnerability in Unknown Timetable and Event Schedule by MotoPress, published on 20 Sep 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-24584 in the wild and no public exploit code.

Affected product: Unknown Timetable and Event Schedule by MotoPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-24584/ (Markdown: https://insights.sbomify.com/CVE-2021-24584/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-24584
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-24584
- OSV: https://osv.dev/vulnerability/CVE-2021-24584

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-24584/
Summaries are generated and may contain mistakes; the official description above is the record.