dbcve.org
Views Dynamic FieldDrupal extension · Drupal

CVE-2019-19826

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-16
Fix available
A fix is available. Upgrade to after 6.x-1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Views Dynamic Fields module through 7.x-1.0-alpha4 for Drupal makes insecure unserialize calls in handlers/views_handler_filter_dynamic_fields.inc, as demonstrated by PHP object injection, involving a field_names object and an Archive_Tar object, for file deletion. Code execution might also be possible.

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 Views Dynamic Fields module for Drupal uses insecure unserialize() on untrusted input in the views_handler_filter_dynamic_fields.inc file. This PHP object injection vulnerability allows attackers to craft malicious serialized PHP objects (including field_names and Archive_Tar objects) that can trigger file deletion and potentially achieve remote code execution.

MitigationUpgrade the Views Dynamic Fields module to a version that replaces insecure unserialize calls with safe deserialization (e.g., json_decode). If immediate upgrade is not feasible, disable the module to eliminate the attack surface.

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
Views Dynamic FieldDrupal extension
Affected:<= 6.x-1.4= 7.x-1.0

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Views Dynamic Fields module is installed
    Check Drupal's module directory (sites/all/modules or modules/contrib) for the views_dynamic_fields folder, or query the system table: SELECT name, status FROM system WHERE name LIKE '%views_dynamic_fields%';
    Affected if The module folder exists or the module is present in the Drupal system table with status = 1 (enabled)
  2. Identify the installed module version
    Open the views_dynamic_fields.info file in the module directory and read the 'version' or 'core' and 'project version' fields, or query: SELECT info FROM system WHERE name = 'views_dynamic_fields';
    Affected if The version is 6.x-1.4 or earlier for Drupal 6, OR exactly 7.x-1.0 for Drupal 7
  3. Locate the vulnerable include file
    Check for the presence of views_handler_filter_dynamic_fields.inc in the module's includes or handlers subdirectory
    Affected if The file exists in the module directory, indicating the vulnerable code is present
  4. Confirm the module is accessible to untrusted users
    Verify the Views Dynamic Fields filter is exposed in any Views that are accessible to anonymous or untrusted users. Check Views UI at admin/structure/views or query the views_display table for views using the dynamic_fields filter handler.
    Affected if A View using this filter is enabled and accessible to unauthenticated users or has inadequate access controls

A user is affected if the Views Dynamic Fields module is installed with version <= 6.x-1.4 or = 7.x-1.0, the vulnerable include file exists, and the module or its Views are accessible to untrusted users.

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 a release after 6.x-1.4
Interim mitigation

Upgrade the Views Dynamic Fields module to a version that replaces insecure unserialize calls with safe deserialization (e.g., json_decode). If immediate upgrade is not feasible, disable the module to eliminate the attack surface.

Recommended fix Moderate confidence

Upgrade to the latest stable release of Views Dynamic Fields module (check drupal.org for the current fixed version)

  1. 1. Back up your Drupal database and files before making any changes.
  2. 2. Navigate to your Drupal site's administration panel or use Composer to update the Views Dynamic Fields module.
  3. 3. Update the Views Dynamic Fields module to the latest stable release available on drupal.org/project/views_dynamic_fields.
  4. 4. Clear the Drupal cache after upgrading: navigate to Configuration > Development > Performance > Clear all caches, or use drush cr.
  5. 5. Verify the update was successful by checking the module version in the Drupal administration interface.
  6. 6. Test that the Views Dynamic Fields functionality works as expected in your environment.
Caveat Review release notes for any potential breaking changes between your current version and the new version

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

Fix this in Views Dynamic Field Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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