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.
5995 vulnerabilities reference this CWE, most recent first.
GHSA-J8V2-M2F3-8JGF
Vulnerability from github – Published: 2023-12-15 12:30 – Updated: 2023-12-15 12:30Kaifa Technology WebITR is an online attendance system, its file uploading function does not restrict upload of file with dangerous type. A remote attacker with regular user privilege can exploit this vulnerability to upload arbitrary files to perform arbitrary command or disrupt service.
{
"affected": [],
"aliases": [
"CVE-2023-48394"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-12-15T10:15:08Z",
"severity": "HIGH"
},
"details": "Kaifa Technology WebITR is an online attendance system, its file uploading function does not restrict upload of file with dangerous type. A remote attacker with regular user privilege can exploit this vulnerability to upload arbitrary files to perform arbitrary command or disrupt service.",
"id": "GHSA-j8v2-m2f3-8jgf",
"modified": "2023-12-15T12:30:24Z",
"published": "2023-12-15T12:30:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-48394"
},
{
"type": "WEB",
"url": "https://www.twcert.org.tw/tw/cp-132-7624-d0300-1.html"
}
],
"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-J8WP-62VQ-268H
Vulnerability from github – Published: 2023-03-06 09:30 – Updated: 2023-03-13 18:30A vulnerability, which was classified as problematic, was found in ECshop up to 4.1.8. This affects an unknown part of the component New Product Handler. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-222357 was assigned to this vulnerability.
{
"affected": [],
"aliases": [
"CVE-2023-1185"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-06T08:15:00Z",
"severity": "HIGH"
},
"details": "A vulnerability, which was classified as problematic, was found in ECshop up to 4.1.8. This affects an unknown part of the component New Product Handler. The manipulation leads to unrestricted upload. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-222357 was assigned to this vulnerability.",
"id": "GHSA-j8wp-62vq-268h",
"modified": "2023-03-13T18:30:41Z",
"published": "2023-03-06T09:30:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1185"
},
{
"type": "WEB",
"url": "https://github.com/wjzdalao/ecshop4.1.8/issues/2"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.222357"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.222357"
}
],
"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-J93Q-24G6-27R6
Vulnerability from github – Published: 2022-05-24 17:36 – Updated: 2022-05-24 17:36The contact-form-7 (aka Contact Form 7) plugin before 5.3.2 for WordPress allows Unrestricted File Upload and remote code execution because a filename may contain special characters.
{
"affected": [],
"aliases": [
"CVE-2020-35489"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-12-17T19:15:00Z",
"severity": "CRITICAL"
},
"details": "The contact-form-7 (aka Contact Form 7) plugin before 5.3.2 for WordPress allows Unrestricted File Upload and remote code execution because a filename may contain special characters.",
"id": "GHSA-j93q-24g6-27r6",
"modified": "2022-05-24T17:36:47Z",
"published": "2022-05-24T17:36:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-35489"
},
{
"type": "WEB",
"url": "https://contactform7.com/2020/12/17/contact-form-7-532"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/contact-form-7/#developers"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/10508"
},
{
"type": "WEB",
"url": "https://www.getastra.com/blog/911/plugin-exploit/contact-form-7-unrestricted-file-upload"
},
{
"type": "WEB",
"url": "https://www.jinsonvarghese.com/unrestricted-file-upload-in-contact-form-7"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-J9G6-VVR6-X5WM
Vulnerability from github – Published: 2024-11-07 18:31 – Updated: 2025-07-23 21:36There exists an auth bypass in Google Quickshare where an attacker can upload an unknown file type to a victim. The root cause of the vulnerability lies in the fact that when a Payload Transfer frame of type FILE is sent to Quick Share, the file that is contained in this frame is written to disk in the Downloads folder. Quickshare normally deletes unkown files, however an attacker can send two Payload transfer frames of type FILE and the same payload ID. The deletion logic will only delete the first file and not the second. We recommend upgrading past commit 5d8b9156e0c339d82d3dab0849187e8819ad92c0 or Quick Share Windows v1.0.2002.2
{
"affected": [],
"aliases": [
"CVE-2024-10668"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-11-07T16:15:16Z",
"severity": "MODERATE"
},
"details": "There exists an auth bypass in Google Quickshare where an attacker can upload an unknown file type to a victim.\u00a0The root cause of the vulnerability lies in the fact that when a Payload Transfer frame of type FILE is sent to Quick Share, the file that is contained in this frame is written to disk in the Downloads folder. Quickshare normally deletes unkown files, however an attacker can send two Payload transfer frames of type FILE and the same payload ID. The deletion logic will only delete the first file and not the second. We recommend upgrading past commit\u00a05d8b9156e0c339d82d3dab0849187e8819ad92c0 or\u00a0Quick Share Windows v1.0.2002.2",
"id": "GHSA-j9g6-vvr6-x5wm",
"modified": "2025-07-23T21:36:43Z",
"published": "2024-11-07T18:31:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10668"
},
{
"type": "WEB",
"url": "https://github.com/google/nearby/pull/2892"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:A/VC:L/VI:H/VA:L/SC:L/SI:H/SA:L/E:X/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:N/R:U/V:D/RE:L/U:Green",
"type": "CVSS_V4"
}
]
}
GHSA-J9H9-46CG-GWP9
Vulnerability from github – Published: 2024-09-18 21:30 – Updated: 2024-09-19 21:33Dedecms V5.7.115 contains an arbitrary code execution via file upload vulnerability in the backend.
{
"affected": [],
"aliases": [
"CVE-2024-46373"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-09-18T21:15:13Z",
"severity": "HIGH"
},
"details": "Dedecms V5.7.115 contains an arbitrary code execution via file upload vulnerability in the backend.",
"id": "GHSA-j9h9-46cg-gwp9",
"modified": "2024-09-19T21:33:29Z",
"published": "2024-09-18T21:30:48Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-46373"
},
{
"type": "WEB",
"url": "https://github.com/gaorenyusi/gaorenyusi/blob/main/CVE-2024-46373.md"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-J9P2-56J2-2M84
Vulnerability from github – Published: 2022-06-22 00:00 – Updated: 2022-06-30 00:00An arbitrary file upload vulnerability /images/background/1.php in of SolarView Compact 6.0 allows attackers to execute arbitrary code via a crafted php file.
{
"affected": [],
"aliases": [
"CVE-2022-31374"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-06-21T13:15:00Z",
"severity": "CRITICAL"
},
"details": "An arbitrary file upload vulnerability /images/background/1.php in of SolarView Compact 6.0 allows attackers to execute arbitrary code via a crafted php file.",
"id": "GHSA-j9p2-56j2-2m84",
"modified": "2022-06-30T00:00:42Z",
"published": "2022-06-22T00:00:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31374"
},
{
"type": "WEB",
"url": "https://github.com/badboycxcc/SolarView_Compact_6.0_upload"
}
],
"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-J9QG-6QFP-WH76
Vulnerability from github – Published: 2022-05-14 03:47 – Updated: 2022-05-14 03:47Unrestricted file upload vulnerability in the Gravity Upload Ajax plugin 1.1 and earlier for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file under wp-content/uploads/gravity_forms.
{
"affected": [],
"aliases": [
"CVE-2014-4972"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-01-08T19:29:00Z",
"severity": "CRITICAL"
},
"details": "Unrestricted file upload vulnerability in the Gravity Upload Ajax plugin 1.1 and earlier for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file under wp-content/uploads/gravity_forms.",
"id": "GHSA-j9qg-6qfp-wh76",
"modified": "2022-05-14T03:47:21Z",
"published": "2022-05-14T03:47:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-4972"
},
{
"type": "WEB",
"url": "https://g0blin.co.uk/cve-2014-4972"
},
{
"type": "WEB",
"url": "https://wpvulndb.com/vulnerabilities/8232"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-J9W2-JFQJ-7XHR
Vulnerability from github – Published: 2022-02-15 00:02 – Updated: 2022-02-24 00:01An issue in the getType function of BBS Forum v5.3 and below allows attackers to upload arbitrary files.
{
"affected": [],
"aliases": [
"CVE-2022-23390"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-02-14T21:15:00Z",
"severity": "CRITICAL"
},
"details": "An issue in the getType function of BBS Forum v5.3 and below allows attackers to upload arbitrary files.",
"id": "GHSA-j9w2-jfqj-7xhr",
"modified": "2022-02-24T00:01:11Z",
"published": "2022-02-15T00:02:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-23390"
},
{
"type": "WEB",
"url": "https://github.com/diyhi/bbs/issues/51"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-JC44-GWJ5-3HQM
Vulnerability from github – Published: 2022-06-24 00:00 – Updated: 2024-03-21 03:34** UNSUPPORTED WHEN ASSIGNED ** Docebo Community Edition v4.0.5 and below was discovered to contain an arbitrary file upload vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
{
"affected": [],
"aliases": [
"CVE-2022-31362"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-06-23T17:15:00Z",
"severity": "HIGH"
},
"details": "** UNSUPPORTED WHEN ASSIGNED ** Docebo Community Edition v4.0.5 and below was discovered to contain an arbitrary file upload vulnerability. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.",
"id": "GHSA-jc44-gwj5-3hqm",
"modified": "2024-03-21T03:34:14Z",
"published": "2022-06-24T00:00:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-31362"
},
{
"type": "WEB",
"url": "https://blog.formalms.org/about/blog/20-life-after-docebo-the-forma-project-begins.html"
},
{
"type": "WEB",
"url": "https://www.swascan.com/security-advisory-docebo-community-edition"
}
],
"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-JC76-CG2Q-PP7H
Vulnerability from github – Published: 2025-07-20 15:30 – Updated: 2025-07-20 15:30CWE-434 Unrestricted Upload of File with Dangerous Type
{
"affected": [],
"aliases": [
"CVE-2025-46384"
],
"database_specific": {
"cwe_ids": [
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-07-20T15:15:24Z",
"severity": "HIGH"
},
"details": "CWE-434 Unrestricted Upload of File with Dangerous Type",
"id": "GHSA-jc76-cg2q-pp7h",
"modified": "2025-07-20T15:30:28Z",
"published": "2025-07-20T15:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46384"
},
{
"type": "WEB",
"url": "https://www.gov.il/en/departments/dynamiccollectors/cve_advisories_listing?skip=0"
}
],
"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"
}
]
}
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.