Calculated Fields FormWordPress extension · Codepeople
CVE-2024-29759
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in CodePeople Calculated Fields Form allows Reflected XSS.This issue affects Calculated Fields Form: from n/a through 1.2.54.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the CodePeople Calculated Fields Form plugin. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized input that gets reflected back in the web page without proper output encoding.
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.2.55CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installationCheck if the Codepeople Calculated Fields Form plugin is installed on the WordPress site by looking in the /wp-content/plugins/ directory for a folder named 'calculated-fields-form' or similar.Affected if The plugin folder exists in the WordPress plugins directory.
-
Identify installed versionOpen the main plugin file (typically the primary PHP file in the plugin folder) and look for the version comment in the file header, or check the readme.txt file for the 'Stable tag' or 'Version' entry.Affected if The version number found is lower than 1.2.55.
-
Confirm plugin is activeIn the WordPress admin dashboard, go to Plugins > Installed Plugins and verify whether the Calculated Fields Form plugin is currently activated.Affected if The plugin shows as active in the WordPress admin.
-
Identify forms using calculated fieldsNavigate to the plugin settings in the WordPress admin (usually under a menu item for Calculated Fields Form) and list any published forms that include calculated field functionality.Affected if There are active forms with calculated fields that accept user input.
You are affected if the plugin is installed, active, and the installed version is below 1.2.55, with published forms that use calculated field functionality.
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.
dbcve · scoped1.2.55
Update the plugin to the latest version which should include proper input sanitization and output encoding for all user-supplied data rendered in web pages.
Calculated Fields Form 1.2.55
- Backup your WordPress site database and files
- Update the Calculated Fields Form plugin to version 1.2.55 or later through the WordPress admin dashboard (Plugins > Updates)
- Verify the update was successful by checking the plugin version
- Test the form functionality to ensure it works correctly after the update
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
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29759 — 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-2024-29759 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