Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-12813: CWE-94 Improper Control of Generation of Code ('Code Injection') in strix-bubol5 Holiday class post calendar

0
Critical
VulnerabilityCVE-2025-12813cvecve-2025-12813cwe-94
Published: Tue Nov 11 2025 (11/11/2025, 03:30:43 UTC)
Source: CVE Database V5
Vendor/Project: strix-bubol5
Product: Holiday class post calendar

Description

The Holiday class post calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 7.1 via the 'contents' parameter. This is due to a lack of sanitization of user-supplied data when creating a cache file. This makes it possible for unauthenticated attackers to execute code on the server.

AI-Powered Analysis

AILast updated: 11/18/2025, 04:24:34 UTC

Technical Analysis

CVE-2025-12813 is a critical remote code execution (RCE) vulnerability found in the Holiday class post calendar plugin for WordPress, developed by strix-bubol5. The vulnerability affects all versions up to and including 7.1. It stems from improper control over code generation (CWE-94), specifically due to a lack of sanitization of user-supplied input passed via the 'contents' parameter. When this parameter is used to create a cache file, malicious input can be injected, allowing an attacker to execute arbitrary code on the server hosting the WordPress site. The vulnerability requires no authentication or user interaction, making it highly exploitable remotely over the network. The CVSS v3.1 base score is 9.8, reflecting the critical impact on confidentiality, integrity, and availability. Exploitation could lead to complete server takeover, data exfiltration, defacement, or deployment of further malware. No patches or updates are currently available, and no known exploits have been reported in the wild yet. The vulnerability was publicly disclosed on November 11, 2025, with the CVE reserved a few days earlier. The plugin is widely used in WordPress environments, often on public-facing websites, increasing the attack surface. The lack of input validation and sanitization is a common security flaw that can be mitigated by proper coding practices. Until a patch is released, organizations must rely on defensive measures such as web application firewalls, monitoring, and restricting access to vulnerable components.

Potential Impact

For European organizations, this vulnerability poses a severe threat due to the widespread use of WordPress and its plugins across various sectors including e-commerce, media, education, and government websites. Successful exploitation could lead to full server compromise, allowing attackers to steal sensitive data, disrupt services, or use compromised servers as a foothold for lateral movement within networks. The unauthenticated nature of the exploit increases the risk of automated mass scanning and exploitation campaigns targeting vulnerable sites. This could result in reputational damage, regulatory penalties under GDPR due to data breaches, and significant operational downtime. Organizations hosting customer data or critical services on affected WordPress installations are especially at risk. The impact extends beyond the initial compromise, as attackers could deploy ransomware or persistent backdoors. Given the critical CVSS score and ease of exploitation, the threat level for European entities is high, necessitating immediate action to prevent exploitation.

Mitigation Recommendations

1. Monitor official sources and the plugin vendor for patches or updates and apply them immediately once available. 2. In the absence of a patch, disable or remove the Holiday class post calendar plugin from all WordPress installations to eliminate the attack vector. 3. Deploy and configure web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'contents' parameter, focusing on suspicious code injection patterns. 4. Conduct thorough input validation and sanitization on all user-supplied data in custom or third-party plugins to prevent similar vulnerabilities. 5. Implement network segmentation to isolate web servers from critical internal systems, limiting lateral movement if compromise occurs. 6. Enable detailed logging and monitor for unusual file creation, modification, or execution activities that could indicate exploitation attempts. 7. Educate website administrators on the risks of using outdated or untrusted plugins and encourage regular security audits. 8. Consider deploying runtime application self-protection (RASP) tools to detect and block exploitation attempts in real time. 9. Review backup and incident response plans to ensure rapid recovery in case of compromise. 10. Restrict administrative access to WordPress dashboards via IP whitelisting or VPN to reduce exposure.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-06T16:32:17.929Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6912b13414bc3e00ba783de2

Added to database: 11/11/2025, 3:44:52 AM

Last enriched: 11/18/2025, 4:24:34 AM

Last updated: 12/26/2025, 7:52:10 AM

Views: 102

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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