Cross-Site Scripting
4 records100%First: 2015. Latest: 2025.
Plugin security history
The Wordfence Intelligence dataset currently contains 4 vulnerability records associated with FancyBox for WordPress, published between 2015 and 2025.
Dataset last synchronized: 2026-08-02 09:41:47 UTC
At a glance
| Year | Records | Relative volume |
|---|---|---|
| 2015 | 1 | |
| 2024 | 2 | |
| 2025 | 1 |
| Severity | Records | Share |
|---|---|---|
| High | 1 | 25% |
| Medium | 3 | 75% |
First: 2015. Latest: 2025.
Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.
3.3.63.3.53.3.43.0.3Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.
| Affected range | Vulnerability | Published | Patched version | Severity |
|---|---|---|---|---|
*-3.3.5 | FancyBox for WordPress <= 3.3.5 - Unauthenticated Stored Cross-Site Scripting | May 13, 2025 | 3.3.6 | High |
*-3.3.4 | Multiple Plugins <= (Various Versions) - Authenticated (Contributor+) Stored DOM-Based Cross-Site Scripting via FancyBox JavaScript Library | December 3, 2024 | 3.3.5 | Medium |
3.0.2-3.3.3 | FancyBox for WordPress 3.0.2 - 3.3.3 - Authenticated (Admin+) Stored Cross-Site Scripting | April 5, 2024 | 3.3.4 | Medium |
[*, 3.0.3) | FancyBox for WordPress <= 3.0.2 - Stored Cross-Site Scripting | February 4, 2015 | 3.0.3 | Medium |
Selected source records
Published: May 13, 2025
Published: December 3, 2024
Published: April 5, 2024
Published: February 4, 2015
Published: May 13, 2025
Published: December 3, 2024
Published: February 4, 2015
Published: April 5, 2024
Running an affected version does not prove that a website was compromised. Suspicious redirects, unknown administrators, injected content, unexpected files or recurring malware may require a manual investigation.
Vulnerability data: Wordfence Intelligence. Analysis and practical guidance: 3Zero Digital.
This page aggregates active Production Feed records. Counts are not software-quality rankings, and an affected version does not prove exploitation or infection. Read the full methodology.