TermsFeed AutoTerms · Security record
Is TermsFeed AutoTerms safe?
No known vulnerability affects the current version (3.0.8). 1 issue was found in earlier versions and fixed, the latest disclosed on Jul 18, 2023.
Checked 6 days ago against the WPVulnerability database, for version 3.0.8.
How it’s looked after
- Last release
- Oct 19, 2026 (3 weeks ago)
- Releases in the last year
- 4
- Tested up to
- WordPress 7.1.4
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 70K+
1 known vulnerability
- 1 high
None affects the current version.
Every known vulnerability in TermsFeed AutoTerms
Newest first, with any that affect the current version at the top.
Fixed in 2.0.0 · CVE-2023-33999 · Jul 18, 2023 · WPScan
Questions about TermsFeed AutoTerms’s security
Is TermsFeed AutoTerms safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep TermsFeed AutoTerms updated: most attacks target sites that haven’t updated.
Does TermsFeed AutoTerms have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep TermsFeed AutoTerms up to date.
Is TermsFeed AutoTerms still maintained?
Yes. Its last release was 3 weeks ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is TermsFeed AutoTerms 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.