Vulnerability Checker lists the core, modules, themes, Composer packages and npm packages installed on a Drupal site and checks them for known vulnerabilities against public sources: drupal.org release history, Packagist security advisories, the npm registry's advisories, the NIST National Vulnerability Database, php.net and, optionally, the GitHub Advisory Database.
It reports what those sources say. It does not scan your code, and a clean report does not prove a site is secure: sources can lag or miss things (see Limits).
Features
- drupal.org: core and every installed module and theme, grouped by project, checked against drupal.org release history the way core's Update module does it: a newer security release in your major version, or a project or release marked insecure, revoked or unsupported. Shows the version that fixes it.
- Composer packages (from
vendor/composer/installed.json) against Packagist's security advisories, the datacomposer audituses. - npm packages (from
package-lock.jsonin the project and Drupal folders, plus any you list) against the npm registry's advisories, asnpm auditdoes. - Drupal core CVEs from the NIST NVD, with CVSS severity.
- PHP: warns when your PHP branch is end of life or a newer security release of it is out (php.net).
- GitHub Advisory Database for Composer and npm packages, off by default (GitHub allows 60 requests an hour without a token).
- A report at Reports » Vulnerability report with a table of findings sorted by severity, advisory links, fixed versions, problems and what could not be checked, and a Check now button that runs as a batch so long checks don't time out.
- An entry on the Status report: error when anything is found, warning when never checked, out of date (7 days) or incomplete.
- Scheduled checks from cron (every 6 or 12 hours, daily or weekly, or never).
- Drush:
drush vcheckprints findings as a table or JSON and exits with 1 when anything is found, for CI. - Failures are never silent: unreachable sources, bad answers and version ranges that can't be read are listed as problems on the report and logged. Runs, problems and settings changes are logged with who and when.
What data leaves the site
A check sends only the names and versions of installed projects and packages to updates.drupal.org, packagist.org, registry.npmjs.org, services.nvd.nist.gov (the core version), www.php.net (the PHP major.minor version) and, only if you enable it, api.github.com. Turn off any checker to stop sending data to its source.
Limits
- drupal.org release history has no severity; those findings link to the release and its advisory. Development snapshots and custom code can't be checked and are listed as "not checked".
- The NVD matches by CPE, can lag drupal.org, and covers Drupal core only here. CVEs that the NVD records as "any Drupal version" (mostly old contributed-module issues) are left out.
- npm ranges are compared with
composer/semver; a range it can't read is reported as a problem to check by hand. - Linux distributions often backport PHP fixes without changing the version number, so a PHP "behind" warning may be a false alarm there.
Configuration
Configuration » Vulnerability Checker Settings (/admin/config/vulnerability_checker): which checkers run, how often, the request timeout, whether to include development packages, extra package-lock.json files (must be inside the project folder), and optional GitHub token and NVD API key. Keys are password fields that are never shown again, and can be set in settings.php to keep them out of configuration exports.
The report needs the restricted permission View the vulnerability report and run checks, or Administer site configuration.
For monitoring systems
drush vcstatusprints the last check as JSON (nothing else on stdout) and exits with 0 (ok), 1 (vulnerable), 2 (stale or never checked) or 3 (incomplete or error);--refreshchecks first.- An optional status file with the same JSON, written after every check, atomically, with permissions 0640, at a path outside the web root and public files.
- Both work over SSH or AWS Systems Manager, with no account, key or incoming connection. The format and examples are in
docs/MONITORING.md.
Site monitoring with Easy Life Site Monitor
Easy Life Site Monitor, from easylifeagents.com, is a monitoring system you download and run on your own computer. You list your sites and watch them over SSH or AWS SSM, with or without agents: server traffic, systemd services, packages, server hardening and installed software. For the Drupal side it reads this module's drush vcstatus output.
Vulnerability Checker is free and works fully without it. The module never contacts easylifeagents.com; the report and settings pages show a short notice about Easy Life Site Monitor that each user can dismiss.
For developers
Each source is a Checkers plugin (attribute on Drupal 10.2 and later, annotation on 10.0 and 10.1). Other modules can add their own checkers by extending CheckersPluginBase and implementing check(). Each checker's section of the report can be themed with vulnerability-checker-result--PLUGIN-ID.html.twig.
Related projects
- Drupal core's Update Status module, which reports security releases of drupal.org projects and can email you about them.
composer auditandnpm auditon the command line.- Check Contrib, which checks that core and contributed code still matches drupal.org file by file.
Requirements
Drupal ^10 || ^11 || ^12. No other modules. Outgoing HTTPS access to the sources above. Drush 12 or later for the Drush command.
Ask your assistant about Vulnerability Checker
Check compatibility with your Drupal and PHP version, maintenance and security coverage, from current release data. How it works
Depends on
Dependencies of the latest stable release
No dependencies recorded for this project.
Required by
Tracked projects that depend on this one
No tracked projects depend on this one yet.
Activity
Releases
| Version | Type | Core | PHP | Release date | |
|---|---|---|---|---|---|
| 1.0.x-dev | Dev | 10–11 | Nov 22, 2026 |