Companion Auto Update · Security record
Is Companion Auto Update safe?
No known vulnerability affects the current version (3.9.4). 6 issues were found in earlier versions and fixed, the latest disclosed on Jul 14, 2025.
Checked 5 days ago against the WPVulnerability database, for version 3.9.4.
How it’s looked after
- Last release
- Mar 21, 2026 (7 months ago)
- Releases in the last year
- 1
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Support resolved
- 0 of 3 threads in two months
- Active installs
- 40K+
6 known vulnerabilities
- 1 critical
- 1 high
- 1 medium
- 3 not rated
None affects the current version.
Disclosed each year
- 20171
- 20182
- 20191
- 20251
Every known vulnerability in Companion Auto Update
Newest first, with any that affect the current version at the top.
Fixed in 3.9.3 · CVE-2025-4369 · Jul 14, 2025 · Wordfence
Fixed in 3.3.6 · Jan 14, 2019 · Wordfence
Fixed in 3.2.1 · CVE-2018-20972 · Oct 2, 2018 · Wordfence
- critical
Local File Inclusion
Fixed in 3.2.1 · CVE-2018-20973 · Oct 1, 2018 · Wordfence
Fixed in 2.9.4 · Jun 1, 2017 · Patchstack
Fixed in 3.3.6 · WPScan
Questions about Companion Auto Update’s security
Is Companion Auto Update safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Companion Auto Update updated: most attacks target sites that haven’t updated.
Does Companion Auto Update have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 6 older issues, fixed in earlier versions, so keep Companion Auto Update up to date.
Is Companion Auto Update still maintained?
Its last release was 7 months ago. Its authors resolved 0 of the 3 support threads opened in the last two months.
Is Companion Auto Update compatible with the latest WordPress?
Companion Auto Update’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
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.