CVE-2025-14887
Stored XSS in twinklesmtp WordPress Plugin Sender Settings
Publication date: 2026-01-07
Last updated on: 2026-01-07
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| twinklesmtp | twinklesmtp | to 1.0.3 (inc) |
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 twinklesmtp Email Service Provider plugin for WordPress. It occurs due to insufficient input sanitization and output escaping in the plugin's sender settings. Authenticated users with administrator-level permissions or higher can inject malicious web scripts that execute when other users access the affected pages. It affects multi-site WordPress installations and installations where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
The vulnerability allows attackers with administrator-level access to inject malicious scripts into the website. These scripts can execute in the browsers of users who visit the injected pages, potentially leading to unauthorized actions such as stealing session tokens, defacing the site, or performing actions on behalf of users without their consent. This can compromise the security and integrity of the affected WordPress site.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking if the TwinkleSMTP plugin version is 1.03 or earlier on a WordPress multi-site installation with unfiltered_html disabled, and if administrator-level users have injected scripts in the sender settings. Since the vulnerability is a stored XSS via sender settings, you can inspect the sender settings pages for suspicious scripts. There are no specific commands provided in the resources to detect this vulnerability automatically. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the TwinkleSMTP plugin to a version later than 1.03 where the vulnerability is fixed, or if an update is not available, restricting administrator-level access to the sender settings page, enabling unfiltered_html to allow proper HTML filtering, and auditing sender settings for malicious scripts to remove them. Additionally, consider applying input sanitization and output escaping manually if possible. [1]