The IgniteUp WordPress plugin through 3.4.1 does not sanitise and escape some fields when high privilege users don't have the unfiltered_html capability, which could lead to Stored Cross-Site Scripting issues
Product
getigniteup igniteup vulnerabilities
5 published CVES affecting getigniteup igniteup, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 2
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest getigniteup igniteup CVEs
Newest publication first
-
MediumCVSS 5.4 EPSS 0.60%
-
CVE-2019-17237 IgniteUp – Coming Soon and Maintenance Mode <= 3.4.0 - Cross-Site Request Forgery
PublishedHighCVSS 8.8 EPSS 0.74%includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows CSRF.
-
CVE-2019-17236 IgniteUp – Coming Soon and Maintenance Mode <= 3.4 - Stored Cross-Site Scripting
PublishedMediumCVSS 6.1 EPSS 0.97%includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress is vulnerable to stored XSS.
-
CVE-2019-17235 IgniteUp – Coming Soon and Maintenance Mode <= 3.4.0 - Information Disclosure
PublishedMediumCVSS 5.3 EPSS 1.4%includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows information disclosure.
-
HighCVSS 7.5 EPSS 3.2%
includes/class-coming-soon-creator.php in the igniteup plugin through 3.4 for WordPress allows unauthenticated arbitrary file deletion.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.