VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

drupal7: vulnerability history, versions and safety

drupal7 is a package in the Debian ecosystem. Vulert records 18 vulnerabilities for it across 27 releases, from Nov 2013 to Apr 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded U18
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all drupal7 vulnerabilities

Vulert verdict on drupal7 i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 26 Apr 2018. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 18 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 18 over 4 years · 0 in the last year i
  • Latest disclosure 26 Apr 2018 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for drupal7, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 27 of 27 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 1
  • 2014 6
  • 2015 3
  • 2016 4
  • 2017 1
  • 2018 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 18 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for drupal7

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Drupal7 Security Update N/A unrated 7.14-2+deb7u12 28 Feb 2016
Drupal7 - SQL Injection Vulnerability N/A unrated 7.14-2+deb7u7 15 Oct 2014
Information Disclosure Vulnerability in Drupal7 N/A unrated 7.14-2+deb7u4 25 Apr 2014
Drupal7 - Remote Code Execution Vulnerability N/A unrated 7.14-2+deb7u19 26 Apr 2018
Security Update for Drupal7 N/A unrated 7.14-2+deb7u11 31 Aug 2015

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About drupal7

Is drupal7 safe to use?

Vulert records 18 vulnerabilities for drupal7 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 18 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does drupal7 have?

18 vulnerabilities are recorded for drupal7 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 18 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new drupal7 vulnerabilities disclosed?

0 vulnerabilities were recorded for drupal7 in the last 12 months, and the oldest entry in this database dates to 26 Nov 2013. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of drupal7 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor drupal7 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the drupal7 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.