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-12165: CWE-862 Missing Authorization in huyme Webcake – Landing Page Builder

0
Medium
VulnerabilityCVE-2025-12165cvecve-2025-12165cwe-862
Published: Fri Dec 05 2025 (12/05/2025, 05:31:22 UTC)
Source: CVE Database V5
Vendor/Project: huyme
Product: Webcake – Landing Page Builder

Description

The Webcake – Landing Page Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'webcake_save_config' AJAX endpoint in all versions up to, and including, 1.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify the plugin's settings.

AI-Powered Analysis

AILast updated: 12/05/2025, 06:04:19 UTC

Technical Analysis

CVE-2025-12165 identifies a missing authorization vulnerability (CWE-862) in the Webcake – Landing Page Builder plugin for WordPress, specifically in the 'webcake_save_config' AJAX endpoint. This endpoint lacks proper capability checks, allowing authenticated users with Subscriber-level access or above to modify plugin settings without appropriate permissions. The vulnerability affects all versions up to and including 1.1. The flaw arises because the plugin fails to verify whether the requesting user has the necessary privileges before processing configuration changes, violating the principle of least privilege. The CVSS v3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based (remote), requires low privileges (authenticated user), no user interaction is needed, and the impact is limited to integrity (unauthorized modification of plugin settings) without affecting confidentiality or availability. There are no known exploits in the wild, and no patches have been published at the time of disclosure. This vulnerability could be leveraged by malicious insiders or compromised low-privilege accounts to alter landing page configurations, potentially redirecting traffic, injecting malicious content, or disrupting marketing campaigns. Since WordPress is widely used across Europe, and this plugin is designed for landing page creation, the risk is relevant for organizations relying on it for web marketing and customer engagement.

Potential Impact

For European organizations, the primary impact of CVE-2025-12165 lies in the unauthorized modification of landing page configurations, which can undermine the integrity of web content and marketing efforts. Attackers with Subscriber-level access could alter plugin settings to redirect visitors to malicious sites, inject fraudulent content, or disrupt legitimate campaigns, potentially damaging brand reputation and customer trust. While the vulnerability does not directly expose sensitive data or cause service outages, the indirect consequences include phishing risks, loss of customer confidence, and potential regulatory scrutiny under data protection laws if customer interactions are compromised. Organizations with large WordPress deployments and multiple user roles are particularly at risk, as the attack surface includes any authenticated user with minimal privileges. The absence of known exploits reduces immediate risk, but the ease of exploitation once an attacker gains low-level access makes timely mitigation critical. Additionally, the vulnerability could be chained with other weaknesses to escalate attacks.

Mitigation Recommendations

To mitigate CVE-2025-12165, European organizations should implement the following specific measures: 1) Immediately audit all WordPress sites using the Webcake – Landing Page Builder plugin to identify affected versions (up to 1.1). 2) Restrict user roles and permissions rigorously, ensuring that Subscriber-level accounts are limited and monitored, and consider temporarily disabling or removing unnecessary Subscriber accounts. 3) Monitor and log all AJAX requests to the 'webcake_save_config' endpoint to detect unauthorized modification attempts. 4) Apply patches or updates from the vendor as soon as they become available; if no patch exists, consider disabling the plugin or replacing it with a secure alternative. 5) Implement Web Application Firewall (WAF) rules to restrict access to the vulnerable AJAX endpoint to authorized users only. 6) Educate site administrators about the risk and encourage strong authentication practices to reduce the likelihood of account compromise. 7) Conduct regular security reviews of WordPress plugins and their permission models to prevent similar issues.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-24T14:16:57.300Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69327172f88dbe026c77991e

Added to database: 12/5/2025, 5:45:22 AM

Last enriched: 12/5/2025, 6:04:19 AM

Last updated: 12/10/2025, 10:03:12 AM

Views: 11

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