CWE-434
AllowedUnrestricted Upload of File with Dangerous Type
Abstraction: Base · Status: Draft
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
5966 vulnerabilities reference this CWE, most recent first.
GHSA-WJXV-CCW6-J9XH
Vulnerability from github – Published: 2022-05-24 19:14 – Updated: 2022-05-24 19:14The shopp_upload_file AJAX action of the Shopp WordPress plugin through 1.4, available to both unauthenticated and authenticated user does not have any security measure in place to prevent upload of malicious files, such as PHP, allowing unauthenticated users to upload arbitrary files and leading to RCE
{
"affected": [],
"aliases": [
"CVE-2021-24493"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-09-13T18:15:00Z",
"severity": "CRITICAL"
},
"details": "The shopp_upload_file AJAX action of the Shopp WordPress plugin through 1.4, available to both unauthenticated and authenticated user does not have any security measure in place to prevent upload of malicious files, such as PHP, allowing unauthenticated users to upload arbitrary files and leading to RCE",
"id": "GHSA-wjxv-ccw6-j9xh",
"modified": "2022-05-24T19:14:19Z",
"published": "2022-05-24T19:14:19Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-24493"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/dcc7be04-550b-427a-a14f-a2365d96a00e"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-WMHJ-JQ93-J3P7
Vulnerability from github – Published: 2023-05-08 15:30 – Updated: 2024-04-04 03:50OS Command injection vulnerability in mblog 3.5.0 allows attackers to execute arbitrary code via crafted theme when it gets selected.
{
"affected": [],
"aliases": [
"CVE-2021-27280"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-05-08T14:15:10Z",
"severity": "HIGH"
},
"details": "OS Command injection vulnerability in mblog 3.5.0 allows attackers to execute arbitrary code via crafted theme when it gets selected.",
"id": "GHSA-wmhj-jq93-j3p7",
"modified": "2024-04-04T03:50:31Z",
"published": "2023-05-08T15:30:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-27280"
},
{
"type": "WEB",
"url": "https://github.com/langhsu/mblog/issues/44"
},
{
"type": "WEB",
"url": "https://github.com/langhsu/mblog"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WMQF-W969-FG83
Vulnerability from github – Published: 2025-09-26 09:31 – Updated: 2026-04-01 18:36Unrestricted Upload of File with Dangerous Type vulnerability in HaruTheme WooCommerce Designer Pro allows Upload a Web Shell to a Web Server. This issue affects WooCommerce Designer Pro: from n/a through 1.9.24.
{
"affected": [],
"aliases": [
"CVE-2025-60219"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-09-26T09:15:48Z",
"severity": "CRITICAL"
},
"details": "Unrestricted Upload of File with Dangerous Type vulnerability in HaruTheme WooCommerce Designer Pro allows Upload a Web Shell to a Web Server. This issue affects WooCommerce Designer Pro: from n/a through 1.9.24.",
"id": "GHSA-wmqf-w969-fg83",
"modified": "2026-04-01T18:36:23Z",
"published": "2025-09-26T09:31:14Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-60219"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/wc-designer-pro/vulnerability/wordpress-woocommerce-designer-pro-plugin-1-9-24-arbitrary-file-upload-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WP5G-24XX-JCG4
Vulnerability from github – Published: 2022-12-12 03:31 – Updated: 2022-12-12 21:31SENS v1.0 has a file upload vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-45759"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-12-12T03:15:00Z",
"severity": "HIGH"
},
"details": "SENS v1.0 has a file upload vulnerability.",
"id": "GHSA-wp5g-24xx-jcg4",
"modified": "2022-12-12T21:31:08Z",
"published": "2022-12-12T03:31:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-45759"
},
{
"type": "WEB",
"url": "https://github.com/saysky/SENS/issues/20"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WP68-XRFG-XVQ4
Vulnerability from github – Published: 2025-02-05 06:30 – Updated: 2025-02-05 21:28Versions of the package cockpit-hq/cockpit before 2.4.1 are vulnerable to Arbitrary File Upload where an attacker can use different extension to bypass the upload filter.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "cockpit-hq/cockpit"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.4.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-1025"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": true,
"github_reviewed_at": "2025-02-05T21:28:44Z",
"nvd_published_at": "2025-02-05T05:15:10Z",
"severity": "HIGH"
},
"details": "Versions of the package cockpit-hq/cockpit before 2.4.1 are vulnerable to Arbitrary File Upload where an attacker can use different extension to bypass the upload filter.",
"id": "GHSA-wp68-xrfg-xvq4",
"modified": "2025-02-05T21:28:44Z",
"published": "2025-02-05T06:30:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1025"
},
{
"type": "WEB",
"url": "https://github.com/Cockpit-HQ/Cockpit/commit/984ef9ad270357b843af63c81db95178eae42cae"
},
{
"type": "WEB",
"url": "https://github.com/Cockpit-HQ/Cockpit/commit/becca806c7071ecc732521bb5ad0bb9c64299592"
},
{
"type": "WEB",
"url": "https://gist.github.com/CHOOCS/fe1227443544d5d74c33982814f290af"
},
{
"type": "PACKAGE",
"url": "https://github.com/Cockpit-HQ/Cockpit"
},
{
"type": "WEB",
"url": "https://security.snyk.io/vuln/SNYK-PHP-COCKPITHQCOCKPIT-8516320"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
],
"summary": "Cockpit Arbitrary File Upload"
}
GHSA-WPGG-QFWQ-FWJ4
Vulnerability from github – Published: 2024-04-16 18:31 – Updated: 2024-11-06 18:31Phpgurukul Tourism Management System v2.0 is vulnerable to Unrestricted Upload of File with Dangerous Type via tms/admin/create-package.php. When creating a new package, there is no checks for what types of files are uploaded from the image.
{
"affected": [],
"aliases": [
"CVE-2024-32254"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-04-16T17:15:10Z",
"severity": "HIGH"
},
"details": "Phpgurukul Tourism Management System v2.0 is vulnerable to Unrestricted Upload of File with Dangerous Type via tms/admin/create-package.php. When creating a new package, there is no checks for what types of files are uploaded from the image.",
"id": "GHSA-wpgg-qfwq-fwj4",
"modified": "2024-11-06T18:31:04Z",
"published": "2024-04-16T18:31:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-32254"
},
{
"type": "WEB",
"url": "https://github.com/jinhaochan/CVE-POC/blob/main/tms/POC.md"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WPH3-VQ9M-Q946
Vulnerability from github – Published: 2024-11-16 06:30 – Updated: 2025-07-09 21:30The Backup and Staging by WP Time Capsule plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the the UploadHandler.php file and no direct file access prevention in all versions up to, and including, 1.22.21. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
{
"affected": [],
"aliases": [
"CVE-2024-8856"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-16T05:15:13Z",
"severity": "CRITICAL"
},
"details": "The Backup and Staging by WP Time Capsule plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the the UploadHandler.php file and no direct file access prevention in all versions up to, and including, 1.22.21. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site\u0027s server which may make remote code execution possible.",
"id": "GHSA-wph3-vq9m-q946",
"modified": "2025-07-09T21:30:59Z",
"published": "2024-11-16T06:30:41Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8856"
},
{
"type": "WEB",
"url": "https://hacked.be/posts/CVE-2024-8856"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wp-time-capsule/trunk/wp-tcapsule-bridge/upload/php/UploadHandler.php"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3188325"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026old=3153289%40wp-time-capsule\u0026new=3153289%40wp-time-capsule\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/fdc2de78-5601-461f-b2f0-c80b592ccb1b?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-WPPF-GQJ5-FC4F
Vulnerability from github – Published: 2025-03-05 18:31 – Updated: 2025-03-05 19:30Summary
An arbitrary file upload vulnerability was identified in the redaxo. This flaw permits users to upload malicious files, which can lead to JavaScript code execution and distribute malware.
Details
On the latest version of Redaxo, v5.18.2, the mediapool/media page is vulnerable to arbitrary file upload.
PoC
- Log in to the portal then navigate to
Mediapool. - Upload a png file (ex: poc.png)
- Intercept the upload HTTP request on burp suite and change
filename: poc.1html,Content-Type:image/htmland insert the malicious html code. (ex:<IFRAME SRC="javascript:alert(1);"></IFRAME>)
-
Forward the request.
-
Navigate to the file.
Impact
Exploiting an arbitrary file upload vulnerability enables attackers to execute malicious code on a server.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "redaxo/source"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.18.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-27411"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": true,
"github_reviewed_at": "2025-03-05T18:31:35Z",
"nvd_published_at": "2025-03-05T16:15:40Z",
"severity": "MODERATE"
},
"details": "### Summary\nAn arbitrary file upload vulnerability was identified in the redaxo. This flaw permits users to upload malicious files, which can lead to JavaScript code execution and distribute malware. \n\n### Details\nOn the latest version of Redaxo, v5.18.2, the mediapool/media page is vulnerable to arbitrary file upload.\n\n### PoC\n1. Log in to the portal then navigate to `Mediapool`.\n2. Upload a png file (ex: poc.png)\n\n\n\n\n3. Intercept the upload HTTP request on burp suite and change `filename: poc.1html`, `Content-Type:image/html` and insert the malicious html code. (ex: `\u003cIFRAME SRC=\"javascript:alert(1);\"\u003e\u003c/IFRAME\u003e`) \n\n\n\n4. Forward the request.\n\n5. Navigate to the file.\n\n\n\n\n\n### Impact\nExploiting an arbitrary file upload vulnerability enables attackers to execute malicious code on a server.",
"id": "GHSA-wppf-gqj5-fc4f",
"modified": "2025-03-05T19:30:37Z",
"published": "2025-03-05T18:31:35Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/redaxo/redaxo/security/advisories/GHSA-wppf-gqj5-fc4f"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-27411"
},
{
"type": "WEB",
"url": "https://github.com/redaxo/redaxo/commit/3b2159bb45da0ab6cfaef5c8cf8b602ee5e2fb37"
},
{
"type": "PACKAGE",
"url": "https://github.com/redaxo/redaxo"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "REDAXO allows Arbitrary File Upload in the mediapool page"
}
GHSA-WPPJ-3PJR-9W79
Vulnerability from github – Published: 2022-01-21 23:55 – Updated: 2022-01-20 15:08crater is vulnerable to Unrestricted Upload of File with Dangerous Type
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "bytefury/crater"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-4080"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": true,
"github_reviewed_at": "2022-01-20T15:08:18Z",
"nvd_published_at": "2022-01-12T14:15:00Z",
"severity": "HIGH"
},
"details": "crater is vulnerable to Unrestricted Upload of File with Dangerous Type",
"id": "GHSA-wppj-3pjr-9w79",
"modified": "2022-01-20T15:08:18Z",
"published": "2022-01-21T23:55:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-4080"
},
{
"type": "WEB",
"url": "https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d"
},
{
"type": "PACKAGE",
"url": "https://github.com/crater-invoice/crater"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/d7453360-baca-4e56-985f-481275fa38db"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "crater is vulnerable to Unrestricted Upload of File with Dangerous Type"
}
GHSA-WPR6-44Q6-C5G9
Vulnerability from github – Published: 2022-05-14 01:37 – Updated: 2022-05-14 01:37Unrestricted file upload (with remote code execution) in OCS Inventory NG ocsreports allows a privileged user to gain access to the server via crafted HTTP requests.
{
"affected": [],
"aliases": [
"CVE-2018-15537"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-11-29T21:29:00Z",
"severity": "HIGH"
},
"details": "Unrestricted file upload (with remote code execution) in OCS Inventory NG ocsreports allows a privileged user to gain access to the server via crafted HTTP requests.",
"id": "GHSA-wpr6-44q6-c5g9",
"modified": "2022-05-14T01:37:52Z",
"published": "2022-05-14T01:37:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-15537"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/150330/OCS-Inventory-NG-ocsreports-Shell-Upload.html"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2018/Nov/40"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation
Generate 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]
Mitigation MIT-21
Strategy: Enforcement by Conversion
When 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.
Mitigation
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically. [REF-423]
Mitigation MIT-5
Strategy: Input Validation
- Assume 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 of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- For example, limiting filenames to alphanumeric characters can help to restrict the introduction of unintended file extensions.
Mitigation
Define 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.
Mitigation
Strategy: Input Validation
Ensure that only one extension is used in the filename. Some web servers, including some versions of Apache, may process files based on inner extensions so that "filename.php.gif" is fed to the PHP interpreter.[REF-422] [REF-423]
Mitigation
When running on a web server that supports case-insensitive filenames, perform case-insensitive evaluations of the extensions that are provided.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation
Do not rely exclusively on sanity checks of file contents to ensure that the file is of the expected type and size. It may be possible for an attacker to hide code in some file segments that will still be executed by the server. For example, GIF images may contain a free-form comments field.
Mitigation
Do not rely exclusively on the MIME content type or filename attribute when determining how to render a file. Validating the MIME content type and ensuring that it matches the extension is only a partial solution.
Mitigation MIT-17
Strategy: Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Mitigation MIT-22
Strategy: Sandbox or Jail
- Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
- OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
- This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
- Be careful to avoid CWE-243 and other weaknesses related to jails.
CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.