Skip to main content

CVE-2025-9519: CWE-94 Improper Control of Generation of Code ('Code Injection') in kleor Easy Timer

High
VulnerabilityCVE-2025-9519cvecve-2025-9519cwe-94
Published: Thu Sep 04 2025 (09/04/2025, 04:23:48 UTC)
Source: CVE Database V5
Vendor/Project: kleor
Product: Easy Timer

Description

The Easy Timer plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.2.1 via the plugin's shortcodes. This is due to insufficient restriction of shortcode attributes. This makes it possible for authenticated attackers, with Editor-level access and above, to execute code on the server.

AI-Powered Analysis

AILast updated: 09/04/2025, 04:47:45 UTC

Technical Analysis

CVE-2025-9519 is a high-severity vulnerability affecting the Easy Timer plugin for WordPress, developed by kleor. This vulnerability is classified under CWE-94, which pertains to improper control of code generation, commonly known as code injection. The flaw exists in all versions of the Easy Timer plugin up to and including version 4.2.1. The root cause is insufficient restriction on shortcode attributes within the plugin, which allows authenticated users with Editor-level privileges or higher to inject and execute arbitrary code on the server hosting the WordPress site. This Remote Code Execution (RCE) vulnerability does not require user interaction beyond the attacker’s own authenticated session, and it can be exploited remotely over the network (AV:N). The CVSS v3.1 base score is 7.2, reflecting high severity, with a vector indicating low attack complexity (AC:L), high privileges required (PR:H), no user interaction (UI:N), and impacts on confidentiality, integrity, and availability (C:H/I:H/A:H). Although no known exploits are currently observed in the wild, the vulnerability poses a significant risk because it enables attackers to fully compromise the affected server, potentially leading to data theft, site defacement, malware deployment, or pivoting to internal networks. The vulnerability is particularly dangerous because WordPress sites often run with elevated privileges and host critical business or customer data. The lack of available patches at the time of publication increases the urgency for mitigation.

Potential Impact

For European organizations, this vulnerability represents a substantial threat due to the widespread use of WordPress as a content management system across various sectors including government, education, healthcare, and commerce. Successful exploitation could lead to unauthorized access to sensitive personal data protected under GDPR, resulting in regulatory penalties and reputational damage. The ability to execute arbitrary code on servers can disrupt business operations through website defacement, data corruption, or ransomware deployment. Additionally, compromised WordPress sites can be used as a foothold for lateral movement within corporate networks, increasing the risk of broader cyberattacks. The high privileges required for exploitation somewhat limit the attack surface to insiders or compromised accounts, but given the common practice of granting Editor-level access to multiple users, the risk remains significant. The absence of known exploits in the wild currently provides a window for proactive defense, but the potential for rapid weaponization is high.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify the presence of the Easy Timer plugin and verify the version in use. Since no official patch is available yet, organizations should consider the following specific mitigations: 1) Restrict Editor-level and higher privileges strictly to trusted personnel and review user roles to minimize the number of users with such access. 2) Implement Web Application Firewalls (WAFs) with custom rules to detect and block suspicious shortcode attribute patterns associated with code injection attempts. 3) Temporarily disable or remove the Easy Timer plugin until a secure patch is released. 4) Monitor server logs and WordPress activity for unusual behavior indicative of exploitation attempts. 5) Employ principle of least privilege on the server and WordPress environment to limit the impact of potential code execution. 6) Keep WordPress core and all other plugins updated to reduce the overall attack surface. 7) Prepare incident response plans specifically addressing potential RCE scenarios to enable rapid containment and recovery.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-08-26T23:53:17.887Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68b91670ad5a09ad00011cd9

Added to database: 9/4/2025, 4:32:48 AM

Last enriched: 9/4/2025, 4:47:45 AM

Last updated: 9/4/2025, 2:09:19 PM

Views: 4

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats