HomeWordPress vulnerabilitiesFancyBox for WordPress
FancyBox for WordPress vulnerabilities
FancyBox for WordPress has 3 known vulnerabilities in this database. The most recent published record is dated 18 Nov 2026.
- Known vulnerabilities
- 3
- Active installs
- 30,000+
- Latest version
- 3.4.3
- Last updated
- 9 Nov 2026
- Most recent
- 18 Nov 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-96571 | High 7.2 | Up to 3.4.2 | Fixed in a later version (latest 3.4.3) | 4 d ago |
| Cross-site scripting (XSS) CVE-2024-0662 | Medium 4.4 | Before 3.3.3 | Fixed in 3.3.3 | 9 Apr 2024 |
| Cross-site scripting (XSS) CVE-2015-1494 | Not scored | Up to 3.0.2 | Fixed in a later version (latest 3.4.3) | 17 Feb 2015 |
Read the published descriptions
- CVE-2026-96571, 18 Nov 2026
- The FancyBox for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Anchor 'href' Attribute in all versions up to, and including, 3.4.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the attacker to wrap the payload anchor around a smilie shortcode (e.g., :mrgreen:), which WordPress renders as an <img> element, satisfying the plugin's a:has(img) enrollment selector and disguising the malicious link as an ordinary comment emoticon. CVE record
- CVE-2024-0662, 9 Apr 2024
- The FancyBox for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in versions 3.0.2 to 3.3.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled. CVE record
- CVE-2015-1494, 17 Feb 2015
- The FancyBox for WordPress plugin before 3.0.3 for WordPress does not properly restrict access, which allows remote attackers to conduct cross-site scripting (XSS) attacks via an mfbfw[*] parameter in an update action to wp-admin/admin-post.php, as demonstrated by the mfbfw[padding] parameter and exploited in the wild in February 2015. CVE record
What to do if you run FancyBox for WordPress
If you run FancyBox for WordPress, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new FancyBox for WordPress vulnerabilities
Free. We email you when a new vulnerability is published for FancyBox for WordPress, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.