Is Meow Lightbox safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (5.6.5). As of 2026-11-04. 2 issues are on record for older versions; version 5.6.5 or newer fixes all of them that state a fix. Keep Meow Lightbox on the latest version (5.6.5) and remove it if you do not use it.

Which versions of Meow Lightbox are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (5.6.4 and older, fixed in 5.6.5); Stored cross-site scripting (XSS) (5.6.2 and older, fixed in 5.6.3). The full list with sources is on this page.

What is the latest version of Meow Lightbox?

5.6.5, according to wordpress.org (last updated 2026-10-30). It has 10,000+ active installs.

What should I do if my Meow Lightbox is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update meow-lightbox). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · meow-lightbox · data as of 2026-11-04

Is Meow Lightbox safe? Known vulnerabilities and latest version

Latest version: 5.6.5
Last updated: 2026-10-30
Active installs: 10,000+
Known issues on record: 2
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 8.1+

The elegant lightbox built for photographers. Fast, responsive, and displays your photos beautifully with EXIF data and maps. You'll love it! 💕 — by Jordy Meow

What to do

Update to the latest version (5.6.5). Anything older than 5.6.5 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get meow-lightbox --field=version shows what you run; wp plugin update meow-lightbox updates it.

Check your version

Known vulnerabilities

2 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.

high 7.2 CVE-2026-109234 · published 2026-10-31

Stored cross-site scripting (XSS) in Meow Lightbox (5.6.4 and older)

Affected: 5.6.4 and older
Fixed in: 5.6.5 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Meow Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content (bbPress reply body)' parameter in all versions up to, and including, 5.6.4 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. This requires the administrator to have enabled Output Buffering, the HtmlDomParser engine, and Aggressive Resolve, as well as a stored-HTML submission surface (such as bbPress anonymous replies) whose kses allow-list preserves img attributes; given these preconditions, a one-shot unauthenticated submission can execute arbitrary JavaScript in the context of any user who views the affected page.

NVD CVE-2026-109234 Wordfence advisory Code change (fix)Plugin source

medium 6.4 CVE-2026-107756 · published 2026-10-14

Stored cross-site scripting (XSS) in Meow Lightbox (5.6.2 and older)

Affected: 5.6.2 and older
Fixed in: 5.6.3 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Meow Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'display_name + comment' parameter in all versions up to, and including, 5.6.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This vulnerability is only exploitable when the plugin's Output Buffering option is enabled (disabled by default), and requires the attacker to have at least one previously approved comment on the site so that subsequent comments are auto-approved by WordPress core.

NVD CVE-2026-107756 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-10-30 — latest release on wordpress.org (5.6.5).
2026-10-31 — Stored cross-site scripting (XSS) disclosed (CVE-2026-109234), fixed in 5.6.5.
2026-10-14 — Stored cross-site scripting (XSS) disclosed (CVE-2026-107756), fixed in 5.6.3.

Free. We check the CVE feeds every day and email you only when a new issue for Meow Lightbox (meow-lightbox) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/meow-lightbox (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/meow-lightbox"><img src="https://laskyr.com/plugins/meow-lightbox/badge.svg" alt="Meow Lightbox vulnerability status"></a>

← Check another plugin · Free hacked-site scan