In WhatsUp Gold versions released before 2026.0.2, a privileged attacker can create a LogToFile action specifying an arbitrary file extension within the IIS web root.
The giftware WordPress plugin before 4.2.10 does not validate the type of uploaded files in one of its upload paths, allowing unauthenticated users to upload arbitrary files, including PHP code, which can lead to remote code execution.
Malcolm is a network traffic analysis tool suite. The file-upload component (FilePond PHP backend) accepts uploads at `POST /server/php/submit.php` and stores them in a directory served by the same nginx and php-fpm instance. The allow-list that should restrict accepted file types is an empty array by default (`file-upload/php/config.php:16`), so the type check is a no-op and every extension is accepted. The filename sanitizer keeps the `.php` extension intact. Committed files land in `/var/www/upload/server/php/files` (`file-upload/php/config.php:7`), and the component's nginx routes any URL ending in `.php` to php-fpm. An authenticated `GET /server/php/files/<name>.php` then executes the uploaded code as `www-data`. Prior to version 26.06.1, in RBAC mode, the upload endpoint is reachable by the granular `ROLE_UPLOAD` role (`nginx/lua/nginx_auth_helpers.lua:71`), a role intended only for submitting capture files. As a result, a user holding the upload-only role runs arbitrary PHP as `www-data` inside the file-upload container. Version 26.06.1 fixes the issue.
The InstaWP Connect – 1-click WP Staging & Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 0.1.3.6 via the (top-level script) function. This is due to the plugin stores its encrypted options file as options-{migrate_key}.txt in wp-content/instawpbackups/ without deploying an index.php or .htaccess to prevent directory listing, exposing the 40-character migrate_key on Apache servers with directory indexing enabled, which allows an attacker to derive the AES-256-CBC passphrase via SHA256(migrate_key), decrypt the options file to recover the api_signature. This makes it possible for unauthenticated attackers to get the database access details and api_signature. Exploitation requires the target WordPress site to be hosted on Apache with directory listing enabled (Options +Indexes) for the wp-content/instawpbackups/ directory, and time limited because it can only be exploited during the migration period.
Fooocus is an image generating software. In versions 2.5.5 and prior, the Fooocus web UI is vulnerable to remote code execution due to the unsafe use of eval when processing metadata JSON. An attacker with access to the Fooocus web UI may be able to execute arbitrary code on the instance. As of time of publication, no known patched versions are available, but a suggested fix pull request is available.
dulldusk/phpfm versions through 1.8.0 contain an unrestricted file upload vulnerability that allows unauthenticated remote attackers to upload and execute arbitrary PHP code. The application has no default authentication and an empty upload extension filter, enabling attackers to upload PHP webshells and execute them by accessing the uploaded file path. This vulnerability is critical with a CVSS score of 9.8.
The Product Input Fields for WooCommerce WordPress plugin before 2.0.2 does not validate uploaded file types when its accepted-types setting is left empty, which its own documentation advertises as accepting all files, allowing unauthenticated attackers to upload arbitrary files and achieve remote code execution on servers that do not honour the directory's access rules.
The Squeeze WordPress plugin before 1.7.12 does not validate the file type or extension of the per-size image data written by one of its attachment-update actions, allowing users with the upload_files capability (Author and above) to write an executable PHP file into the uploads directory and achieve remote code execution.
Statamic CMS versions prior to 5.74.3 and 6.24.2 allowed unauthenticated users to upload file types via public frontend forms that were not properly restricted, bypassing the Control Panel's file upload restrictions. Although executable file types like .php and .html were blocked by a global allowlist, other disallowed file types could be uploaded and stored on a publicly accessible disk. This vulnerability is fixed in versions 5.74.3 and 6.24.2.
Dinky's POST /download/uploadFromRsByLocal handler passes the caller-supplied path parameter directly to new File(path) and file.transferTo(dest) with no path validation. The route is marked @SaIgnore and /download/** is excluded from the Sa-Token interceptor, so the only guard is a header equality check against a dinkyToken value whose default (efda1551-7958-4e0f-80a8-dfd107df3e38) is hardcoded in source and shipped to every deployment. Anyone who can reach Dinky's HTTP port (8888 by default) and supplies the hardcoded token can write arbitrary files as the Dinky service account. The default Docker image runs on 8888 with no proxy or authentication and chmod 777 on /opt/dinky, so the application's own classpath, launch scripts, and static assets are writable. Demonstrated impact: overwriting /opt/dinky/config/static/index.html served attacker JavaScript to admin browsers immediately, and writing /opt/dinky/org/dinky/Dinky.class executed attacker code as the Dinky service account at the next JVM start via a classpath-shadow launched by script/bin/auto.sh. Writes are uid 9999 (flink), not root, so /etc, /root, /home, and /usr are refused. Affects Dinky v1.2.5 (the current release) and the development branch, where the code is byte-identical.
A vulnerability was determined in SourceCodester Online Examination & Learning Management System 1.0. This issue affects some unknown processing of the file upload_files.php. This manipulation causes unrestricted upload. The attack may be initiated remotely.
The System REST API accepts user-supplied file uploads without enforcing sufficient validation on the file type or destination, allowing files to be written to arbitrary server-accessible locations. Exploitation requires authenticated administrative access with publisher privileges.
Successful exploitation permits an authenticated publisher to upload files to server-accessible locations. Depending on the deployment environment and how uploaded files are handled, this could lead to the execution of uploaded content, potentially resulting in remote code execution.
A vulnerability in Rongzhitong Visual Integrated Command and Dispatch Platform up to version 20260617 allows remote attackers to perform unrestricted file uploads via manipulation of the File argument in the /dm/dispatch/userinfo/upload endpoint. The vulnerability has a CVSS 3.1 score of 7.3, indicating a medium severity. The vendor was contacted but did not respond, and no patch or remediation information is currently available. Exploit code is publicly available but no known exploitation in the wild has been reported.
Pluck CMS through 4.7.21 restricts dangerous file uploads in its admin file-management feature using a fixed blacklist in data/inc/files.php ('.php','php3','php4','php5','php6','php7','phtml','.phtm','.pht','.ph3','.ph4','.ph5','.asp','.cgi','.phar'), checked against the last 4-5 characters of the filename.
The LightSync Pro WordPress plugin up to version 2.1.6 has a vulnerability allowing authenticated users with Author-level access or higher to upload arbitrary files due to missing file type validation. This flaw exists in the rest_replace_media() function and could lead to remote code execution on the affected server.
The zportals WordPress plugin before version 6.3.4 contains a vulnerability that allows authenticated users with Subscriber or higher roles to upload arbitrary PHP files due to improper validation of uploaded files. This can lead to remote code execution on the affected system.
CVAT versions 2.5.0 through 2.66.0 contain a cross-site scripting (XSS) vulnerability related to how annotation guide assets are served. An attacker can influence the Content-Type header of files attached to annotation guides, causing a victim's browser to interpret malicious files as HTML and execute embedded JavaScript. This vulnerability has been fixed in version 2.67.0.
CVE-2026-14175 is a critical vulnerability in Bilin Software and Informatics Consultancy Inc.'s HUMANIST Digital Human Resources product. It allows unrestricted upload of files with dangerous types, enabling an attacker to upload a web shell to the web server. This affects version 26.0 of the software prior to 26.1. The vulnerability has a CVSS score of 9.8, indicating high severity with network attack vector, no required privileges or user interaction, and full confidentiality, integrity, and availability impact.
The Chat Widget: Floating Customer Support Button for 30+ Channels, Supporting SMS, Calls, and Chat WordPress plugin before 1.8.2 does not validate the type, extension, content, or size of files submitted to its public response endpoint and stores them under the uploads directory, so an unauthenticated user can upload arbitrary files. The original extension is discarded (files are stored under a bare UUID), so this does not yield code execution or stored XSS; impact is bounded to disk consumption and content hosting. The storing path requires the channel's response storage or mail-forwarding to be configured.