CVE-2025-47684: WordPress Smaily for WP <= 3.1.6 - Cross Site Request Forgery (CSRF) Vulnerability
First published: Wed May 07 2025(Updated: )
Cross-Site Request Forgery (CSRF) vulnerability in Smaily Smaily for WP allows Cross Site Request Forgery. This issue affects Smaily for WP: from n/a through 3.1.6.
Credit: audit@patchstack.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Smaily for WP | <=3.1.6 | |
| Smaily for WP | <=3.1.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-47684?
CVE-2025-47684 has been classified as a medium severity Cross-Site Request Forgery (CSRF) vulnerability.
How do I fix CVE-2025-47684?
To fix CVE-2025-47684, update Smaily for WP to version 3.1.7 or later.
What versions of Smaily for WP are affected by CVE-2025-47684?
CVE-2025-47684 affects Smaily for WP versions up to and including 3.1.6.
What is Cross-Site Request Forgery in the context of CVE-2025-47684?
Cross-Site Request Forgery in CVE-2025-47684 allows an attacker to trick a user into making unintended requests on their behalf.
Can CVE-2025-47684 affect my WordPress site without Smaily for WP?
CVE-2025-47684 specifically affects sites using the Smaily for WP plugin, so it does not pose a risk to WordPress sites that do not have this plugin installed.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/weakness
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/author
- agent/severity
- agent/event
- collector/epss-latest
- source/FIRST
- agent/source
- agent/tags
- agent/epss
- vendor/smaily
- canonical/smaily for wp
- vendor/wordpress