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-15158: CWE-434 Unrestricted Upload of File with Dangerous Type in eastsidecode WP Enable WebP

0
High
VulnerabilityCVE-2025-15158cvecve-2025-15158cwe-434
Published: Wed Jan 07 2026 (01/07/2026, 08:21:56 UTC)
Source: CVE Database V5
Vendor/Project: eastsidecode
Product: WP Enable WebP

Description

The WP Enable WebP plugin for WordPress is vulnerable to arbitrary file uploads due to improper file type validation in the 'wpse_file_and_ext_webp' function in all versions up to, and including, 1.0. This makes it possible for authenticated attackers, with Author-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

AI-Powered Analysis

AILast updated: 01/07/2026, 08:51:25 UTC

Technical Analysis

CVE-2025-15158 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) found in the WP Enable WebP plugin for WordPress, developed by eastsidecode. The vulnerability arises from insufficient validation of file types in the 'wpse_file_and_ext_webp' function, which fails to properly restrict the types of files that authenticated users can upload. This flaw affects all versions up to and including 1.0 of the plugin. An attacker with Author-level privileges or higher can exploit this vulnerability to upload arbitrary files to the server hosting the WordPress site. Since the plugin does not adequately verify file extensions or content, malicious files such as web shells or scripts can be uploaded, potentially enabling remote code execution (RCE). The vulnerability does not require user interaction beyond the attacker's own authenticated session, and the attack vector is network-based with low complexity. The CVSS v3.1 score of 8.8 reflects the high impact on confidentiality, integrity, and availability, as successful exploitation could lead to full server compromise. Although no exploits are currently known in the wild, the vulnerability poses a significant risk to WordPress sites using this plugin, especially those with multiple users having elevated permissions. The lack of a patch at the time of reporting increases the urgency for mitigation and monitoring.

Potential Impact

For European organizations, the impact of CVE-2025-15158 can be severe. Many businesses and institutions rely on WordPress for their web presence, and plugins like WP Enable WebP are commonly used to optimize image delivery. An attacker exploiting this vulnerability could gain unauthorized access to upload malicious files, leading to remote code execution, data breaches, defacement, or service disruption. This could compromise sensitive customer data, intellectual property, and operational continuity. The breach could also damage organizational reputation and lead to regulatory penalties under GDPR if personal data is exposed. Organizations with multi-author WordPress environments are particularly vulnerable, as the attack requires only Author-level access, which is commonly granted to content creators or editors. The vulnerability could be leveraged as a foothold for lateral movement within corporate networks, increasing the risk of broader compromise. Given the high CVSS score and potential for full server takeover, the threat is critical for European entities hosting WordPress sites with this plugin.

Mitigation Recommendations

1. Immediately audit WordPress sites to identify installations of the WP Enable WebP plugin and determine the version in use. 2. Restrict Author-level and higher privileges to trusted users only, minimizing the number of accounts that can exploit this vulnerability. 3. Implement strict file upload monitoring and filtering on the web server and application level to detect and block suspicious or executable files. 4. Use web application firewalls (WAFs) with custom rules to detect anomalous upload patterns or attempts to upload unauthorized file types. 5. Disable or remove the WP Enable WebP plugin if it is not essential, or replace it with alternative plugins that have been verified as secure. 6. Monitor server logs and WordPress audit trails for unusual file uploads or changes indicative of exploitation attempts. 7. Prepare to apply vendor patches or updates as soon as they become available and test them in a staging environment before deployment. 8. Educate site administrators and content creators about the risks of elevated privileges and the importance of secure credential management. 9. Consider implementing multi-factor authentication (MFA) for WordPress accounts to reduce the risk of credential compromise. 10. Regularly back up website data and server configurations to enable rapid recovery in case of compromise.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-27T19:08:50.291Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695e1b30a55ed4ed998cb6a7

Added to database: 1/7/2026, 8:37:04 AM

Last enriched: 1/7/2026, 8:51:25 AM

Last updated: 1/8/2026, 12:36:33 PM

Views: 22

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats