Stream stored XSS via user display name field
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Stream – Activity Log & Audit Trail WordPress plugin has a stored DOM-based cross-site scripting flaw in the display name field. A remote attacker with subscriber-level login or higher can inject scripts that run whenever a user opens the affected page, but only on sites with 50 or fewer total users.
Written by a model
Original description
The Stream – Activity Log & Audit Trail plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'display_name' parameter in all versions up to, and including, 4.4.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable on sites with 50 or fewer total users, as above that threshold the user filter uses an AJAX endpoint that returns entity-encoded labels and is not affected.
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-119216 (Stream <= 4.4.0 - Authenticated (Subscriber+) Stored DOM-Based Cross-Site Scripting via User Display Name), 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-119216 (entry last updated 2026-11-21):
Affected:
- xwp Stream – Activity Log & Audit Trail: through 4.4.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119216 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119216 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/b6d34376-26ed-4542-8628-b23f98d83886?source=cve
- https://plugins.trac.wordpress.org/browser/stream/tags/4.4.0/build/admin.js
- https://plugins.trac.wordpress.org/browser/stream/tags/4.4.0/classes/class-list-table.php#L1216
- https://plugins.trac.wordpress.org/browser/stream/tags/4.4.0/classes/class-author.php#L113
- https://plugins.trac.wordpress.org/browser/stream/tags/4.4.0/classes/class-admin.php#L175
- https://github.com/xwp/stream/pull/2066
- https://plugins.trac.wordpress.org/changeset/3798232/stream/trunk/build/admin.js
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-119216
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-119216"}.Affected versions
- xwp Stream – Activity Log & Audit Trailthrough 4.4.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.4/10CVSS 6.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 9
Questions about CVE-2026-119216
Is CVE-2026-119216 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-119216?
Stream – Activity Log & Audit Trail: through 4.4.0.
Source: cve.now feed data
Related
- CVE-2026-11907Stream <= 4.2.0 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Disclosure via Heartbeat API
- CVE-2026-127133Stream <= 4.5.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via BuddyPress Group Name
- CVE-2024-7423Stream <= 4.0.1 - Cross-Site Request Forgery to Arbitrary Options Update
- CVE-2024-13879Stream <= 4.0.2 - Authenticated (Admin+) Server-Side Request Forgery
- CVE-2022-43490WordPress Stream Plugin <= 3.9.2 is vulnerable to Cross Site Request Forgery (CSRF)
- CVE-2022-43450WordPress Stream Plugin <= 3.9.2 is vulnerable to Insecure Direct Object References (IDOR)
No corrections so far. Something wrong on this page? Report an error.