Stored XSS via unescaped username block attribute
Published May 30, 2025 · Updated Apr 8, 2026
Stored cross-site scripting in Ninja Team WP Telegram Chat Widget 1.1 and earlier allows remote authenticated users to inject scripts via username. The block rendering path in blocks/src/init.php accepts the username attribute without sufficient input sanitization and emits it without context-appropriate output escaping. Contributor-level access is sufficient to store the payload in a page, and the script runs in a visitor browser when that page is opened, permitting actions within that visitor’s WordPress session.
Summary
What happened
Stored cross-site scripting in Ninja Team WP Telegram Chat Widget 1.1 and earlier allows remote authenticated users to inject scripts via username. The block rendering path in blocks/src/init.php accepts the username attribute without sufficient input sanitization and emits it without context-appropriate output escaping. Contributor-level access is sufficient to store the payload in a page, and the script runs in a visitor browser when that page is opened, permitting actions within that visitor’s WordPress session.
The record
- CVE
- CVE-2025-5236
- Published
- May 30, 2025
- Updated
- Apr 8, 2026
- Vendor
- Ninja Team
- Product
- WP Telegram Chat Widget
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 30, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo