WordPress plugin
Companion Auto Update security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 4 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical1
- High2
- Medium1
- Low0
All Companion Auto Update vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Authenticated (Admin+) SQL Injection <3.3.6Update to 3.3.6 | — | |
| High8.8 | Cross-Site Request Forgery <3.2.1Update to 3.2.1 | CVE-2018-20972 | |
| Critical9.8 | Local File Inclusion <3.2.1Update to 3.2.1 | CVE-2018-20973 |
- High7.2Authenticated (Admin+) SQL Injection
<3.3.6Update to 3.3.6
- High8.8Cross-Site Request Forgery
<3.2.1Update to 3.2.1
- Critical9.8Local File Inclusion
<3.2.1Update to 3.2.1
Companion Auto Update: common questions
Does Companion Auto Update have known vulnerabilities?
Yes. VulnCrest Radar lists 4 known vulnerabilities in Companion Auto Update: 1 critical, 2 high, 1 medium. None are known to affect version null.
How do I check which version of Companion Auto Update I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Companion Auto Update vulnerability?
CVE-2025-4369, published Jul 14, 2025: Companion Auto Update <= 3.9.2 - Authenticated (Administrator+) Stored Cross-Site Scripting via update_delay_days parameter. Severity: Medium (CVSS 5.5).
Is any Companion Auto Update vulnerability listed in CISA KEV?
No. None of the known Companion Auto Update vulnerabilities is currently listed in the CISA KEV catalog.