{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-47684 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47684 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47684 is a medium-severity vulnerability in Smaily for WP, published on 7 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-47684 and fix it if it is affected.\n\nWhat it is: CVE-2025-47684 is a medium-severity vulnerability in Smaily for WP, published on 7 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-47684 in the wild and no public exploit code.\n\nAffected product: Smaily for WP. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-47684/ (Markdown: https://insights.sbomify.com/CVE-2025-47684/index.md)","id":"CVE-2025-47684","markdown":"https://insights.sbomify.com/CVE-2025-47684/index.md","name":"CVE-2025-47684","record":{"aliases":["GHSA-f62m-xcf9-8m88"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can trick authenticated users into performing unwanted actions in the Smaily for WP plugin, potentially altering settings or data.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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 \u003c= 3.1.7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WordPress Smaily for WP plugin \u003c= 3.1.7 - Cross Site Request Forgery (CSRF) Vulnerability","id":"CVE-2025-47684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Contribuinte Checkout plugin \u003c= 2.0.03 - Cross Site Request Forgery (CSRF) to Stored XSS vulnerability","id":"CVE-2025-47685"},"packages":[],"prev":{"headline":"WordPress WP Maintenance plugin \u003c= 6.1.9.7 - PHP Object Injection Vulnerability","id":"CVE-2025-47683"},"products":["Smaily for WP"],"published":"2025-05-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Smaily"]},"summary":"Attackers can trick authenticated users into performing unwanted actions in the Smaily for WP plugin, potentially altering settings or data.","url":"https://insights.sbomify.com/CVE-2025-47684/"}