The Drupal Vulnerability Scanner detects drupal.org security advisories that affect your site's Drupal core and contributed modules. It runs when you start it and in scheduled reports at most every 2 hours (Pro plan or higher), and only against sites whose ownership your account has verified.
How it tests
- The core version is read from your site's
CHANGELOG.txtfile (exact patch level). WhenCHANGELOG.txtis blocked, the scanner falls back to the<meta name="generator">tag, which gives the major version only. - Contributed module versions are read from each module's
.info.ymlfile. - The detected versions are matched against our own copy of the drupal.org core and contributed-module security advisories, refreshed every 2 hours and supplemented with data from the NVD. No third party is contacted during the scan.
- The same responses are also checked for the PHP2Shell vulnerability in PHP and for outdated software versions.
- The scanner runs only against sites whose ownership your account has verified.
What you see
- A finding for core and for each detected module whose version falls in an affected range, naming the advisory.
- When only the major version is known (generator tag), the finding says the exact release cannot be judged.
Limits
- Sites that block
CHANGELOG.txtand the.info.ymlfiles can only be judged by major version. - Modules not exposing an
.info.ymlfile are not detected.