← Back

Wp Webhooks

wp-webhooks

3 CVEs • 1 product

Products (1)

Click to collapse
Toggle
Email Encoder
email_encoder

CVEs (3)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Wp Webhooks
1Email Encoder
Jun 17, 2026
Jul 29, 2024
N/A· v4
5.4 MEDIUM· v3
N/A· v2
The Email Encoder WordPress plugin before 2.2.2 does not escape the WP_Email_Encoder_Bundle_options[protection_text] parameter before outputting it back in an attribute in an admin page, leading to a Stored Cross-Site S...Show more
The Email Encoder WordPress plugin before 2.2.2 does not escape the WP_Email_Encoder_Bundle_options[protection_text] parameter before outputting it back in an attribute in an admin page, leading to a Stored Cross-Site ScriptingShow less
1Wp Webhooks
1Email Encoder
Jun 17, 2026
Aug 30, 2023
N/A· v4
5.4 MEDIUM· v3
N/A· v2
The Email Encoder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'eeb_mailto' shortcode in versions up to, and including, 2.1.8 due to insufficient input sanitization and output escaping on use...Show more
The Email Encoder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'eeb_mailto' shortcode in versions up to, and including, 2.1.8 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. A partial patch was issued in version 2.1.8. The vulnerability was fully patched in 2.1.9.Show less
1Wp Webhooks
1Email Encoder
Jun 17, 2026
Sep 6, 2021
N/A· v4
6.1 MEDIUM· v3
4.3 MEDIUM· v2
The Email Encoder – Protect Email Addresses WordPress plugin before 2.1.2 has an endpoint that requires no authentication and will render a user supplied value in the HTML response without escaping or sanitizing the data...Show more
The Email Encoder – Protect Email Addresses WordPress plugin before 2.1.2 has an endpoint that requires no authentication and will render a user supplied value in the HTML response without escaping or sanitizing the data.Show less