Plugins · fancy-facebook-comments · data as of 2026-11-04
Is Fancy Comments WordPress safe? Known vulnerabilities and latest version
- Status
- Closed 2026-10-14
- Known issues on record
- 3
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate fancy-facebook-comments && wp plugin delete fancy-facebook-comments
Check your version
Known vulnerabilities
3 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 3 record(s) do not state which versions are affected.
high 7.1 CVE-2026-110384 · published 2026-10-17
Reflected cross-site scripting (XSS) in Fancy Comments WordPress (1.2.21 and older)
- Affected
- 1.2.21 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Heateor Support Fancy Comments WordPress fancy-facebook-comments allows Reflected XSS.This issue affects Fancy Comments WordPress: from n/a through 1.2.21.
medium 5.4 CVE-2024-29804 · published 2024-03-27
Stored cross-site scripting (XSS) in Fancy Comments WordPress (1.2.14 and older)
- Affected
- 1.2.14 and older
- Fixed in
- 1.2.15
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Team Heateor Fancy Comments WordPress allows Stored XSS.This issue affects Fancy Comments WordPress: from n/a through 1.2.14.
medium 5.4 CVE-2023-23670 · published 2023-03-30
Cross-site scripting (XSS) in Fancy Comments WordPress (1.2.10 and older)
- Affected
- 1.2.10 and older
- Fixed in
- 1.2.11
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Auth. (contributor+) Cross-Site Scripting (XSS) vulnerability in Team Heateor Fancy Comments WordPress plugin <= 1.2.10 versions.
Recent activity
- 2026-10-14 — closed on wordpress.org.
- 2026-10-17 — Reflected cross-site scripting (XSS) disclosed (CVE-2026-110384), fix version not stated.
- 2024-03-27 — Stored cross-site scripting (XSS) disclosed (CVE-2024-29804), fixed in 1.2.15.
- 2023-03-30 — Cross-site scripting (XSS) disclosed (CVE-2023-23670), fixed in 1.2.11.
Get an email when Fancy Comments WordPress has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Fancy Comments WordPress (fancy-facebook-comments) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Cross-site scripting (XSS) (3)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/fancy-facebook-comments (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/fancy-facebook-comments"><img src="https://laskyr.com/plugins/fancy-facebook-comments/badge.svg" alt="Fancy Comments WordPress vulnerability status"></a>