Skip to main content
VulnerabilityPublished

CVE-2026-123972: WP-Slimbox2 Plugin · Cross-site Scripting

Affects WP-Slimbox2 PluginSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 19 Nov 2026, 11:50 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 19 Nov 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 18 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
malcalevakWP-Slimbox2 PluginAffected
  • <=1.1.3.1
Fixed in–

AI-suggested

Users should monitor the vendor's channels for updates. Until a fix is available, administrators should exercise caution when interacting with comments in the moderation queue, especially those containing image links or suspicious content. Implementing additional input validation or disabling the WP-Slimbox2 Plugin temporarily may reduce risk.

Description

The WP-Slimbox2 Plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'comment' parameter affecting all versions up to and including 1.1.3.1. This vulnerability allows unauthenticated attackers to inject malicious scripts that execute when a logged-in user, typically an administrator, views the injected comment. Exploitation can lead to privilege escalation where the attacker’s account is granted full Administrator rights. The vulnerability arises from insufficient input sanitization and output escaping. The WordPress comment moderation queue does not effectively mitigate this risk because administrators routinely interact with unmoderated comments.

References

Community reviews

Loading reviews…