CVE-2025-5939
No known patch is available for this vulnerability.
The affected plugin has been removed from the WordPress.org directory (reason: Security Issue), and no patched version is being distributed through the official directory. If you have the affected software installed, you should uninstall or replace it rather than wait for an update.
Description
The Telegram for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
The Telegram for WP plugin (≤1.6.1) has a stored XSS vulnerability in admin settings, exploitable only on multisite or with unfiltered_html disabled.
Vulnerability
The Telegram for WP plugin for WordPress versions up to and including 1.6.1 contains a Stored Cross-Site Scripting (XSS) vulnerability in its admin settings. The flaw arises from insufficient input sanitization and output escaping, allowing injection of arbitrary web scripts. This vulnerability specifically affects multi-site installations and any installation where the unfiltered_html capability has been disabled. The plugin has been closed from the WordPress.org directory as of June 11, 2025, citing a security issue, and no patched version was released [1].
Exploitation
An authenticated attacker with administrator-level permissions (or higher) can inject malicious scripts via the affected admin settings fields. The attacker must have the ability to save settings; the stored script will then execute whenever any user, including lower-privileged users, accesses the compromised admin page. The attack is limited to environments where unfiltered_html is not enabled (i.e., multisite or sites where that capability has been revoked) [1].
Impact
Successful exploitation allows the attacker to inject arbitrary web scripts that execute in the context of the victim's browser session. This can lead to session hijacking, credential theft, defacement, or redirection to malicious sites. The impact is constrained to the WordPress admin interface, but any user visiting the affected pages may be affected.
Mitigation
The plugin has been closed and removed from the WordPress.org plugin directory as of June 11, 2025, due to an unresolved security issue. No patched version exists or is being distributed. Users should immediately uninstall the Telegram for WP plugin and consider alternative solutions. No workaround is available other than removal [1].
AI Insight generated on May 23, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2(expand)+ 1 more
- (no CPE)
- (no CPE)range: <=1.6.1
Patches
0telegram-for-wpThis plugin has been removed from the WordPress.org directory on 2025-06-11 (reason: Security Issue). No patched version is being distributed through the official directory. Users who have it installed should uninstall it.
Source: api.wordpress.org · directory page
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
2News mentions
0No linked articles in our index yet.