dbcve.org
Artificial IntelligenceDrupal extension · Artificial Intelligence Project

CVE-2025-31678

HIGH · 8.2 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 1.0.3 or later.
See remediation →
91/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
Missing Authorization vulnerability in Drupal AI (Artificial Intelligence) allows Forceful Browsing.This issue affects AI (Artificial Intelligence): from 0.0.0 before 1.0.3.

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

Missing authorization vulnerability in Drupal AI module allows forceful browsing, enabling users to access restricted pages or resources they shouldn't have permission to view. The lack of proper access control checks permits bypassing normal authorization mechanisms.

MitigationUpgrade Drupal AI module to version 1.0.3 or later to obtain the authorization fix.

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
Artificial IntelligenceDrupal extension
Affected:< 1.0.3

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
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify if Drupal AI module is installed
    Check your Drupal installation for the presence of the Artificial Intelligence (ai) module. This can be done via the Drupal admin interface at /admin/modules, or by searching for the ai module directory in your codebase (commonly in modules/contrib/ai or similar).
    Affected if The Drupal AI module is present in your installation
  2. Check the installed version of Drupal AI module
    Locate the ai.info.yml or composer.json file within the AI module directory and read the version number. Alternatively, use Drush command: drush pm-list --type=module --status=enabled | grep -i ai
    Affected if The version is below 1.0.3 (any version < 1.0.3)
  3. Confirm the module is enabled
    Verify the AI module is currently enabled and active on your Drupal site. Check via Drupal admin at /admin/modules, or run: drush pm-list --status=enabled --type=module
    Affected if The AI module shows as enabled in the module list
  4. Test for unauthorized access to restricted pages
    As a low-privileged user, attempt to access Drupal AI-related admin pages or resource endpoints that should require elevated permissions (e.g., /admin/config/ai/*). Compare access results against expected role-based access control.
    Affected if A user without proper permissions can access AI module administrative paths or restricted resources

You are affected if the Drupal AI module is installed, enabled, and running a version prior to 1.0.3, allowing unauthorized access to restricted pages or resources.

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.3 or later
Fixed in 1.0.3
Interim mitigation

Upgrade Drupal AI module to version 1.0.3 or later to obtain the authorization fix.

Recommended fix High confidence

1.0.3

  1. Back up your Drupal site database and files before updating
  2. Update the Drupal AI (Artificial Intelligence) module to version 1.0.3 or later via Composer: composer require drupal/ai:^1.0.3
  3. Run database updates if any are required: drush updatedb or via the web interface at /update.php
  4. Clear the Drupal cache: drush cr or via the web interface at admin/config/development/performance

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

Fix this in Artificial Intelligence Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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