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

Plugin security history

PrettyPhoto – Simple Lightbox Plugin Vulnerability History & Security Timeline

The Wordfence Intelligence dataset currently contains 3 vulnerability records associated with PrettyPhoto – Simple Lightbox Plugin, published between 2015 and 2025.

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

At a glance

Security Snapshot

3Total records
0Critical
0High
3Medium
0Low
0Informational
2Patched records
1Currently marked unpatched
2015-05-05First disclosure
2025-09-05Latest disclosure
2 of 3CVE coverage

Use this history

Check and watch PrettyPhoto – Simple Lightbox Plugin.

A history record does not establish whether the version installed on your website is affected. Enter the exact version in the checker, or add this software to a private Critical/High alert watchlist.

Year-by-Year Timeline

YearRecordsRelative volume
201511 records
202411 records
202511 records

Severity Breakdown

SeverityRecordsShare
Medium3100%

Vulnerability-Type Breakdown

Cross-Site Scripting

3 records100%

First: 2015. Latest: 2025.

Patch Status

Patched
2
Currently marked unpatched
1
Unknown status
0

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

Latest Known Patched Versions

  • 1.2.4
  • 1.2

Affected-Version History

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

Affected rangeVulnerabilityPublishedPatched versionSeverity
*-1.2.4prettyPhoto <= 1.2.4 - Authenticated (Contributor+) Stored Cross-Site ScriptingSeptember 5, 2025Not suppliedMedium
*-1.2.3WordPress prettyPhoto <= 1.2.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via url ParameterJune 5, 20241.2.4Medium
*-1.1WordPress prettyPhoto <= 1.1 - DOM Cross-Site ScriptingMay 5, 20151.2Medium

Selected source records

Latest Records

MediumCVE-2025-58808

prettyPhoto <= 1.2.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: September 5, 2025

Affected versions
*-1.2.4
Patched versions
Not supplied
Original Wordfence record
MediumCVE-2024-5162

WordPress prettyPhoto <= 1.2.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via url Parameter

Published: June 5, 2024

Affected versions
*-1.2.3
Patched versions
1.2.4
Original Wordfence record
Medium

WordPress prettyPhoto <= 1.1 - DOM Cross-Site Scripting

Published: May 5, 2015

Affected versions
*-1.1
Patched versions
1.2
Original Wordfence record

Highest-Severity Records

MediumCVE-2024-5162

WordPress prettyPhoto <= 1.2.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via url Parameter

Published: June 5, 2024

Affected versions
*-1.2.3
Patched versions
1.2.4
Original Wordfence record
MediumCVE-2025-58808

prettyPhoto <= 1.2.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: September 5, 2025

Affected versions
*-1.2.4
Patched versions
Not supplied
Original Wordfence record
Medium

WordPress prettyPhoto <= 1.1 - DOM Cross-Site Scripting

Published: May 5, 2015

Affected versions
*-1.1
Patched versions
1.2
Original Wordfence record

Currently Marked Unpatched Records

MediumCVE-2025-58808

prettyPhoto <= 1.2.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

Published: September 5, 2025

Affected versions
*-1.2.4
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