Calculated Fields FormWordPress extension · Codepeople
CVE-2020-7228
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Calculated Fields Form plugin through 1.0.353 for WordPress suffers from multiple Stored XSS vulnerabilities present in the input forms. These can be exploited by an authenticated user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Calculated Fields Form WordPress plugin (versions up to 1.0.353) contains multiple stored Cross-Site Scripting (XSS) vulnerabilities in its input forms. The vulnerability is exploitable by authenticated users, allowing malicious JavaScript to be persistently stored and executed when other users view the affected forms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Calculated Fields FormWordPress extension
<= 1.0.353CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'Calculated Fields Form' or 'Codepeople Calculated Fields Form' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'calculated-fields-form'.Affected if The plugin is present in the WordPress installation.
-
Determine installed versionIn WordPress admin, go to Plugins > Installed Plugins and click on the plugin name to view version details, or open the main plugin file (e.g., calculated-fields-form/cp_calculatedfieldsfree.php) and look for the 'Version' header in the plugin comments.Affected if The version number is 1.0.353 or lower.
-
Identify active form configurationsIn WordPress admin, go to Calculated Fields Form (or CFF) in the sidebar and list all published forms. Note the form IDs and names.Affected if There is at least one published form using this plugin.
-
Inspect form field contents for XSS payloadsEdit each form and review the field labels, placeholders, default values, and calculation formulas. Look for unsanitized HTML/script tags in any input fields, particularly in field labels, help text, or calculated field expressions.Affected if Any form contains raw HTML, script tags, or JavaScript event handlers in field configuration that could execute.
You are affected if the plugin is installed with version 1.0.353 or lower and contains any published forms where malicious scripts could be stored in field configurations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to the latest version which includes proper input sanitization and output encoding for all form fields. Additionally, implement Content Security Policy (CSP) headers as a defense-in-depth measure.
Fix this in Calculated Fields Form
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7228 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data