CVE-2026-100184: Calculated Fields Form (WordPress plugin) · Cross-site Scripting
Affects Calculated Fields Form (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.7 Medium.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| codepeopleCalculated Fields Form – AI Form Builder for WordPress – Contact, Payment, Quote, Quiz & More | Affected
| Fixed in– |
AI-suggested
Users should check the vendor advisory for updates. In the meantime, avoid using Text Area fields with 'url.<name>' predefined values with predefinedClick disabled or implement additional input validation and output escaping controls. Monitor vendor channels for an official fix and apply it promptly once available.
Description
The Calculated Fields Form plugin for WordPress up to version 5.5.1.3 is vulnerable to a reflected DOM-based cross-site scripting (XSS) attack via a parameter that matches the form's url.<name> predefined value. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts that execute when a user interacts with a crafted link. Exploitation requires the targeted form to have a Text Area field configured with a 'url.<name>' predefined value and predefinedClick disabled, which is a common plugin feature.
References
- wordfence.com/threat-intel/vulnerabilities/id/6f1d2fe6-6cee-4e21-85ac-37d2d48156d2?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/calculated-fields-form/tags/5.5.1.2/js/fbuilder-pro-public.jquery.js (opens in a new tab)
- plugins.trac.wordpress.org/browser/calculated-fields-form/tags/5.5.1.2/js/fields-public/05_fbuilder.ftextarea.js (opens in a new tab)
- plugins.trac.wordpress.org/browser/calculated-fields-form/tags/5.5.1.2/js/fbuilder-pro-public.jquery.js (opens in a new tab)
- plugins.trac.wordpress.org/browser/calculated-fields-form/tags/5.5.1.2/js/modules/08_url/public/01_url.js (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3713574%40calculated-fields-form&new=3713574%40calculated-fields-form (opens in a new tab)