The Neos Flow upload flaw GHSA-7wrr-qcrp-4hhf lets an attacker, without logging in, write arbitrary files into the public resources directory of a Flow application with a single request. Depending on the web-server configuration, that can lead to remote code execution. Because the Neos content management system is built on the PHP framework Flow, every Neos site running an affected Flow version is vulnerable. The Neos team released fixed versions for all maintained branches on 13 November 2026 and rates the issue at CVSS 9.8.
Neos Flow upload flaw: what happened
According to the security advisory on neos.io, two problems come together. First, Flow processes a file upload before the security policy of the called action is evaluated. An unauthenticated visitor can therefore upload files even if the action itself is protected. Second, the list of forbidden file extensions had gaps. The GitHub advisory GHSA-7wrr-qcrp-4hhf specifically names .phar, .php7, .pht and .shtml as extensions that were not covered.
The uploaded files end up in Web/_Resources/Persistent. Whether that turns into code execution depends on the web server. If it executes PHP or other scripts below Web/_Resources, requesting the uploaded file is enough. On Apache, an uploaded .htaccess file can even re-enable script execution that had been turned off. If the server does not allow scripts there, the advisory says the result is leftover attack files rather than remote execution.
GitHub classifies the issue as CWE-434, unrestricted upload of a dangerous file type. No CVE identifier had been assigned when we retrieved the advisory on 14 November.
Affected versions and updates
The Composer package neos/flow is affected in these versions:
- up to and including 8.3.21 — fixed in 8.3.22
- 8.4.0 to 8.4.6 — fixed in 8.4.7
- 9.0.0 to 9.0.9 — fixed in 9.0.10
- 9.1.0 to 9.1.4 — fixed in 9.1.5
- 9.2.0 to 9.2.2 — fixed in 9.2.3
For most projects, Neos says a composer update neos/flow followed by a deploy is enough. composer show neos/flow confirms whether a fixed version is actually installed. The new releases are plain patch updates. They now check file extensions for every kind of upload, discard newly created resources if a request fails, and enforce the action policy before an error action is called.
Flow 8.2 and older versions are no longer maintained and will not receive a fix. For those installs, hardening the web server is the only protection.
Harden the web server: no scripts under _Resources
The Neos team’s central recommendation applies regardless of the update: the web server should never execute PHP or any other script type below Web/_Resources. That closes the code-execution path even if a file lands there. How to do it depends on the setup. Typical checks include:
- nginx with PHP-FPM: Check whether the
locationrule that forwards requests to PHP-FPM also covers paths under/_Resources/. If it does, a preceding rule should reject scripts in that path. - Apache: Check whether a PHP handler is active for
Web/_Resourcesand whether.htaccessfiles are evaluated there. SettingAllowOverride Nonefor that directory prevents an uploaded.htaccessfrom taking effect. - Shared hosting and managed environments: Ask the provider how script execution in subdirectories is handled. The issue was reported by mittwald, a hoster with many PHP projects, via security@neos.io.
After any change, a test is worthwhile: place a harmless test file with a PHP extension under Web/_Resources and request it. If the source is served or the request is rejected instead of the code running, the hardening works. Remove the test file afterwards.
Check whether your site has already been hit
An update closes the hole but does not remove files that may already have been uploaded. The advisory describes two checks:
- File system: Look in
Web/_Resources/Persistentfor suspicious entries, such as files starting with a dot or extensions like.ph*,.shtml,.cgi,.plor.py. The advisory includes a ready-madefindcommand. - Database: Search the table
neos_flow_resourcemanagement_persistentresourcefor file names matching those patterns. The advisory also provides a SQL query. Hits suggest an unauthenticated upload.
Any files found should be reviewed and, if necessary, removed together with the corresponding database record. If an executable file is found, treat the installation as compromised: rotate credentials, search the logs for requests to that file, and check whether further changes were made to the system. That is general advice for such findings, not a statement about known attacks — reports of exploitation in the wild were not available as of 14 November.
Context: upload flaws remain a recurring issue
Unrestricted uploads are among the oldest and most dangerous classes of web flaws. Only a few days ago we covered the upload flaw CVE-2026-114432 in Contact Form 7. Other PHP projects have also had critical issues recently, including the SQL injection in Craft CMS and the fixes in Symfony HttpFoundation. The pattern is similar: a framework detail that developers rarely inspect themselves opens a path into applications that are otherwise well maintained.
With Neos and Flow, the flaw sits in the framework, not in a plugin. Running a Neos site, you cannot avoid the issue by dropping particular packages. The response is a positive point: according to the Neos team, fixes for five branches were ready within 24 hours of the report, and mittwald disclosed the issue privately before any details became public.
Anyone unsure whether a project is affected can ask in the official forum or the community Slack. Security issues in Neos, Flow or related packages should still go to security@neos.io and should not be discussed in public until a fix is available.
Bottom line
The Neos Flow upload flaw is critical because it works without a login and affects every Neos installation on an affected Flow version. The remedy is manageable: update neos/flow to 8.3.22, 8.4.7, 9.0.10, 9.1.5 or 9.2.3, disable script execution under Web/_Resources, and check the upload directories for files that may already have been placed there. For Flow 8.2 and older, hardening the web server is the only protection.




