GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Check your stack
DRUPAL-CONTRIB-2026-190unknown

This module enables you to personalize content for anonymous and authenticated users by showing different blocks to visitors based on client-side conditions.

Impact

This module enables you to personalize content for anonymous and authenticated users by showing different blocks to visitors based on client-side conditions.

Source excerpt · OSV
Applies when

This vulnerability is mitigated by the fact that a site must have placed a block whose access is restricted to certain users inside a Display Blocks reaction.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

drupal/smart_content Packagist:https://packages.drupal.org/8
Affected rangeRecorded fix
Earlier releases before 3.2.1Ecosystem versions3.2.1

Version evidence: OSV · DRUPAL-CONTRIB-2026-190

View original version evidence (0 explicit versions)

Original source description

This module enables you to personalize content for anonymous and authenticated users by showing different blocks to visitors based on client-side conditions.

The Smart Content Block submodule doesn't sufficiently check block access when it renders the blocks of a "Display Blocks" reaction through the module's AJAX endpoint.

This vulnerability is mitigated by the fact that a site must have placed a block whose access is restricted to certain users inside a Display Blocks reaction. Sites that only use Views blocks in reactions are not affected, because Views re-checks access when the view is executed.

References