Material IconsDrupal extension · Imagexmedia
CVE-2026-3210
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 · uneditedIncorrect Authorization vulnerability in Drupal Material Icons allows Forceful Browsing.This issue affects Material Icons: from 0.0.0 before 2.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 confidenceIncorrect Authorization vulnerability in Drupal Material Icons module allows Forceful Browsing, enabling users to access restricted resources or pages they shouldn't have access to due to missing or improper authorization checks in versions before 2.0.4.
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
Material IconsDrupal extension
< 2.0.4CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Material Icons moduleSearch for the 'material_icons' module directory in your Drupal installation, typically under 'modules/contrib/' or 'sites/all/modules/'Affected if The module directory exists in the Drupal installation
-
Check the module versionOpen the module's .info.yml file (usually named material_icons.info.yml) and locate the 'version' or 'core' field, or check the composer.json file if presentAffected if The reported version is less than 2.0.4 or no version is specified (indicating an unpatched release)
-
Verify the module is enabledLog in to the Drupal admin dashboard and navigate to 'Extend' or 'Modules' page, or query the 'system' database table filtering by name='material_icons' and status=1Affected if The module is installed and enabled (status = 1)
If the Material Icons module is installed, enabled, and the version is below 2.0.4, the environment is affected by this authorization bypass vulnerability.
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 · scoped2.0.4
Update Material Icons Drupal module to version 2.0.4 or later to include proper authorization controls and restrict access to sensitive resources.
2.0.4
- Backup your Drupal site database and files
- Update the Material Icons module to version 2.0.4 via Drupal's admin interface (Extend > Check for updates > Update) or via Composer: composer require drupal/material_icons:^2.0.4
- Run database updates if any are required (drush updatedb or via admin UI)
- Clear Drupal caches (drush cr or via admin UI at Configuration > Development > Performance > Clear all caches)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Material Icons
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3210 — 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-2026-3210 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