dbcve.org
Calculated Fields FormWordPress extension · Codepeople

CVE-2024-2020

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 5.1.57 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
The Calculated Fields Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the form page href parameter in all versions up to, and including, 5.1.56 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the professional version or higher.

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 · high confidence

The Calculated Fields Form WordPress plugin up to version 5.1.56 fails to properly sanitize the form page href parameter and escape it during output, allowing stored XSS injection by unauthenticated attackers. This causes arbitrary JavaScript to execute in users' browsers when accessing affected pages.

MitigationUpdate the Calculated Fields Form plugin to a version newer than 5.1.56 that addresses the sanitization and escaping vulnerability.

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
Affected:< 5.1.57

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Calculated Fields Form', or check the plugin's main PHP file for the Version header comment. Alternatively, inspect the plugin directory via FTP or file manager.
    Affected if The installed version is 5.1.56 or lower (anything below 5.1.57)
  2. Verify the plugin is actively loaded
    Confirm the plugin folder 'calculated-fields-form' exists in /wp-content/plugins/ and the main file cpcff_main.php is present and the plugin is activated in WordPress admin.
    Affected if The plugin is installed and active with a vulnerable version number
  3. Check for forms using the href parameter feature
    In the plugin settings, review any form configurations that include a 'href' or 'link' parameter, particularly in form templates or page redirection settings. Inspect the database table wp cp_calculated_fields for any records containing href-related fields.
    Affected if Forms contain href parameter configurations that could be exploited for XSS injection
  4. Inspect for stored XSS payloads in the database
    Search the WordPress database (specifically tables storing form data and settings) for suspicious patterns like '<script', 'javascript:', 'onerror=', 'onload=' or other JavaScript event handlers within what should be URL fields. Use a database query or a plugin like WP Reset to examine table contents.
    Affected if Any href-related database fields contain unsanitized script tags or event handlers

You are affected if the Calculated Fields Form plugin version is below 5.1.57 and the href parameter feature is in use or the database contains malicious script injections in form-related fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 5.1.57 or later
Fixed in 5.1.57
Interim mitigation

Update the Calculated Fields Form plugin to a version newer than 5.1.56 that addresses the sanitization and escaping vulnerability.

Recommended fix High confidence

Calculated Fields Form version 5.1.57

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find 'Calculated Fields Form' in the plugin list
  4. Click 'Update now' to update the plugin to the latest version, or manually update to version 5.1.57
  5. Verify the plugin shows version 5.1.57 or higher after update
  6. Clear any page caches if caching plugins are in use
  7. Test that forms using the href parameter render correctly without errors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Calculated Fields Form Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2020 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-2020 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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