CVE-2025-47684 MEDIUM

CVE-2025-47684: WordPress Smaily for WP plugin <= 3.1.7 - Cross Site Request Forgery (CSRF) Vulnerability

Vendor Smaily

Product Smaily for WP

Weakness CWE-352 · CSRF

Published May 7, 2025

Last update April 28, 2026

View on NVD All CVEs

CVSS base score

5.4/10

Attack vector Network

Attack complexity Low

Privileges required None

User interaction Required

Confidentiality None

Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

What the vulnerability does

01Description

Cross-Site Request Forgery (CSRF) vulnerability in Smaily Smaily for WP smaily-for-wp allows Cross Site Request Forgery.This issue affects Smaily for WP: from n/a through <= 3.1.7.

Explanation of Vulnerability in Simple Terms

02Summary

Smaily for WP versions 3.1.7 and earlier contain a cross-site request forgery (CSRF) vulnerability. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the Smaily plugin without the admin's knowledge or consent. This could allow unauthorized changes to plugin settings or data.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the Smaily plugin by tricking a logged-in admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker could modify Smaily plugin settings or data if they trick your admin into visiting a malicious page while logged in.

Conditions required to exploit

05Prerequisites

A site admin must be logged in and visit a page controlled by the attacker (e.g., via a phishing link or malicious ad).

Key dates

06Disclosure timeline

May 7, 2025 CVE published

April 28, 2026 Record updated

External resources

07References

NVD — National Vulnerability Database https://nvd.nist.gov/vuln/detail/CVE-2025-47684 CWE — Common Weakness Enumeration https://cwe.mitre.org/data/definitions/352.html AskarLabs — CWE-352 write-up Cross-Site Request Forgery

Related vulnerabilities