← WordPress Vulnerabilities
WordPress security by component

Email Encoder – Protect Email Addresses and Phone Numbers

Email Encoder – Protect Email Addresses and Phone Numbers is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Feb 29, 2024; the highest CVE/CNA score is 6.5.

Plugin slug: email-encoder-bundle

CVE-2024-1282: Email Encoder – Protect Email Addresses and Phone Numbers: Cross-site scripting

Email Encoder – Protect Email Addresses and Phone Numbers is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

PublishedFeb 29, 2024
Safe version guidanceSee mitigation notes
Safe version
Feb 29, 2024 CVE-2024-1282
Email Encoder – Protect Email Addresses and Phone Numbers: Cross-site scripting
Email Encoder – Protect Email Addresses and Phone Numbers is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4
Jan 11, 2024 CVE-2023-7070
Email Encoder – Protect Email Addresses and Phone Numbers: Cross-site scripting
Email Encoder – Protect Email Addresses and Phone Numbers is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4
Nov 22, 2023 CVE-2023-47821
Email Encoder Bundle: Cross-site scripting
Email Encoder Bundle is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.5
NVD5.4
Aug 30, 2023 CVE-2023-4599
Email Encoder: Cross-site scripting
Email Encoder is affected by cross-site scripting. Exploitation requires an authenticated WordPress account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4