Chatterbug Forms CVE-2026-125055: Check the upload fix before reopening forms
Restrict public Chatterbug Forms submissions while you verify the update for CVE-2026-125055. Wordfence’s CVE record rates the issue Critical, CVSS 3.1 9.8, and lists versions through 1.0.2 as affected. The vendor has published upload-hardening changes under stable tag 1.1, but the official package still has a 1.0.2 plugin header.
Wordfence records disclosure at November 12, 2026, 21:10:49 UTC. The CVE record was published on November 13, after that disclosure.
Check exposure and the update package
An unauthenticated visitor who can reach a public Chatterbug form can obtain its submission nonce. Wordfence describes inadequate server-side file-type validation, particularly when no field restriction is configured. Uploaded files may execute if the web server permits execution in their storage location. An upload alone does not establish remote code execution.
The vendor readme identifies stable tag 1.1 and documents file-type checks, upload restrictions and safer file handling. However, the WordPress directory page still displays version 1.0.2 while linking to a 1.1 download. The downloaded archive has the same conflicting labels. A dashboard version check alone cannot settle which code is installed.
Ask the vendor or your managed host to confirm the patched package before deployment. Use the confirmed 1.1 package or a later compatible supported release, test it in staging, and keep public submissions restricted if patch status remains uncertain. Finding validation function names in source is not proof that every upload path enforces them correctly.
Inspect the public archive on Linux
This check downloads the official archive and reads two metadata fields without extracting or executing PHP. It does not inspect your WordPress installation or test the vulnerability. Use Linux with Python 3 and curl installed.
Create a fresh scratch directory:
workdir=$(mktemp -d) && cd "$workdir"Stop if setup fails. Keep the remaining commands in the same shell. Download the archive:
curl --fail --show-error --silent --location --max-time 60 \
--output chatterbug-forms.1.1.zip \
https://downloads.wordpress.org/plugin/chatterbug-forms.1.1.zipStop if curl returns an error. Save this source as chatterbug_package_info.py:
import argparse
import re
from zipfile import BadZipFile, ZipFile
parser = argparse.ArgumentParser(allow_abbrev=False)
parser.add_argument("archive")
args = parser.parse_args()
fields = (
("chatterbug-forms/chatterbug-forms.php", "Version", "Plugin header"),
("chatterbug-forms/readme.txt", "Stable tag", "Readme stable tag"),
)
values = []
try:
with ZipFile(args.archive) as archive:
for name, field, label in fields:
info = archive.getinfo(name)
if info.file_size > 1_000_000:
raise ValueError("metadata file exceeds size limit")
content = archive.read(name).decode("utf-8-sig")
pattern = rf"^{re.escape(field)}:[ \t]*([^\r\n]+)"
match = re.search(pattern, content, re.MULTILINE)
if not match:
raise ValueError(f"missing {field} field")
values.append((label, match[1].strip()))
except (OSError, BadZipFile, KeyError, ValueError, RuntimeError) as error:
parser.exit(1, f"Metadata check failed: {error}\n")
for label, value in values:
print(f"{label}: {value}")
if values[0][1] != values[1][1]:
print("Labels differ: confirm the delivered update with the vendor.")
print("Metadata only; installed files and upload behavior are unchecked.")Run the metadata check:
python3 chatterbug_package_info.py chatterbug-forms.1.1.zipObserved on Debian 13, Python 3.12.14, November 13, 2026, exit status 0:
Plugin header: 1.0.2
Readme stable tag: 1.1
Labels differ: confirm the delivered update with the vendor.
Metadata only; installed files and upload behavior are unchecked.The publisher may replace the archive later. Exit status 0 means the metadata was read, not that the package passed a security test. Missing, invalid or incomplete archives fail with status 1.
After saving any evidence you need, remove only these scratch files:
rm -- chatterbug_package_info.py chatterbug-forms.1.1.zip
cd /
rmdir -- "$workdir"
unset workdirDeploy and validate without attack payloads
- Inventory every site using the plugin, including multisite installations, and identify publicly reachable forms. If an update cannot be validated promptly, deactivate the plugin or have your host enforce access restrictions on submission handling. Hiding a form page alone may leave its handler reachable. Plan an alternative contact route while forms are unavailable.
- Back up the database and site files, including uploads and plugin configuration. Verify a restore in private staging. Suppress outbound notifications there so test submissions do not reach real customers.
- Install the vendor-confirmed package in staging using your normal WordPress or hosting deployment process. Record its source and the installed files; account for the conflicting version labels. Check PHP errors and ordinary page rendering before testing forms.
- Submit harmless files allowed by your policy, then a harmless non-executable file type that the policy excludes. Confirm rejection on the server, successful storage for allowed uploads, and expected notifications to test recipients. Never use executable files or bypass payloads. Review server configuration to prevent execution in upload storage. The vendor’s Apache
.htaccessaddition does not protect nginx. - Deploy the tested package to production, repeat benign functional checks, and inspect error logs before restoring public access. If rollback is necessary, keep affected forms restricted; restoring an older package also restores its vulnerability.
Only the archive metadata check ran on Linux. No WordPress instance, plugin update or exploit was tested. The Wordfence advisory page returned a JavaScript challenge; the vulnerability claims above use Wordfence’s accessible CVE record. That record does not establish active exploitation.
Acknowledgements
This post was created with assistance from AI.