WordPress plugin
404 to Start security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium1
- Low0
All 404 to Start vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.5 | Authenticated (Administrator+) Stored Cross-Site Scripting ≤1.6.1No patch available | CVE-2022-3855 |
- Medium5.5Authenticated (Administrator+) Stored Cross-Site Scripting
≤1.6.1No patch available
404 to Start: common questions
Does 404 to Start have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in 404 to Start: 1 medium. At least one is not fixed in the latest version.
How do I check which version of 404 to Start 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 404 to Start vulnerability?
CVE-2022-3855, published Dec 15, 2022: 404 to Start <= 1.6.1 - Authenticated (Administrator+) Stored Cross-Site Scripting. Severity: Medium (CVSS 5.5).
Is any 404 to Start vulnerability listed in CISA KEV?
No. None of the known 404 to Start vulnerabilities is currently listed in the CISA KEV catalog.