404 To 301
Vendor:
First CVE: Aug 16, 2019 · Active for 6 years
2
Total CVEs
More Total CVEs than 49% of tracked products
1.0
Avg CVEs / Year
Bottom 1%
7.6
Avg CVSS
Higher Avg CVSS than 60% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact 404 To 301 over time
Volume of CVEsAvg CVSS Base Score
First CVE
Aug 16, 2019
6 years ago
Most Recent CVE
Jun 7, 2023
1,144 days ago
CVE Severity & Scoring
404 To 3012 CVEs
50%
50%
All CVEs352,708 CVEs
45%
40%
11%
MediumCritical
Attack Vector
Local0 (0.0%)
Network2 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low2 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None1 (50.0%)
Unknown0 (0.0%)
Required1 (50.0%)
Privileges Required
Low1 (50.0%)
High0 (0.0%)
None1 (50.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2015-9323CRITICAL The 404-to-301 plugin before 2.0.3 for WordPress has SQL injection. | Aug 16, 2019 | 9.8 | 68 | NO | YES |
CVE-2021-4338MEDIUM The 404 to 301 plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on the open_redirect & save_redirect functions in versions up to, and inc | Jun 7, 2023 | 5.4 | 18 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (2 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
1 CVE
50.0% of CVEs· 98th percentile
ExploitDB
1 CVE
50.0% of CVEs· 91st percentile
Social Chatter
Signals from CVEs in this product scope (2 CVEs).
Media Mentions
Signals from CVEs in this product scope (2 CVEs).
Top CNAs Publishing CVEs For 404 To 301
Top CWEs
Versions
No cataloged versions.