Skip to main content
CVE-2026-109234VulnerabilityPublished

The Meow Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content (bbPress

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-109234· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 31 Oct 2026, 07:08 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
tigroumeowMeow LightboxAffected
  • <=5.6.4
Fixed in–

AI-suggested

Users should verify if newer versions beyond 5.6.4 address this issue. Until a fix is available, administrators should consider disabling Output Buffering, the HtmlDomParser engine, or Aggressive Resolve features if feasible, or restrict the use of stored-HTML submission surfaces such as bbPress anonymous replies. Monitor the vendor's advisory channels for official remediation guidance.

Description

The Meow Lightbox WordPress plugin up to version 5.6.4 is vulnerable to stored cross-site scripting (XSS) via the 'post_content' parameter used in bbPress reply bodies. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary JavaScript. Exploitation requires specific plugin settings enabled by the administrator, including Output Buffering, the HtmlDomParser engine, Aggressive Resolve, and a stored-HTML submission surface with a permissive kses allow-list. When these conditions are met, the injected script executes in the context of any user viewing the affected page.

References

Community reviews

Loading reviews…