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-13094: CWE-434 Unrestricted Upload of File with Dangerous Type in wp3d WP3D Model Import Viewer

0
High
VulnerabilityCVE-2025-13094cvecve-2025-13094cwe-434
Published: Sat Dec 13 2025 (12/13/2025, 04:31:23 UTC)
Source: CVE Database V5
Vendor/Project: wp3d
Product: WP3D Model Import Viewer

Description

The WP3D Model Import Viewer plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the handle_import_file() function in all versions up to, and including, 1.0.7. 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: 12/13/2025, 05:00:52 UTC

Technical Analysis

CVE-2025-13094 is a vulnerability classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) found in the WP3D Model Import Viewer plugin for WordPress. The vulnerability arises from the handle_import_file() function, which lacks proper validation of uploaded file types. This flaw allows authenticated users with Author-level privileges or higher to upload arbitrary files to the web server hosting the WordPress site. Since the plugin does not restrict file types, attackers can upload malicious scripts or executables, potentially leading to remote code execution (RCE). The vulnerability affects all versions up to and including 1.0.7. The CVSS v3.1 score of 8.8 reflects the ease of exploitation (network attack vector, low attack complexity, privileges required but no user interaction) and the severe impact on confidentiality, integrity, and availability of the affected systems. Although no exploits are publicly known yet, the vulnerability poses a significant risk because WordPress is widely used, and plugins often have elevated privileges on the server. Attackers gaining Author-level access can leverage this vulnerability to escalate privileges, implant backdoors, or disrupt services. The lack of patch links suggests a fix is pending or not yet publicly released, emphasizing the need for immediate mitigation steps.

Potential Impact

For European organizations, this vulnerability poses a critical risk, especially for those relying on WordPress for business-critical websites, e-commerce platforms, or content management. Successful exploitation can lead to full server compromise, data breaches, defacement, or service outages. Confidential information stored or processed by the website could be exposed or altered, damaging organizational reputation and compliance with GDPR and other data protection regulations. The ability to execute arbitrary code remotely increases the risk of lateral movement within internal networks, potentially affecting other systems. Organizations with multiple WordPress instances or those allowing Author-level user roles broadly are particularly vulnerable. The threat is amplified in sectors such as finance, healthcare, media, and government, where website integrity and data confidentiality are paramount. Additionally, the absence of public exploits currently provides a window for proactive defense, but this may close rapidly once exploit code becomes available.

Mitigation Recommendations

1. Immediately audit WordPress sites for the presence of the WP3D Model Import Viewer plugin and identify versions up to 1.0.7. 2. Restrict or remove Author-level user privileges where possible, limiting upload capabilities to trusted users only. 3. Implement strict file upload controls at the web server or application firewall level to block dangerous file types and extensions commonly used for code execution (e.g., .php, .exe, .js). 4. Monitor file upload directories for unexpected or suspicious files and implement integrity checks. 5. Employ web application firewalls (WAFs) with rules targeting arbitrary file upload attempts. 6. Keep WordPress core, themes, and plugins updated; apply security patches promptly once the vendor releases a fix for this vulnerability. 7. Conduct regular security audits and penetration tests focusing on plugin vulnerabilities and user privilege misuse. 8. Educate site administrators and content creators on the risks of elevated privileges and safe upload practices. 9. Consider isolating WordPress instances in segmented network zones to limit potential lateral movement. 10. Prepare incident response plans to quickly address any signs of compromise related to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-11-12T20:54:54.977Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 693cef64d977419e584a5018

Added to database: 12/13/2025, 4:45:24 AM

Last enriched: 12/13/2025, 5:00:52 AM

Last updated: 12/14/2025, 9:55:57 PM

Views: 14

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