CVE-2025-5939
BaseFortify
Publication date: 2025-06-13
Last updated on: 2025-06-16
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Telegram for WP WordPress plugin (up to version 1.6.1). It occurs because the plugin does not properly sanitize or escape input in the admin settings. An attacker with administrator-level permissions can inject malicious scripts that will execute whenever a user accesses the affected page. This vulnerability only affects multi-site WordPress installations or those where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
If exploited, this vulnerability allows an attacker with admin privileges to inject malicious scripts into the WordPress site. These scripts can execute in the browsers of users who visit the injected pages, potentially leading to theft of sensitive information, session hijacking, or other malicious actions. Since it requires administrator-level access, the risk is limited to compromised or malicious admins, but the impact can include loss of data integrity and user trust.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking if the Telegram for WP plugin version 1.6.1 or earlier is installed on a WordPress multi-site setup with unfiltered_html disabled. Since the vulnerability is a stored cross-site scripting via admin settings, detection can include reviewing admin settings for suspicious script injections. Specific commands are not provided in the resources, but generally, you can list installed plugins and their versions using WordPress CLI commands such as 'wp plugin list' and inspect plugin files or admin settings for injected scripts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or removing the Telegram for WP plugin, especially since it has been temporarily closed and removed from download pending a security review. Additionally, ensure that only trusted administrators have access, and consider enabling unfiltered_html if feasible. Monitoring and cleaning any injected scripts in admin settings is also recommended. [1]