Chatterbug Forms WordPress plugin flaw allows unauthenticated file upload (CVE-2026-125055)

Critical 9.8CVE-2026-125055

Chatterbug Forms WordPress plugin flaw allows unauthenticated file upload (CVE-2026-125055)

The Chatterbug Forms – Fast, Flexible WordPress Form Builder plugin for WordPress has a critical arbitrary file upload vulnerability, tracked as CVE-2026-125055. It affects all versions up to and including 1.0.2. Unauthenticated attackers can upload files that may be executable, such as PHP scripts, which makes remote code execution on the web server possible.

The flaw is rated 9.8 out of 10 (Critical). As of the record date, 15 November 2026, it is not listed in CISA’s Known Exploited Vulnerabilities catalog. The records do not yet confirm a patched release, so administrators should check the plugin’s status urgently and consider removing it until a fix is confirmed.

What’s affected

The vulnerable plugin is Chatterbug Forms – Fast, Flexible WordPress Form Builder (vendor listed as sameh101). All versions from the first release up to and including 1.0.2 are affected.

The problem is in the cbforms_check_form_submissions function, which handles form submissions. The function does not validate file extensions on the server side. When a form’s upload field has no file-type restriction configured, the allowed-type check falls back to the uploaded file’s own extension. As a result, any extension is accepted, including .php.

The plugin uses a submission nonce, but it is printed inline on every public page that contains a Chatterbug form. Any visitor can obtain it, so it does not stop unauthenticated attackers.

The records reference a code change to the plugin’s development trunk. They do not state which released version, if any, contains the fix.

How serious is it

The CVSS 3.1 base score is 9.8 (Critical), assigned by the CVE Numbering Authority (CNA), with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms:

  • Attack vector: Network. The flaw can be exploited remotely over the internet against any site with a public Chatterbug form.
  • Attack complexity: Low. No special conditions are needed.
  • Privileges required: None. The attacker does not need an account on the site.
  • User interaction: None. No site user has to click anything.
  • Impact: High for confidentiality, integrity and availability. A successful attacker who achieves code execution could read data, change the site and disrupt service.

NVD lists the record status as “Deferred”, meaning NVD has not done its own analysis. The score above comes from the CNA.

Is it being exploited?

CVE-2026-125055 is not in CISA’s Known Exploited Vulnerabilities (KEV) catalog as of 15 November 2026. The supplied records contain no reports of exploitation. However, the flaw requires no authentication and has low complexity, so sites running the plugin should treat it as urgent.

What to do

  • Find affected sites. Check your WordPress installations for the Chatterbug Forms plugin and note the installed version. Versions up to and including 1.0.2 are vulnerable.
  • Update only to a confirmed fixed version. The advisory data does not yet confirm a fixed version. If an update newer than 1.0.2 is available, check the vendor or Wordfence advisory to confirm it addresses this CVE before relying on it.
  • Deactivate and remove the plugin if no fix is confirmed. This is the most reliable way to remove the exposure. Use another form builder in the meantime.
  • Restrict file uploads. If you must keep the plugin running briefly, remove file upload fields from Chatterbug forms or take pages with those forms offline.
  • Block script execution in upload directories. Configure the web server so PHP files cannot run from the WordPress uploads directory. This is a general hardening step that limits the impact of upload flaws.
  • Look for signs of compromise. Review upload directories for unexpected .php or other executable files. Check web server logs for unusual form submissions and for requests to newly uploaded files. If you find any, follow your incident response process.
  • Use a web application firewall (WAF) that has rules for WordPress plugin vulnerabilities, if available.

References