Skip to main content
Menu
CVEs

Slimbox unauthenticated stored XSS in comment anchor titles

CVE-2026-123968Published November 19, 2026, updated

7.2HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

Slimbox, a WordPress plugin, has a stored cross-site scripting flaw that lets an attacker inject scripts that run in the browser of anyone who views an affected page. The flaw can be reached remotely, without logging in, by posting a comment with a crafted link title that the plugin later displays unsafely.

Written by a model

Original description

The Slimbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (anchor title within comment HTML)' parameter in all versions up to, and including, 1.0.8 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. WordPress core comment KSES permits unauthenticated commenters to post anchor elements with href and title attributes, so an entity-encoded payload stored in the title attribute survives sanitization verbatim; the browser then decodes the entities when populating the DOM .title property, and the Slimbox library's jQuery .html() caption sink renders it as executable HTML.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-123968 (Slimbox <= 1.0.8 - Unauthenticated Stored Cross-Site Scripting via Comment Anchor title Attribute), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123968 (entry last updated 2026-11-19):
Affected:
- kevinsylvestre Slimbox: through 1.0.8
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123968 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123968 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/cd9c9666-02f5-4602-ac35-3b68e18bf612?source=cve
- https://plugins.trac.wordpress.org/browser/slimbox/trunk/slimbox.php#L21
- https://plugins.trac.wordpress.org/browser/slimbox/trunk/javascript/jquery.slimbox.js#L6
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123968
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123968"}.

Affected versions

cve.now Index

32Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.2/10CVSS 7.2
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 5

Questions about CVE-2026-123968

Is CVE-2026-123968 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-123968?

Slimbox: through 1.0.8.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.