Security Alert Summary
The Slimbox plugin for WordPress (all versions up to and including 1.0.8) is vulnerable to stored cross-site scripting (XSS) via the comment anchor title attribute. Insufficient input sanitization and output escaping allow an unauthenticated attacker to inject scripts that execute when a user views an affected page.
CVE Details
- CVE ID: CVE-2026-123968
- Affected component: Slimbox plugin for WordPress (vendor: kevinsylvestre)
- Affected versions: All versions up to and including 1.0.8
- Published: November 19, 2026 at 12:18:39 PM UTC
- Last modified: November 19, 2026 at 4:19:33 PM UTC
- CVSS v3.1: Base Score 7.2 – High; Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - Authentication / privileges / user interaction: No authentication required; privileges required: none; user interaction: none
- Primary impact:
- Confidentiality: Low
- Integrity: Low
- Availability: None
- Weakness (CWE): CWE-79 (Improper Neutralization of Input During Web Page Generation – Cross-site Scripting)
Technical Details
The plugin fails to properly sanitize and escape content placed in the comment anchor title attribute. WordPress core comment KSES allows unauthenticated commenters to submit anchor (<a>) elements with href and title attributes. An entity-encoded payload stored in the title attribute survives KSES sanitization; when the browser populates the DOM .title property it decodes those entities. The Slimbox library then inserts that value into its caption sink using jQuery’s .html() method, which renders the decoded content as executable HTML and enables stored XSS.
The vulnerability exists because input survives server-side filtering and is later inserted into the page without proper output encoding before being interpreted by the browser. The description identifies the comment “anchor title within comment HTML” parameter and the Slimbox library’s use of .html() as the rendering sink responsible for execution.
How This Could Impact Your Website
On a multi-user WordPress site, an unauthenticated commenter could submit a crafted comment that stores a payload in the anchor title attribute. When internal staff, site owners, or external contributors view the page, the payload can execute in their browsers. Practical consequences include exposure of internal user information available to the page context (for example, visible email addresses or profile data accessible in the same page), and an increased risk of targeted phishing or social engineering campaigns against staff whose sessions or details can be observed in the browser context.
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 and author roles that allow comment posting.
- Enforce strong passwords and enable two-factor authentication for editor and administrator accounts.
- Remove unused or unmaintained plugins to reduce attack surface.
- Monitor site activity and logs for unusual comment submissions or other anomalous behavior.
If you’d like help reviewing your plugins, user roles, or overall WordPress security posture, our team at Freshy is happy to help.