CVE-2026-2840
Stored XSS in Email Encoder WordPress Plugin Allows Script Injection
Publication date: 2026-04-16
Last updated on: 2026-04-16
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| email_encoder | email_encoder | to 2.4.4 (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?
The Email Encoder – Protect Email Addresses and Phone Numbers plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in its 'eeb_mailto' shortcode. This vulnerability exists in all versions up to and including 2.4.4 due to insufficient input sanitization and output escaping.
Authenticated attackers with contributor level access or higher can exploit this flaw to inject arbitrary web scripts into pages. These scripts will execute whenever any user accesses the injected page.
How can this vulnerability impact me? :
This vulnerability allows attackers with contributor level access or above to inject malicious scripts into web pages. When other users visit these pages, the injected scripts execute in their browsers.
- It can lead to theft of user credentials or session tokens.
- It can enable unauthorized actions on behalf of users.
- It can compromise the integrity and trustworthiness of the affected website.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers with contributor level access and above to inject arbitrary web scripts via stored cross-site scripting (XSS). This can lead to unauthorized access or manipulation of user data when users access the injected pages.
Such unauthorized script execution could potentially expose personal or sensitive information, which may impact compliance with data protection regulations like GDPR or HIPAA that require safeguarding user data against unauthorized access or disclosure.
However, the provided information does not explicitly detail the direct impact on compliance with these standards.