Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site with equation-populated Select2 dropdown
-
DeliveryCraft link with script in URL parameter
-
ExploitLure victim to click crafted link
-
ExecutionGETURLPARAMETER feeds setChoices unsanitized
-
ImpactScript executes in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation is NOT possible against default/stock configurations. It requires the target site to host a publicly accessible Calculated Fields Form that has a Select2-enabled dropdown whose choices are dynamically populated by a calculated equation that pipes a URL parameter through the GETURLPARAMETER() function into setChoices({texts:[...]}). Only when that specific equation/dropdown wiring exists is the reflected URL-parameter value rendered unsanitized. Limiting factors: the attack is unauthenticated (PR:N) but requires victim user interaction (UI:R, clicking a crafted link), impact is confined to script execution in the victim's browser (C:L/I:L, no availability impact), and the required dropdown-from-URL-parameter configuration is author-created and non-default, substantially narrowing the exploitable site population despite the low attacker-side complexity. |
| Impact | This is a genuine but conditional, moderate-severity issue rather than a top-tier priority. The CVSS 3.1 vector (6.1, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) describes a network-reachable, unauthenticated reflected DOM-based XSS that nonetheless requires victim interaction (UI:R) and yields only limited confidentiality/integrity impact scoped to the browser context (C:L/I:L, S:C). No EPSS score, CISA KEV listing, or public proof-of-concept is present in the supplied intelligence, so exploitation status is 'no public exploit identified at time of analysis' - this is not confirmed active exploitation and should not be treated as such. The most important mitigating signal is not in the raw CVSS metrics but in the description: exploitation is gated on a specific, non-default form configuration (a public form with a Select2 dropdown whose choices are fed from a URL parameter via GETURLPARAMETER() into setChoices). Although PR:N/AC:L make the attacker's side trivial, the realistic population of exploitable sites is limited to those that happen to have built this exact equation-driven dropdown. No signals conflict here; the CVSS vector is internally consistent with the description. Net: patch on a normal cadence, prioritizing sites known to use calculated-equation-populated dropdowns. |
| Exploit ScenarioDerived | An attacker identifies a target WordPress site running Calculated Fields Form (≤5.5.1.3) with a public form whose Select2 dropdown choices are populated by a calculated equation piping a URL parameter through GETURLPARAMETER(). The attacker crafts a link to that form page embedding a malicious script in the consumed URL parameter and lures a logged-in user or visitor into clicking it; the unsanitized value is reflected into setChoices({texts:[...]}) and executed in the victim's browser. No public proof-of-concept is identified in the provided data, and success requires only the single crafted link once the vulnerable configuration exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Reflected DOM-based cross-site scripting in the CodePeople Calculated Fields Form plugin for WordPress (all versions up to and including 5.5.1.3) allows unauthenticated attackers to execute arbitrary script in a victim's browser, but only on sites that have been specifically configured to expose the flaw. The issue is conditional rather than a default-configuration defect: the site must host a public form with a Select2-enabled dropdown whose choices are built by a calculated equation that pipes a URL parameter through GETURLPARAMETER() into setChoices({texts:[...]}); where that wiring exists, a single crafted link is enough to trigger script execution when a user clicks it. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation; the assessed severity is moderate (CVSS 6.1), with impact confined to the victim's session (C:L/I:L/A:N) and victim interaction required (UI:R).
RemediationAI
The primary fix is to update the Calculated Fields Form plugin past 5.5.1.3 to the first release containing the vendor's patch. The fix is referenced in plugin changeset 3713574 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3713574%40calculated-fields-form&new=3713574%40calculated-fields-form); because no separately tagged patched version number is confirmed in the supplied data, treat this as an upstream fix available via PR/commit and verify the installed plugin version against the WordPress plugin directory before considering the issue closed, rather than assuming a specific version number. Where immediate upgrading is not possible, the most effective compensating control is to remove the vulnerable feature pairing: audit every published form for calculated equations that call GETURLPARAMETER() and feed the result into setChoices({texts:[...]}) on a Select2 dropdown, and either delete/replace those equations or hard-code the dropdown choices instead of sourcing them from the URL - at the cost of losing dynamic, shareable pre-filled dropdown behavior on those forms. Forms that do not use this URL-parameter-to-Select2 pattern are not exploitable and need no change. Additional hardening includes deploying a WAF rule that blocks or encodes script-bearing query-string values on pages rendering this plugin (recognizing that client-side DOM execution may bypass server-side filtering, so this is secondary), and reducing exposure by limiting where such dynamic forms are published. For site operators, also consider the plugin's own Wordfence advisory page for any follow-up guidance at https://www.wordfence.com/threat-intel/vulnerabilities/id/215a9f92-e922-4fa3-a4ac-83af788f4e55?source=cve.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a DOM-based (client-side) reflected XSS in a WordPress plugin, falling under CWE-79 (Improper Neutralization of Input During Web Page Generation). Unlike server-side reflected XSS, the injection and execution happen entirely in JavaScript: the plugin's URL-parameter module (js/modules/08_url/public/01_url.js) exposes GETURLPARAMETER(), which reads a value out of the page URL, and the dropdown builder (js/fields-public/08_fbuilder.fdropdown.js, notably around lines 84 and 240) feeds that value into a Select2 widget via setChoices({texts:[...]}) without adequate sanitization or contextual output escaping. When a calculated equation is authored to combine those two features - a URL parameter read by GETURLPARAMETER() and piped into a Select2 dropdown's choice texts - attacker-controlled markup from the query string is rendered into the DOM and executed. Because the payload is never stored and the vulnerable sink is a client-side template/render path, the exploit is reflected and requires the victim to load a crafted link. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) confirms network reachability with no authentication (PR:N), mandatory victim interaction (UI:R), and a scope change (S:C) reflecting that the injected script can affect resources beyond the vulnerable component's original privilege boundary.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Unauthenticated remote reflected XSS requiring a victim click (UI:R) and executing cross-context in the browser (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Calculated Fields Form - AI Form Builder for WordPress - Contact, Payment, Quote, Quiz & More plugin for WordPress is vulnerable to Reflected DOM-Based Cross-Site Scripting via the 'x (any URL parameter consumed by the form's calculated equation)' parameter in all versions up to, and including, 5.5.1.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Exploitation requires the target site to have a public form configured with a Select2-enabled dropdown whose choices are populated via a calculated equation that pipes a URL parameter through GETURLPARAMETER() into setChoices({texts:[...]}); given that configuration, exploitation requires only a single crafted link.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-90561
GHSA-7crj-xgq2-jr8f
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB