LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19826: The Views Dynamic Fields module through 7.x-1.0-alpha4 for Drupal makes insecure unserialize calls in handl...

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.

HighCVSS 8.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Drupal 7 contributed module can process unsafe serialized data. If an affected site uses Views Dynamic Fields through 7.x-1.0-alpha4, an unauthenticated network attacker may be able to delete files, and code execution is described as possible but not confirmed by the bundle.

Executive priority

Prioritize this for any Drupal 7 estate using the module, especially public-facing sites. The risk is not broad unless the module is present, but impact can be severe because file deletion is demonstrated and code execution is listed as possible.

Technical view

CVE-2019-19826 is an insecure unserialize issue in Views Dynamic Fields, specifically handlers/views_handler_filter_dynamic_fields.inc. The CVE describes PHP object injection using field_names and Archive_Tar objects, demonstrated for file deletion. CVSS 3.0 is 8.1 with network attack vector, no privileges, no user interaction, and high attack complexity.

Likely exposure

Exposure is limited to Drupal sites with the Views Dynamic Fields module installed at versions through 7.x-1.0-alpha4. The bundle does not identify affected CPEs, default exposure paths, or whether all module configurations are reachable remotely.

Exploitation context

The source bundle reports a demonstrated file-deletion impact and says code execution might also be possible. It does not cite active exploitation, and KEV status is false. Treat public-facing affected Drupal instances as higher priority because the CVSS vector indicates network reachability without authentication.

Researcher notes

Evidence is sparse in the provided bundle: no CWE, no CPEs, and no confirmed patch statement are included. The strongest technical claims are the insecure unserialize location, PHP object injection, demonstrated file deletion, possible code execution, and CVSS 8.1.

Mitigation direction

  • Inventory Drupal sites for Views Dynamic Fields and installed version.
  • Check the Drupal project issue for vendor-maintained remediation guidance.
  • Upgrade, disable, or remove affected module versions where vendor guidance supports it.
  • Restrict public access to affected functionality until remediation is verified.
  • Review backups and file integrity monitoring for impacted sites.

Validation and detection

  • Confirm whether Views Dynamic Fields is installed on each Drupal 7 site.
  • Verify installed versions are not through 7.x-1.0-alpha4.
  • Inspect affected handler code for unsafe unserialize usage if source access is available.
  • Review logs and file integrity records for unexplained file deletion activity.
  • Document whether public routes expose views using this module.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-19826 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.0HighCVSS:3.0/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.1High
CVSS 3.0 vector shape for CVE-2019-19826Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.