CVE-2024-2017

Countdown, Coming Soon, Maintenance – Countdown & Clock <= 2.7.8 - Missing Authorization to Authenticated (Subscriber+) PHP Object Injection

2024-06-05 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2.7.8.1
Affected Plugin
Countdown, Coming Soon, Maintenance – Countdown & Clock
Affected Version
<= 2.7.8
CVSS
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-2017
View all Countdown, Coming Soon, Maintenance – Countdown & Clock vulnerabilities

At a glance

CVE-2024-2017 is a medium-severity Missing Authorization vulnerability in the Countdown, Coming Soon, Maintenance WordPress plugin, affecting versions <= 2.7.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.7.8.1; sites on affected versions should update now. Disclosed June 2024, reported by Lucio Sá.

Vulnerability Overview

The Countdown, Coming Soon, Maintenance – Countdown & Clock plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the conditionsRow and switchCountdown functions in all versions up to, and including, 2.7.8. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject PHP Objects and modify the status of countdowns.

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-862: Missing Authorization

Reaching this weakness in Countdown, Coming Soon, Maintenance <= 2.7.8 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Countdown, Coming Soon, Maintenance the fix is 2.7.8.1: builds <= 2.7.8 are affected, anything from 2.7.8.1 onward is not.

Remediation

Update to version 2.7.8.1, 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: Countdown, Coming Soon, Maintenance 2.7.8.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-2017https://www.wordfence.com/threat-intel/vulnerabilities/id/d8fab229-cd6b-45a3-9e80-a03a1704ad3ehttps://nvd.nist.gov/vuln/detail/CVE-2024-2017

Related records

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