WP-Slimbox2 Plugin unauthenticated stored XSS in comment link titles
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The WP-Slimbox2 Plugin by malcalevak has a stored cross-site scripting flaw in comment handling. An unauthenticated attacker can remotely inject scripts that run when a user opens an affected page. If a logged-in administrator clicks the attacker's image link in a comment, the attacker's own account can receive the full Administrator role.
Written by a model
Original description
The WP-Slimbox2 Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.1.3.1 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. Successful exploitation requires a logged-in user, typically an administrator, to click the attacker's image link in the comment; however, because unmoderated comments appear in the WordPress moderation queue where administrators routinely interact with them, the moderation gate does not meaningfully prevent exploitation. Successful exploitation causes the attacker's own account to receive the complete Administrator role.
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-123972 (WP-Slimbox2 Plugin <= 1.1.3.1 - Unauthenticated Stored Cross-Site Scripting via Comment Link 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-123972 (entry last updated 2026-11-19):
Affected:
- malcalevak WP-Slimbox2 Plugin: through 1.1.3.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123972 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123972 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/2d3402c3-d0b6-4226-be05-9b2b2e2bb2b8?source=cve
- https://plugins.trac.wordpress.org/browser/wp-slimbox2/tags/1.1.3.1/index.php#L43
- https://plugins.trac.wordpress.org/browser/wp-slimbox2/tags/1.1.3.1/src/slimbox2_autoload.js#L63
- https://plugins.trac.wordpress.org/browser/wp-slimbox2/tags/1.1.3.1/javascript/slimbox2.js
- https://plugins.trac.wordpress.org/browser/wp-slimbox2/tags/1.1.3.1/src/slimbox2_autoload.js#L79
- https://plugins.trac.wordpress.org/browser/wp-slimbox2/tags/1.1.3.1/index.php#L83
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-123972
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-123972"}.Affected versions
- malcalevak WP-Slimbox2 Pluginthrough 1.1.3.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · 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 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
Questions about CVE-2026-123972
Is CVE-2026-123972 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-123972?
WP-Slimbox2 Plugin: through 1.1.3.1.
Source: cve.now feed data
Related
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-130158RepoManager: Stored XSS via host-reported package metadata
- CVE-2026-131260Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-131258Stored Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-59988django-docutils unsafe Docutils defaults allow local file disclosure, SSRF, and stored XSS
No corrections so far. Something wrong on this page? Report an error.