dbcve.org
Calculation FieldsDrupal extension · Joaopaulocdev

CVE-2026-3528

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-26
Fix available
A fix is available. Upgrade to 1.0.4 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
Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Calculation Fields allows Cross-Site Scripting (XSS).This issue affects Calculation Fields: from 0.0.0 before 1.0.4.

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 confidence

A Cross-Site Scripting (XSS) vulnerability exists in the Drupal Calculation Fields module due to improper input neutralization during web page generation. Attackers can inject malicious JavaScript code through calculation fields that will be executed in the browsers of users viewing affected pages. The vulnerability affects versions prior to 1.0.4.

MitigationUpdate the Drupal Calculation Fields module to version 1.0.4 or later to incorporate proper input sanitization and 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
Calculation FieldsDrupal extension
Affected:< 1.0.4

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. Verify Drupal Calculation Fields module is installed
    Run 'drush pm-list --type=module' or check the Drupal modules directory for the calculation_fields module (typically in modules/contrib/joaopaulocdev_calculation_fields or similar). Also check the .info.yml file for the module.
    Affected if The module is present and enabled in the Drupal installation
  2. Determine the installed version of the Calculation Fields module
    Run 'drush pm-info calculation_fields' or inspect the calculation_fields.info.yml file in the module directory to read the 'version:' or 'core:' field. Also check composer.json if installed via Composer.
    Affected if The reported version is any version prior to 1.0.4 (e.g., 1.0.3, 1.0.2, 1.0.1, 1.0.0, or no version shown which indicates an unpatched release)
  3. Confirm calculation fields are in use on the site
    Query the Drupal database for field configurations: run 'drush sql-query "SELECT * FROM config WHERE name LIKE '%calculation%'"' or check the field_config and field_config_instance tables for any fields of type 'calculation' or related to the module.
    Affected if Any calculation field configurations exist and are being used in content types, forms, or views on the site

The environment is affected if the Joaopaulocdev Calculation Fields module is installed with a version earlier than 1.0.4 and calculation fields are actively configured or rendered on the Drupal site.

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 1.0.4 or later
Fixed in 1.0.4
Interim mitigation

Update the Drupal Calculation Fields module to version 1.0.4 or later to incorporate proper input sanitization and output encoding.

Recommended fix High confidence

1.0.4

  1. Back up your Drupal site database and files
  2. Update the Calculation Fields module to version 1.0.4 or later using Composer (composer update drupal/calculation_fields) or via Drupal's admin interface at /admin/modules
  3. Clear Drupal caches after the update using drush cr or via admin interface
  4. Verify the Calculation Fields module shows version 1.0.4 or higher at /admin/modules
  5. Test calculation field functionality to ensure the upgrade did not break existing forms
Caveat Minor patch upgrade; test calculation field forms after applying

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

Fix this in Calculation Fields Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3528 — 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-2026-3528 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