Live › vulnerability › CVE-2026-109234
The Meow Lightbox plugin for WordPress does not sanitize the bbPress reply body, so stored script can be injected. Anyone who views the injected page runs attacker JavaScript in their browser session.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 06:33 UTC. All times on this page are UTC.
Sites running the Meow Lightbox WordPress plugin up to and including 5.6.4 with Output Buffering, the HtmlDomParser engine and Aggressive Resolve enabled, and with a stored-HTML submission surface such as bbPress anonymous replies. Sites without those non-default settings, or without a public submission form, are less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| meow-lightbox | wordpress-plugin | <= 5.6.4 | 5.6.5 |
5.6.4 or lower.5.6.5 or later (released 2026/10/30)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-109234")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.