VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

wordpress: vulnerability history, versions and safety

wordpress is a package in the Debian ecosystem. Vulert records 10 vulnerabilities for it across 30 releases, from Mar 2011 to Feb 2016. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded U10
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 wordpress vulnerabilities

Vulert verdict on wordpress i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 10 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 10 over 4 years · 0 in the last year i
  • Latest disclosure 16 Feb 2016 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 wordpress, 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 30 of 30 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 1
  • 2012 1
  • 2013 2
  • 2014 2
  • 2015 3
  • 2016 1

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

03 Vulnerabilities

Recorded vulnerabilities for wordpress

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
WordPress - Multiple Security Issues N/A unrated 3.6.1+dfsg-1~deb6u6 01 Jun 2015
WordPress SQL Injection Vulnerability in Debian:6.0 N/A unrated 3.6.1+dfsg-1~deb6u7 18 Aug 2015
WordPress - Cross-Site Scripting and Privilege Escalation Vulnerabilities N/A unrated 3.6.1+dfsg-1~deb6u8 30 Sep 2015
WordPress - Open Redirection and Side Request Forgery Vulnerabilities N/A unrated 3.6.1+dfsg-1~deb6u9 16 Feb 2016
WordPress - Denial of Service and Information Disclosure N/A unrated 3.6.1+dfsg-1~deb6u5 17 Sep 2014

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 wordpress

Is wordpress safe to use?

Vulert records 10 vulnerabilities for wordpress in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 wordpress have?

10 vulnerabilities are recorded for wordpress in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 10 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 wordpress vulnerabilities disclosed?

0 vulnerabilities were recorded for wordpress in the last 12 months, and the oldest entry in this database dates to 11 Mar 2011. 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 wordpress 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 wordpress for upcoming vulnerabilities?

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