WordPress plugin
Smaily for WP security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High0
- Medium2
- Low0
All Smaily for WP vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium4.3 | Cross-Site Request Forgery ≤3.1.6No patch available | CVE-2025-47684 | |
| Medium6.4 | Authenticated (Contributor+) Stored Cross-Site Scripting ≤3.1.5Update to 3.1.6 | CVE-2024-54286 |
- Medium4.3Cross-Site Request Forgery
≤3.1.6No patch available
- Medium6.4Authenticated (Contributor+) Stored Cross-Site Scripting
≤3.1.5Update to 3.1.6
Smaily for WP: common questions
Does Smaily for WP have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in Smaily for WP: 2 medium. At least one is not fixed in the latest version.
How do I check which version of Smaily for WP I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Smaily for WP vulnerability?
CVE-2025-47684, published May 7, 2025: Smaily for WP <= 3.1.6 - Cross-Site Request Forgery. Severity: Medium (CVSS 4.3).
Is any Smaily for WP vulnerability listed in CISA KEV?
No. None of the known Smaily for WP vulnerabilities is currently listed in the CISA KEV catalog.