If your site runs Contact Form 7, open the Plugins screen and read the version number before you do anything else today. Anything from 6.2 to 6.2.3 lets an unauthenticated visitor leave a file on your server, and a demonstration of how to do it is due to be published today, 19 November. Version 6.2.4 closed that hole on 29 October. Version 6.2.5, released on Tuesday, closed two smaller leaks on top of it. That is the whole decision: you are on 6.2.5, or you have an hour of work this morning.
The short version
- Affected versions: 6.2 through 6.2.3. Fixed in 6.2.4. Best available now: 6.2.5.
- The bug needs no account and no login. Any visitor who can reach a form with a file upload field can use it.
- On a stock Debian or Ubuntu Apache server, that file can be found and run as code. On nginx and on most managed hosts it is “only” an arbitrary file inside
wp-content/uploads, which still means an HTML or SVG page served from your own domain. - 6.2.4 got stricter about file names. Any form that accepts uploads needs to be tested after you update.
- If you cannot update within the hour, close directory listing and block PHP execution in the uploads folder today. That is a ten-line file, and it buys you time.
What the bug actually does
Two failures stack. The plugin does not check the type or extension of a file going through a form’s file field, and a flaw in its temporary-file cleanup means the upload is not removed when the submission finishes. Together, an unauthenticated request can park a file of its choosing on disk and leave it there.
The specific trick that made it work is in the file name: an invalid UTF-8 sequence in the name slips past a check that expects a valid string, which is where the published title comes from. The researcher credited is Shinya Murakami, and the vulnerability is catalogued as CVE 2026-114432.
None of this needs knowledge of your site, only a form with an upload field — which is what a quote form, an invoice form or a “send us your CV” form is.
Where it stops being a plumbing problem
A stray file in a folder sounds survivable. It stops being survivable when the server agrees to interpret it, and that depends on configuration you probably did not write.
On a stock Debian or Ubuntu Apache setup, two defaults line up badly: the server lists directory contents, and it maps .phar to the PHP handler. An uploaded file with that extension can be browsed to by name and executed, which turns a form field into remote code execution on the account that runs your WordPress site.
On nginx, and on Apache installs where .htaccess overrides are switched off, the same file cannot be executed. It is still served as active content from your own origin: an HTML or SVG page you did not publish, hosted under your name, passing every “is this our domain” check a visitor or mail filter might make. The gap between those outcomes is your host’s configuration, not your code.
Check the version in one command
With WP-CLI it is one line:
wp plugin get contact-form-7 --fields=name,status,version
# and, if you want to see everything else waiting for you
wp plugin list --update=available
Without WP-CLI: Plugins → Installed Plugins, find Contact Form 7, read the version under the name. If the number is 6.2, 6.2.1, 6.2.2 or 6.2.3, stop reading and update.
If you cannot update today
Create or edit wp-content/uploads/.htaccess and put this in it:
Options -Indexes
<FilesMatch "\.(php|phtml|phar|php[0-9])$">
Require all denied
</FilesMatch>
That closes the two conditions that turn an upload into code execution on Apache: the folder no longer lists itself, and the server refuses to hand a PHP-family file to the interpreter. It does not fix the bug. Files can still land in the folder; they just cannot run.
On nginx this file does nothing at all, because nginx does not read .htaccess. There you need a location block in the server config, which means a message to your host. Ask for two things in the same message: block execution of PHP files inside the uploads directory, and tell you which PHP branch you are on, because a critical PHP security release is being published today as well.
Where you stand, in one table
| Your version | What it means today | What to do |
|---|---|---|
| 6.2.5 | Current. Both leaks closed. | Nothing today. If you jumped here from 6.2.3, retest your upload forms. |
| 6.2.4 | Upload hole closed. Two smaller leaks open. | Update to 6.2.5 today. |
| 6.2 – 6.2.3 | Publicly attackable, with a walkthrough due today. | Update now, then read the uploads folder for files you did not put there. |
| No idea | Exposure is unknown, which is worse than known. | Read the number now, then harden uploads while you arrange the update. |
The two leaks in 6.2.5 nobody is talking about
6.2.5 does not fix the upload bug; it fixes two smaller ones: mail tags and default values could reveal private post data or user details. If a form’s mail template references post data, or a default value resolves against something the visitor should not see, the response carries it out.
That is quieter than an arbitrary upload and easy to skip because nothing is on fire. What makes it worth the update is how little it needs: no invalid UTF-8, no server configuration, no extension games. A form, a tag, a request.
What I would do in the next hour
- Read the version. One command or one screen. Everything below depends on the answer.
- Back up and update to 6.2.5. A backup before a plugin update is a thirty-second habit that occasionally saves a weekend.
- Submit a test file through every form with an upload field. 6.2.4 made file names stricter, so a form that once accepted an odd name may now reject it, quietly. Test with a normal name and an odd one.
- List the uploads folder by date. Look at the newest files. Anything that is not an image or a PDF you recognise is worth opening in a text editor rather than a browser.
- Ask whether the folder lists itself. Browse to a known uploads subfolder. If you get a file list instead of a 403 or 404, your host is one of the configurations where an upload can become code execution.
- Put the
.htaccessabove in place even if you updated. It costs nothing, does not touch images, and decides whether the next upload bug is a nuisance or an incident.
Two unrelated things land this week and get confused with each other. PHP 8.6.0 is released today, and the PHP team is publishing a security release in the same 30-minute window that touches every supported branch. That one is not about plugin versions; it is about which PHP branch your host runs, and I covered the decision and the checks separately, because the answer there is usually “wait” and the answer here is “today”.
If the version turns out to be 6.2.3 and the site has been live for a month, updating is the start of the job, not the end. Unrecognised files in uploads, a new administrator account, an outgoing mail spike — that is a different checklist, and the five-minute infection check covers the order to look in. I would run it after the update, not before, so you are not reading a live attack while the door is still open.
The pattern to remember: plugin security releases are announced, details go public weeks later, and the gap between those two dates is your only window. Updating core without opening an attack window is the same lesson from a different angle — the update is not the risk, the delay is.
The action
Open the Plugins screen. If Contact Form 7 says 6.2.5, close the tab and get on with your day. If it says anything lower, update it, then spend ten minutes on the uploads folder: what is in it, whether it lists itself, and whether your host will block a .phar from running there. Today is the day those questions stop being theoretical.









