CVE-2021-24584

Timetable and Event Schedule by MotoPress <= 2.4.1 - Unauthorised Event TimeSlot Update

2021-08-23 00:00
dc11

Strategic Overview

Status
Patched in 2.4.2
Affected Version
<= 2.4.1
CVSS
6.4Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2021-24584
View all Timetable and Event Schedule by MotoPress vulnerabilities

At a glance

CVE-2021-24584 is a medium-severity Improper Access Control vulnerability in the Timetable and Event Schedule by MotoPress WordPress plugin, affecting versions <= 2.4.1. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). The issue is fixed in version 2.4.2; sites on affected versions should update now. Disclosed August 2021, reported by dc11.

Vulnerability Overview

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

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-284: Improper Access Control

Reaching this weakness in Timetable and Event Schedule by MotoPress <= 2.4.1 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For Timetable and Event Schedule by MotoPress the fix is 2.4.2: builds <= 2.4.1 are affected, anything from 2.4.2 onward is not.

Remediation

Update to version 2.4.2, 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.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C