VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

wordpress: vulnerability history, versions and safety

wordpress is a package in the Debian ecosystem. Vulert records 675 vulnerabilities for it across 42 releases, from Dec 2004 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
675 vulnerabilities recorded U675
i
37 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 17 Aug 2026.

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

Careful: 37 of the 675 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 675 vulnerabilities on record across 21 years, 5 in the last year.

What to do: Plan around the 37 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 675 over 21 years · 5 in the last year i
  • Latest disclosure 17 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 37 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 42 of 42 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2004 4
  • 2005 20
  • 2006 34
  • 2007 70
  • 2008 36
  • 2009 28
  • 2010 6
  • 2011 20
  • 2012 42
  • 2013 38
  • 2014 54
  • 2015 24
  • 2016 38
  • 2017 91
  • 2018 30
  • 2019 46
  • 2020 42
  • 2021 11
  • 2022 20
  • 2023 6
  • 2024 6
  • 2025 5
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for wordpress

The 5 most severe of 675 vulnerabilities recorded for this package

Search all 675 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Deserialization Vulnerability in WordPress - CVE-2020-28032 9.8 critical 5.5.3+dfsg1-1 02 Nov 2020
Privilege Escalation Vulnerability in WordPress XML-RPC 9.8 critical 5.5.3+dfsg1-1 02 Nov 2020
Privilege Escalation Vulnerability in WordPress: CVE-2020-28035 9.8 critical 5.5.3+dfsg1-1 02 Nov 2020
Critical Remote Code Execution Vulnerability in WordPress - CVE-2020-28037 9.8 critical 5.5.3+dfsg1-1 02 Nov 2020
Critical Input Sanitization Bypass in WordPress - CVE-2019-20041 9.8 critical 5.3.2+dfsg1-1 27 Dec 2019

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 675 vulnerabilities for wordpress in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 675 not yet rated. 37 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does wordpress have?

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

5 vulnerabilities were recorded for wordpress in the last 12 months, and the oldest entry in this database dates to 31 Dec 2004. 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.