# CVE-2021-24585: Timetable and Event Schedule by MotoPress < 2.4.0 - Arbitrary User's Hashed Password/Email/Username Disclosure

> Low-privilege users can retrieve sensitive user data including hashed passwords and emails by exploiting an information disclosure flaw in the plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xm59-x79v-w7q2

## What is CVE-2021-24585?

CVE-2021-24585 is a medium-severity vulnerability in Unknown Timetable and Event Schedule by MotoPress, published on 20 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Timetable and Event Schedule WordPress plugin before 2.4.0 outputs the Hashed Password, Username and Email Address (along other less sensitive data) of the user related to the Even Head of the Timeslot in the response when requesting the event Timeslot data with a user with the edit_posts capability. Combined with the other Unauthorised Event Timeslot Modification issue (https://wpscan.com/reports/submissions/4699/) where an arbitrary user ID can be set, this could allow low privilege users with the edit_posts capability (such as author) to retrieve sensitive User data by iterating over the user_id

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Motopress Timetable and Event Schedule.

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

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

## Is CVE-2021-24585 being exploited?

There is no known exploitation of CVE-2021-24585 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-24584](https://insights.sbomify.com/CVE-2021-24584/): Timetable and Event Schedule by MotoPress < 2.4.2 - Unauthorised Event TimeSlot Update (medium 5.4)
- [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-24585 and fix it if it is affected.

What it is: CVE-2021-24585 is a medium-severity vulnerability in Unknown Timetable and Event Schedule by MotoPress, published on 20 Sep 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-24585 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-24585/ (Markdown: https://insights.sbomify.com/CVE-2021-24585/index.md)
```

## Sources

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

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