Silkalns vulnerabilities
5 vulnerabilities
Known vulnerabilities in Silkalns products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 7 products.
Products
7- Activello4 vulnerabilities
- Newspaper X2 vulnerabilities
- Sparkling2 vulnerabilities
- Bonkers1 vulnerabilities
- Illdy1 vulnerabilities
- Pixova Lite1 vulnerabilities
- Shapely1 vulnerabilities
CVE-2020-36721colorlibactivello+20
EPSS score0.97%
The Brilliance <= 1.2.7, Activello <= 1.4.0, and Newspaper X <= 1.3.1 themes for WordPress are vulnerable to Plugin Activation/Deactivation. This is due to the 'activello_activate_plugin' and 'activello_deactivate_plugin' functions in the 'inc/welcome-screen/class-activello-welcome.php' file missing capability and security checks/nonces. This makes it possible for unauthenticated attackers to activate and deactivate arbitrary plugins installed on a vulnerable site.CVE-2020-36708colorlibactivello+42EPSS score65.34%
The following themes for WordPress are vulnerable to Function Injections in versions up to and including Shapely <= 1.2.7, NewsMag <= 2.4.1, Activello <= 1.4.0, Illdy <= 2.1.4, Allegiant <= 1.2.2, Newspaper X <= 1.3.1, Pixova Lite <= 2.0.5, Brilliance <= 1.2.7, MedZone Lite <= 1.2.4, Regina Lite <= 2.0.4, Transcend <= 1.1.8, Affluent <= 1.1.0, Bonkers <= 1.0.4, Antreas <= 1.0.2, Sparkling <= 2.4.8, and NatureMag Lite <= 1.0.4. This is due to epsilon_framework_ajax_action. This makes it possible for unauthenticated attackers to call functions and achieve remote code execution.CVE-2022-45358colorlibactivello+2EPSS score0.39%
Auth. (subscriber+) Reflected Cross-Site Scripting (XSS) vulnerability in Silkalns Activello theme <= 1.4.4 versions.CVE-2022-45849colorlibactivello_theme+2EPSS score0.47%
Auth. (subscriber+) Reflected Cross-Site Scripting (XSS) vulnerability in Silkalns Activello theme <= 1.4.4 versions.CVE-2024-13423silkalnssparkling+1EPSS score0.38%
The Sparkling theme for WordPress is vulnerable to unauthorized plugin activation/deactivation due to a missing capability check on the 'sparkling_activate_plugin' and 'sparkling_deactivate_plugin' functions in versions up to, and including, 2.4.9. This makes it possible for unauthenticated attackers to activate/deactivate arbitrary plugins.