CVE
WordPress Calculated Fields Form plugin <= 5.5.2.8 - Cross Site Scripting (XSS) vulnerability
- Exploited
- No known exploitation
- Fix
- Fixed in 5.5.2.9
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 5.5.2.9.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The Calculated Fields Form plugin for WordPress, from codepeople, has a DOM-based cross-site scripting flaw. An attacker can reach it remotely without logging in, but a user must take some action, such as opening a crafted link or page, before the attack works.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in codepeople Calculated Fields Form calculated-fields-form allows DOM-Based XSS.This issue affects Calculated Fields Form: from n/a through 5.5.2.8.
cve.now Index
- Exploitation0/40No signal
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
What to do
Upgrade to a fixed version: 5.5.2.9.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124253 (WordPress Calculated Fields Form plugin <= 5.5.2.8 - Cross Site Scripting (XSS) vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-124253 (entry last updated 2026-11-11):
Affected:
- codepeople Calculated Fields Form: through 5.5.2.8
Fixed versions: 5.5.2.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-124253 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124253 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/calculated-fields-form/vulnerability/wordpress-calculated-fields-form-plugin-5-5-2-8-cross-site-scripting-xss-vulnerability?_s_id=cve
- https://www.cve.org/CVERecord?id=CVE-2026-124253
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-124253
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124253"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- calculated-fields-form
through 5.5.2.8
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124253
Is CVE-2026-124253 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw is cross-site scripting, which lets attackers inject malicious scripts into the site. Those scripts can steal visitor data or hijack visitor accounts.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-124253?
calculated-fields-form: through 5.5.2.8.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists all versions of the codepeople Calculated Fields Form plugin for WordPress up to and including 5.5.2.8, with no extra conditions. To check a site, compare the installed plugin version shown on the WordPress Plugins admin page against that range.Source: patchstack.com, cve.org
How do I fix CVE-2026-124253?
Update the Calculated Fields Form plugin to 5.5.2.9 or later, the fixed version named in the advisory.Source: patchstack.com, cve.org