Classic · Security record
Is Classic safe?
No known vulnerability affects the current version (1.6). 1 issue was found in earlier versions and fixed, the latest disclosed on Aug 12, 2007.
Checked today against the WPVulnerability database, for version 1.6.
How it’s looked after
- Last release
- Jun 13, 2023 (3 years ago)
- Releases in the last year
- 0
- Active installs
- 1K+
1 known vulnerability
- 1 not rated
None affects the current version.
Every known vulnerability in Classic
Newest first, with any that affect the current version at the top.
Fixed in 1.6 · CVE-2007-4483 · Aug 12, 2007 · Wordfence
Questions about Classic’s security
Is Classic safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Classic updated: most attacks target sites that haven’t updated.
Does Classic have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Classic up to date.
Is Classic still maintained?
Its last release was 3 years ago, so it may no longer be actively maintained.
Hear about the next one first
Track your theme on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every theme updated.