Classic Editor + · Security record
Is Classic Editor + safe?
No known vulnerability affects the current version (4.4.5). 5 issues were found in earlier versions and fixed, the latest disclosed on Jan 24, 2022.
Checked 3 days ago against the WPVulnerability database, for version 4.4.5.
How it’s looked after
- Last release
- Oct 23, 2026 (2 weeks ago)
- Releases in the last year
- 5
- Tested up to
- WordPress 7.1.4
- Support resolved
- 2 of 2 threads in two months
- Active installs
- 30K+
5 known vulnerabilities
- 5 not rated
None affects the current version.
Every known vulnerability in Classic Editor +
Newest first, with any that affect the current version at the top.
Fixed in 2.6.4 · Jan 24, 2022 · Wordfence
Fixed in 2.6.4 · Jan 24, 2022 · Patchstack
Fixed in 2.6.4 · Jan 24, 2022 · Patchstack
Fixed in 2.6.4 · WPScan
Fixed in 2.6.4 · WPScan
Questions about Classic Editor +’s security
Is Classic Editor + safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Classic Editor + updated: most attacks target sites that haven’t updated.
Does Classic Editor + have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 5 older issues, fixed in earlier versions, so keep Classic Editor + up to date.
Is Classic Editor + still maintained?
Yes. Its last release was 2 weeks ago. Its authors resolved 2 of the 2 support threads opened in the last two months.
Is Classic Editor + compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.1.4, the current version.
Hear about the next one first
Track your plugin 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 plugin updated.