PatchTheCVECVE-2022-3855: The 404 to Start WordPress plugin through 1.6.1 does not sanitise and escape some of its settings, which could
CVE-2022-3855 is a medium-severity flaw (CVSS 4.8) affecting 404 to start. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The 404 to Start WordPress plugin through 1.6.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.8 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | High |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 55%) |
| CISA exploited list | No |
| Published | 2023-01-09 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-3855?
404 to start: upgrade to newer than 1.6.1. Exact commands for each OS are on this page.
Is CVE-2022-3855 being exploited?
CVE-2022-3855 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-3855 affect?
CVE-2022-3855 affects 404 to start. Severity is medium (CVSS 4.8). The 404 to Start WordPress plugin through 1.6.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability
How urgent is CVE-2022-3855?
Priority 33/100. Public exploit reference