Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-434 (危险类型文件的不加限制上传) — Vulnerability Class 2034

2034 vulnerabilities classified as CWE-434 (危险类型文件的不加限制上传). AI Chinese analysis included.

CWE-434 represents a critical input validation weakness where applications permit the upload of file types that are inherently dangerous or automatically processed by the system. Attackers typically exploit this vulnerability by uploading malicious scripts, such as web shells or executable binaries, disguised as legitimate documents or images. Once uploaded, these files are executed by the server, granting the attacker remote code execution capabilities and potentially full system compromise. To mitigate this risk, developers must implement strict allowlists that define only the specific, safe file extensions permitted for upload. Additionally, files should be stored outside the web root directory to prevent direct execution, and content verification techniques, such as checking file headers rather than relying solely on extensions, should be employed to ensure integrity and prevent evasion of basic validation checks.

MITRE CWE Description
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Common Consequences (1)
Integrity, Confidentiality, AvailabilityExecute Unauthorized Code or Commands
Arbitrary code execution is possible if an uploaded file is interpreted and executed as code by the recipient. This is especially true for web-server extensions such as .asp and .php because these file types are often treated as automatically executable, even when file system permissions do not spec…
Mitigations (5)
Architecture and DesignGenerate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.[REF-422] [REF-423]
Architecture and DesignWhen the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and DesignConsider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically. [REF-423]
ImplementationAssume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Architecture and DesignDefine a very limited set of allowable extensions and only generate filenames that end in these extensions. Consider the possibility of XSS (CWE-79) before allowing .html or .htm file types.
Examples (2)
The following code intends to allow a user to upload a picture to the web server. The HTML code that drives the form on the user end has an input field of type "file".
<form action="upload_picture.php" method="post" enctype="multipart/form-data"> Choose a file to upload: <input type="file" name="filename"/> <br/> <input type="submit" name="submit" value="Submit"/> </form>
Good · HTML
// Define the target location where the picture being // uploaded is going to be saved. $target = "pictures/" . basename($_FILES['uploadedfile']['name']); // Move the uploaded file to the new location. if(move_uploaded_file($_FILES['uploadedfile']['tmp_name'], $target)) { echo "The picture has been successfully uploaded."; } else { echo "There was an error uploading the picture, please try again."; }
Bad · PHP
The following code demonstrates the unrestricted upload of a file with a Java servlet and a path traversal vulnerability. The action attribute of an HTML form is sending the upload file request to the Java servlet.
<form action="FileUploadServlet" method="post" enctype="multipart/form-data"> Choose a file to upload: <input type="file" name="filename"/> <br/> <input type="submit" name="submit" value="Submit"/> </form>
Good · HTML
public class FileUploadServlet extends HttpServlet { ... protected void doPost(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { response.setContentType("text/html"); PrintWriter out = response.getWriter(); String contentType = request.getContentType(); // the starting position of the boundary header int ind = contentType.indexOf("boundary="); String boundary = contentType.substring(ind+9); String pLine = new String(); String uploadLocation = new String(UPLOAD_DIRECTORY_STRING); //Constant value // verify that content type is multipart form data i
Bad · Java
CVE IDTitleCVSSSeverityPublished
CVE-2015-10144 Responsive Thumbnail Slider < 1.0.1 - Authenticated (Subscriber+) Arbitrary File Upload — Thumbnail carousel slider 8.8 High2025-07-25
CVE-2025-5243 Arbitrary File Upload in SMG Software's Information Portal — Information Portal 10.0 Critical2025-07-24
CVE-2025-7437 Ebook Store <= 5.8012 - Unauthenticated Arbitrary File Upload — Ebook Store 9.8 Critical2025-07-24
CVE-2025-7852 WPBookit <= 1.0.6 - Unauthenticated Arbitrary File Upload via image_upload_handle Function — WPBookit 9.8 Critical2025-07-24
CVE-2018-25114 osCommerce 2.3.4.1 Installer Unauthenticated Configuration File Injection PHP Code Execution — Online Merchant 9.8 -2025-07-23
CVE-2025-40599 SonicWALL SMA 代码问题漏洞 — SMA 100 Series 7.2 -2025-07-23
CVE-2025-54439 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 8.8 High2025-07-23
CVE-2025-54444 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.8 Critical2025-07-23
CVE-2025-54442 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.8 Critical2025-07-23
CVE-2025-54441 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 8.8 High2025-07-23
CVE-2025-54440 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.8 Critical2025-07-23
CVE-2025-54447 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 8.1 High2025-07-23
CVE-2025-54448 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.8 Critical2025-07-23
CVE-2025-54449 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.8 Critical2025-07-23
CVE-2012-10020 FoxyPress <= 0.4.2.1 - Arbitrary File Upload — FoxyPress 9.8 Critical2025-07-22
CVE-2015-10137 Website Contact Form With File Upload <= 1.3.4 - Arbitrary File Upload — Website Contact Form With File Upload 9.8 Critical2025-07-22
CVE-2025-7939 jerryshensjf JPACookieShop 蛋糕商城JPA版 GoodsController.java addGoods unrestricted upload — JPACookieShop 蛋糕商城JPA版 6.3 Medium2025-07-21
CVE-2025-54071 RomM's authenticated arbitrary file write vulnerability can lead to Remote Code Execution — romm 8.8 -2025-07-21
CVE-2025-7931 code-projects Church Donation System admin_pic.php unrestricted upload — Church Donation System 7.3 High2025-07-21
CVE-2025-32744 Dell AppSync 代码问题漏洞 — AppSync 6.6 Medium2025-07-21
CVE-2025-54082 nova-tiptap has an Unauthenticated Arbitrary File Upload Vulnerability — nova-tiptap 8.6 -2025-07-21
CVE-2025-7917 Simopro Technology|WinMatrix3 Web package - Arbitrary File Upload — WinMatrix3 Web package 7.2 High2025-07-21
CVE-2025-7906 yangzongzhuan RuoYi CommonController.java uploadFile unrestricted upload — RuoYi 6.3 Medium2025-07-20
CVE-2025-7898 Codecanyon iDentSoft Account Setting Page updateSetting unrestricted upload — iDentSoft 4.7 Medium2025-07-20
CVE-2025-46384 Emby Windows 代码问题漏洞 — Windows 8.8 High2025-07-20
CVE-2025-7895 harry0703 MoneyPrinterTurbo File Extension video.py upload_bgm_file unrestricted upload — MoneyPrinterTurbo 6.3 Medium2025-07-20
CVE-2025-7880 Metasoft 美特软件 MetaCRM sendsms.jsp unrestricted upload — MetaCRM 6.3 Medium2025-07-20
CVE-2025-7879 Metasoft 美特软件 MetaCRM mobileupload.jsp unrestricted upload — MetaCRM 6.3 Medium2025-07-20
CVE-2025-7878 Metasoft 美特软件 MetaCRM upload2.jsp unrestricted upload — MetaCRM 6.3 Medium2025-07-20
CVE-2025-7877 Metasoft 美特软件 MetaCRM sendfile.jsp unrestricted upload — MetaCRM 6.3 Medium2025-07-20

Vulnerabilities classified as CWE-434 (危险类型文件的不加限制上传) represent 2034 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.