Smaily for WP
smaily-for-wp · plugin
Known security vulnerabilities for Smaily for WP. Find out in seconds which version runs on your site with WP Lens.
2 known vulnerabilities
1 exploitable without logging in · 1 with no official fix seen · latest May 7, 2025
Listed on wordpress.org · latest 3.1.7 · last updated Aug 8, 2025 · 500+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Medium 6.5
CVE-2024-54286login required≤ 3.1.5
WordPress Smaily for WP plugin <= 3.1.5 - Cross Site Scripting (XSS) vulnerability
- Medium 5.4
CVE-2025-47684unauthenticated · needs a clickno fix seen
WordPress Smaily for WP plugin <= 3.1.7 - Cross Site Request Forgery (CSRF) Vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS). The record lists the latest wordpress.org release (3.1.7) as affected.