Skip to content
Founder-led WordPress incident response and care Request an assessment
3zerodigital Request a Website Assessment

Plugin security history

wp-flipslideshow Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 1 vulnerability records associated with wp-flipslideshow, published between 2012 and 2012.

Dataset last synchronized: 2026-08-03 00:31:25 UTC

At a glance

Security Snapshot

1Total records
0Critical
0High
1Medium
0Low
0Informational
1Patched records
0Currently marked unpatched
2012-11-09First disclosure
2012-11-09Latest disclosure
1 of 1CVE coverage

Year-by-Year Timeline

YearRecordsRelative volume
201211 records

Severity Breakdown

SeverityRecordsShare
Medium1100%

Vulnerability-Type Breakdown

Cross-Site Scripting

1 record100%

First: 2012. Latest: 2012.

Patch Status

Patched
1
Currently marked unpatched
0
Unknown status
0

Patch status reflects the latest successfully synchronized source dataset and must be checked against the installed version.

Latest Known Patched Versions

  • 2.2

Affected-Version History

Ranges are deduplicated by source range record and shown with the associated disclosure and known patched versions.

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-2.1SWFUpload <= 2.2.0.1 - Cross-Site ScriptingNovember 9, 20122.2Medium

Selected source records

Latest Records

MediumCVE-2012-3414

SWFUpload <= 2.2.0.1 - Cross-Site Scripting

Published: November 9, 2012

Affected versions
*
Patched versions
Not supplied
Affected versions
*-3.4
Patched versions
3.5
Affected versions
*
Patched versions
Not supplied
Affected versions
*-1.0
Patched versions
Not supplied
Affected versions
*-1.7
Patched versions
Not supplied
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.1.6
Patched versions
2.1.7
Affected versions
*-2.1
Patched versions
2.3
Affected versions
*
Patched versions
Not supplied
Affected versions
[*, 3.2)
Patched versions
3.2
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.3
Patched versions
2.4
Affected versions
[*, 3.0)
Patched versions
3.0
Affected versions
*-2.3
Patched versions
2.4
Affected versions
*
Patched versions
Not supplied
Affected versions
[*, 4.4)
Patched versions
4.4
Affected versions
*-2.4
Patched versions
2.6
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.1
Patched versions
2.2
Affected versions
[*, 3.3.2)
Patched versions
3.3.2
Affected versions
[*, 2.3)
Patched versions
2.3
Affected versions
*-3.10
Patched versions
3.11
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-2.0
Patched versions
2.1
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-2.3
Patched versions
2.4
Affected versions
*-2.1
Patched versions
2.2
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*
Patched versions
Not supplied
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-3.3
Patched versions
3.4
Affected versions
[*, 2.12)
Patched versions
2.12
Affected versions
*
Patched versions
Not supplied
Affected versions
*-1.9.6
Patched versions
1.9.7
Affected versions
*-3.5
Patched versions
3.6
Affected versions
*
Patched versions
Not supplied
Affected versions
*
Patched versions
Not supplied
Original Wordfence record

Highest-Severity Records

MediumCVE-2012-3414

SWFUpload <= 2.2.0.1 - Cross-Site Scripting

Published: November 9, 2012

Affected versions
*
Patched versions
Not supplied
Affected versions
*-3.4
Patched versions
3.5
Affected versions
*
Patched versions
Not supplied
Affected versions
*-1.0
Patched versions
Not supplied
Affected versions
*-1.7
Patched versions
Not supplied
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.1.6
Patched versions
2.1.7
Affected versions
*-2.1
Patched versions
2.3
Affected versions
*
Patched versions
Not supplied
Affected versions
[*, 3.2)
Patched versions
3.2
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.3
Patched versions
2.4
Affected versions
[*, 3.0)
Patched versions
3.0
Affected versions
*-2.3
Patched versions
2.4
Affected versions
*
Patched versions
Not supplied
Affected versions
[*, 4.4)
Patched versions
4.4
Affected versions
*-2.4
Patched versions
2.6
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.1
Patched versions
2.2
Affected versions
[*, 3.3.2)
Patched versions
3.3.2
Affected versions
[*, 2.3)
Patched versions
2.3
Affected versions
*-3.10
Patched versions
3.11
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-2.0
Patched versions
2.1
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-2.3
Patched versions
2.4
Affected versions
*-2.1
Patched versions
2.2
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*
Patched versions
Not supplied
Affected versions
*
Patched versions
Not supplied
Affected versions
*-2.2
Patched versions
2.3
Affected versions
*-3.3
Patched versions
3.4
Affected versions
[*, 2.12)
Patched versions
2.12
Affected versions
*
Patched versions
Not supplied
Affected versions
*-1.9.6
Patched versions
1.9.7
Affected versions
*-3.5
Patched versions
3.6
Affected versions
*
Patched versions
Not supplied
Affected versions
*
Patched versions
Not supplied
Original Wordfence record

View all associated vulnerabilities

Need help reviewing an exposed WordPress website?

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.

Data Source, Attribution and Methodology

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.

Return to the Security History Directory