WP-Slimbox2 Plugin Vulnerability (CVE-2026-123972)

On this page

Security Alert Summary

The WP-Slimbox2 Plugin is affected by a stored Cross-Site Scripting (XSS) vulnerability (CVE-2026-123972) that allows unauthenticated attackers to inject JavaScript via the “comment” parameter. Injected scripts can execute when a logged-in user interacts with the malicious content, and successful exploitation is reported to grant the attacker\’s account the complete Administrator role.


CVE Details

  • CVE ID: CVE-2026-123972
  • Affected component: WP-Slimbox2 Plugin (plugin for WordPress)
  • Affected versions: All versions up to and including 1.1.3.1
  • Published: November 19, 2026 at 12:18:40 PM
  • Last modified: November 19, 2026 at 12:18:40 PM
  • CVSS v3.1 base score: 7.2 (HIGH)
  • CVSS v3.1 vector string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
  • Authentication / privileges / user interaction: Authentication not required; privileges required: None; user interaction: None (as reported in CVSS data)
  • Primary impact: Confidentiality: Low; Integrity: Low; Availability: None
  • Scope: Changed
  • CWE / weakness ID: CWE-79 (Cross-site Scripting)

Technical Details

This vulnerability is a stored Cross-Site Scripting issue caused by insufficient input sanitization and output escaping of the “comment” parameter in the plugin. An attacker can submit a crafted comment containing an image link or other payload that injects arbitrary script into pages displayed to users.

Successful exploitation, as described in the advisory, requires a logged-in user (typically an administrator) to interact with the attacker\’s image link in the comment. Because unmoderated comments appear in the WordPress moderation queue and administrators routinely interact with moderation items, the moderation queue does not meaningfully prevent exploitation. The advisory reports that successful exploitation results in the attacker\’s account receiving the full Administrator role.

No specific function names or REST endpoints are named in the available data beyond the “comment” parameter and the general lack of adequate sanitization and escaping. The direct impact is execution of attacker-controlled scripts in the context of an authenticated user who views or interacts with the injected content.


How This Could Impact Your Website

Consider a small site with several users: a site owner, an internal editor who moderates comments, and an external contributor who submits content. An attacker submitting a crafted comment could cause administrative users who review moderation items to execute injected scripts. Practical consequences include exposure of limited confidential data tied to the administrator\’s session and profile, and unauthorized modification of content or roles if the injected script performs actions using the administrator\’s privileges. The advisory specifically notes the attacker\’s account can be elevated to Administrator following successful exploitation.

This increases the risk of targeted phishing or social engineering against staff whose emails or names may be accessible, and raises the chance of unauthorized changes to site content or configuration if an elevated account is achieved. If you\’re unsure whether your site is affected or how to assess your current user roles and plugins, it may be worth having a professional review.


Recommended Actions

  • Update the affected plugin as soon as a patched version is available.
  • Review and reduce unnecessary user roles, especially contributor-level accounts and accounts able to submit comments.
  • Enforce strong passwords and enable two-factor authentication for editors and administrators.
  • Remove unused or unmaintained plugins from your site.
  • Monitor site activity and administrator accounts for unusual behavior (new admin accounts, role changes, unexpected content changes).

If you\’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.


References