CVE-2024-0866

Check & Log Email <= 1.0.9 - Unauthenticated Hook Injection

2024-03-25 00:00
Sean Murphy

Strategic Overview

Status
Patched in 1.0.10
Affected Plugin
Check & Log Email – Easy Email Testing & Mail logging
Affected Version
<= 1.0.9
CVSS
8.1High
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2024-0866
View all Check & Log Email – Easy Email Testing & Mail logging vulnerabilities

At a glance

CVE-2024-0866 is a high-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the Check & Log Email WordPress plugin, affecting versions <= 1.0.9. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.0.10; sites on affected versions should update now. Disclosed March 2024, reported by Sean Murphy.

Vulnerability Overview

The Check & Log Email plugin for WordPress is vulnerable to Unauthenticated Hook Injection in all versions up to, and including, 1.0.9 via the check_nonce function. This makes it possible for unauthenticated attackers to execute actions with hooks in WordPress under certain circumstances. The action the attacker wishes to execute needs to have a nonce check, and the nonce needs to be known to the attacker. Furthermore, the absence of a capability check is a requirement.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in Check & Log Email <= 1.0.9 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For Check & Log Email the fix is 1.0.10: builds <= 1.0.9 are affected, anything from 1.0.10 onward is not.

Remediation

Update to version 1.0.10, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Check & Log Email 1.0.10 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2024-0866https://www.wordfence.com/threat-intel/vulnerabilities/id/9ae9307c-680c-43c7-8246-a3e6149c1fb6https://nvd.nist.gov/vuln/detail/CVE-2024-0866

Related records

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