dbcve.org
Artificial IntelligenceDrupal extension · Artificial Intelligence Project

CVE-2025-31692

HIGH · 7.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 1.0.5 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Drupal AI (Artificial Intelligence) allows OS Command Injection.This issue affects AI (Artificial Intelligence): from 0.0.0 before 1.0.5.

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

OS Command Injection vulnerability in Drupal AI module allows attackers to execute arbitrary operating system commands via improper neutralization of special elements. The vulnerability exists in versions before 1.0.5 of the Drupal AI (Artificial Intelligence) module, allowing unauthenticated attackers to inject malicious OS commands through unsanitized input paths.

MitigationUpgrade Drupal AI module to version 1.0.5 or later to remediate the OS command injection vulnerability. If immediate upgrade is not possible, restrict access to AI module functionality and audit for any unauthorized command execution.

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.5

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 Drupal AI module is installed
    Check for the presence of the 'ai' module directory in your Drupal installation under modules/contrib/ai or modules/custom/ai. Also check your Drupal site's module list via admin/modules or using Drush: drush pm-list --type=module --status=enabled | grep -i ai
    Affected if The AI module directory exists in modules/contrib/ai or modules/custom/ai
  2. Determine installed AI module version
    Locate the ai.info.yml file in the module directory and read the 'version:' or 'core_version_requirement:' fields. Alternatively, check composer.json if installed via Composer for the exact version number under 'version' or 'require'
    Affected if The version number found is less than 1.0.5, or no version is specified (meaning it is an unpatched development version)
  3. Confirm the AI module is enabled
    Access Drupal admin/modules and verify the AI module status is 'Enabled', or run: drush pm-list --type=module --status=enabled --format=table | grep 'Artificial Intelligence'
    Affected if The module shows as enabled in Drupal's module management interface
  4. Check for AI module administrative access
    Review Drupal user role permissions at admin/user/permissions and verify which roles have 'administer ai' or AI-related configuration permissions. Also check for any exposed AI module routes at admin/config/ai
    Affected if Roles beyond administrator (such as authenticated users) have AI module configuration or execution permissions

A user is affected if the Drupal AI module is installed, enabled, and the installed version is below 1.0.5, making the OS command injection vulnerability exploitable.

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.5 or later
Fixed in 1.0.5
Interim mitigation

Upgrade Drupal AI module to version 1.0.5 or later to remediate the OS command injection vulnerability. If immediate upgrade is not possible, restrict access to AI module functionality and audit for any unauthorized command execution.

Recommended fix High confidence

1.0.5

  1. 1. Backup the Drupal site database and all files before making any changes
  2. 2. Update the Drupal AI module to version 1.0.5 using Composer: composer update drupal/ai --with-all-dependencies
  3. 3. Alternatively, update through the Drupal admin interface at /admin/modules/update
  4. 4. Run database updates if required: drush updb (or via admin at /update.php)
  5. 5. Clear all Drupal caches: drush cr (or via admin at /admin/config/development/performance)
  6. 6. Verify the installed version is 1.0.5: drush pm:list | grep ai

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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