Skip to content
statance
MenuClose
← All WordPress releases

Is WordPress 2.0 end of life?

End of life

Yes. WordPress 2.0 reached end of life on 5 August 2007 (19.3 years ago) and no longer receives security updates.

Released
26 December 2005
Active support ends
5 August 2007
Security support ends
5 August 2007
Latest release
2.0.11 · 5 August 2007
Long-term support
No

What this means for your servers

New vulnerabilities in WordPress 2.0 are no longer fixed. Every newly published CVE that affects it stays open on your servers, and vulnerability scanners and compliance audits (PCI DSS, SOC 2, Cyber Essentials, ISO 27001) flag unsupported software as a finding. Upgrade, or isolate the machine until you can.

How to check if you’re running WordPress 2.0

WP-CLI

wp core version

What to upgrade to

The newest supported release is WordPress 7.1.

Only the latest WordPress branch is fully supported; older branches receive security backports at the core team’s discretion. Update from Dashboard → Updates or wp core update, after backing up files and the database and checking plugin compatibility.

Find end-of-life software before an auditor does

Statance’s daily website scan detects outdated WordPress versions and raises a security finding when it goes past end of life or falls behind the latest patch, along with known CVEs from OSV.dev and CISA’s Known Exploited Vulnerabilities list. Security monitoring is included in Pro and Business. How security monitoring works.

Other WordPress releases

ReleaseStatusSecurity support ends
WordPress 7.1SupportedNo date announced
WordPress 7.0Security fixes onlyNo date announced
WordPress 6.9Security fixes onlyNo date announced
WordPress 6.8Security fixes onlyNo date announced
WordPress 6.7Security fixes onlyNo date announced
WordPress 6.6Security fixes onlyNo date announced
WordPress 6.5Security fixes onlyNo date announced
WordPress 6.4Security fixes onlyNo date announced
WordPress 6.3Security fixes onlyNo date announced
WordPress 6.2Security fixes onlyNo date announced
WordPress 6.1Security fixes onlyNo date announced
WordPress 6.0Security fixes onlyNo date announced
WordPress 5.9Security fixes onlyNo date announced
WordPress 5.8Security fixes onlyNo date announced
WordPress 5.7Security fixes onlyNo date announced
WordPress 5.6Security fixes onlyNo date announced
WordPress 5.5Security fixes onlyNo date announced
WordPress 5.4Security fixes onlyNo date announced
WordPress 5.3Security fixes onlyNo date announced
WordPress 5.2Security fixes onlyNo date announced
WordPress 5.1Security fixes onlyNo date announced
WordPress 5.0Security fixes onlyNo date announced
WordPress 4.9Security fixes onlyNo date announced
WordPress 4.8Security fixes onlyNo date announced
WordPress 4.7Security fixes onlyNo date announced
WordPress 2.3End of life29 March 2008
WordPress 2.2End of life24 September 2007
WordPress 2.1End of life24 September 2007
WordPress 1.5End of life26 December 2005
WordPress 1.2End of life17 February 2005
WordPress 1.0End of life22 May 2004

All WordPress end-of-life dates →

FAQ

Is WordPress 2.0 end of life?

Yes. WordPress 2.0 reached end of life on 5 August 2007 (19.3 years ago) and no longer receives security updates.

When does WordPress 2.0 reach end of life?

Security support for WordPress 2.0 ended on 5 August 2007.

What should I upgrade WordPress 2.0 to?

WordPress 7.1 is the newest release that is still supported. Only the latest WordPress branch is fully supported; older branches receive security backports at the core team’s discretion.

Can I keep running WordPress 2.0 after end of life?

It keeps working, but new vulnerabilities will not be fixed, so every newly published CVE stays open on your server. Scanners and compliance frameworks (PCI DSS, SOC 2, Cyber Essentials) treat unsupported software as a finding.

What is the latest version of WordPress 2.0?

The latest release in this cycle is 2.0.11, released on 5 August 2007.

Lifecycle data from endoflife.date/wordpress, refreshed 17 November 2026. Vendors occasionally change dates; check the vendor’s own lifecycle page before making a compliance decision.

Stop tracking end-of-life dates by hand.

Statance flags end-of-life and vulnerable software on every server automatically.