Alexmoss vulnerabilities
4 vulnerabilities
Known vulnerabilities in Alexmoss products, newest first, with CVSS severity, EPSS, KEV listings and ransomware use, across 4 products.
Products
4- Firecask Like & Share Button1 vulnerabilities
- Firecask’S Twitter Follow Button1 vulnerabilities
- Opensea1 vulnerabilities
- Whatsapp Share Button1 vulnerabilities
CVE-2022-49745starpluginseasy_age_verify+1239
EPSS score0.44%
The Freemius SDK, as used by hundreds of WordPress plugin and theme developers, was vulnerable to Cross-Site Request Forgery and Information disclosure due to missing capability checks and nonce protection on the _get_debug_log, _get_db_option, and the _set_db_option functions in versions up to, and including 2.4.2. Any WordPress plugin or theme running a version of Freemius less than 2.4.3 is vulnerable.CVE-2024-11226alexmossfirecask like & share button+1EPSS score0.34%
The FireCask Like & Share Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'width' parameter in all versions up to, and including, 1.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.CVE-2024-10116alexmossfirecask’s twitter follow button+2EPSS score0.40%
The Twitter Follow Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'username' parameter in all versions up to, and including, 0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.CVE-2023-5668alexmosswhatsapp share button+2EPSS score0.39%
The WhatsApp Share Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'whatsapp' shortcode in all versions up to, and including, 1.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.