Plugin Security Certification (PSC-2026-64649): “YayMail” – Version 4.4.0

Plugin Security Certification (PSC-2026-64649): “YayMail” – Version 4.4.0

WooCommerce email customization plugins operate on a sensitive boundary between order data, customer communication, template rendering, and admin-side content editing. These plugins often process customer names, billing and shipping details, order metadata, payment-related labels, coupons, custom fields, and transactional email content. A weakness in this class of plugin can lead to stored XSS in email templates or admin previews, unauthorized modification of transactional communications, data leakage through shortcodes or preview logic, or abuse of import/export and template management functionality. YayMail – WooCommerce Email Customizer version 4.4.0 has successfully completed the CleanTalk Plugin Security Certification process and received PSC-2026-64649, confirming that the plugin was reviewed from a secure code perspective with attention to the most common exploitation paths for WooCommerce email template, shortcode, preview, and customization plugins.

Plugin Security Certification (PSC-2026-64648): “Direct Checkout for WooCommerce” – Version 3.6.6

Plugin Security Certification (PSC-2026-64648): “Direct Checkout for WooCommerce” – Version 3.6.6

Checkout optimization plugins operate directly on one of the most commercially sensitive workflows in WordPress: the path between product selection and order completion. Because these plugins modify cart behavior, checkout redirects, AJAX add-to-cart flows, and checkout field visibility, weaknesses in this class of software can affect both security and business integrity. Improper handling of redirects, checkout configuration, request validation, or administrative settings may lead to unauthorized behavior, data exposure, stored XSS, CSRF, or broken transaction flows. Direct Checkout for WooCommerce version 3.6.6 has successfully completed the CleanTalk Plugin Security Certification process and received PSC-2026-64648, confirming that the plugin was reviewed from a secure code perspective with attention to the most common exploitation paths for WooCommerce checkout, cart, redirect, and purchase-flow optimization plugins.

Plugin Security Certification (PSC-2026-64647): “MailPoet” – Version 5.23.2

Plugin Security Certification (PSC-2026-64647): “MailPoet” – Version 5.23.2

Email marketing plugins operate across several high-risk boundaries in WordPress because they combine subscriber data handling, admin-side campaign management, form collection and segmentation, scheduled and automated sending logic, and in some deployments external delivery infrastructure. Weaknesses in this class of plugin can lead to stored XSS in administrative interfaces, unauthorized access to subscriber information, misuse of automation workflows, or abuse of privileged settings that affect site communications and user trust. MailPoet version 5.23.2 has successfully completed the CleanTalk Plugin Security Certification process and received PSC-2026-64647, confirming that the plugin was reviewed from a secure code perspective with attention to the most common exploitation paths for newsletter, subscriber management, email automation, and WooCommerce email plugins.

Plugin Security Certification (PSC-2026-64646): “Backup Migration” – Version 2.1.5.1

Plugin Security Certification (PSC-2026-64646): “Backup Migration” – Version 2.1.5.1

Backup and migration plugins sit on one of the most sensitive trust boundaries in WordPress because they routinely interact with site files, database contents, archive generation and extraction, and sometimes remote storage or cross-site transfer flows. A weakness in this class of plugin can quickly translate into unauthorized data exposure, integrity loss during restore operations, or abuse of privileged backup management features. Backup Migration version 2.1.5.1 has successfully completed the CleanTalk Plugin Security Certification process and received PSC-2026-64646, confirming that the plugin was reviewed from a secure code perspective with attention to the most common exploitation paths for backup, restore, migration, and staging plugins.

Plugin Security Certification (PSC-2026-64645): “Forminator Forms – Contact Form, Payment Form & Custom Form Builder” – Version 8.6.0

Plugin Security Certification (PSC-2026-64645): “Forminator Forms – Contact Form, Payment Form & Custom Form Builder” – Version 8.6.0

Forminator Forms – Contact Form, Payment Form & Custom Form Builder (v1.53.1) is a multifunctional WordPress plugin that enables the creation of forms, polls, quizzes, payment forms, and lead-generation tools through a drag-and-drop interface. It integrates with payment gateways, CRMs, and third-party services, making it a high-impact component in the application security surface.

Built for websites running on WordPress, Forminator handles sensitive user data, payments, file uploads, and AJAX interactions — making security a critical requirement.

The plugin functionality includes payments (Stripe, PayPal), quizzes, surveys, integrations, and GDPR-ready data handling

CVE-2026-4659 – Unlimited Elements For Elementor – LFI (Local File Inclusion) Author+ – POC

CVE-2026-4659 – Unlimited Elements For Elementor – LFI (Local File Inclusion) Author+ – POC

CVE-2026-4659 affects Unlimited Elements for Elementor and it is an authenticated Local File Inclusion vulnerability that allows an Author level user to read arbitrary local files from the WordPress host. The bug is especially practical because it uses a normal looking Elementor widget feature. A repeater can load JSON or CSV data from a URL, which is a common pattern for dynamic widgets. The vulnerability appears when the plugin treats certain URLs as local filesystem paths and then reads them. When debug output is enabled, the plugin returns the raw file content in the response, which turns a file read primitive into direct exfiltration through the page preview. With an install base around 300k plus and common editorial setups where Authors can edit pages, this is a realistic path from a low privilege content role to server level secret disclosure.

Plugin Security Certification (PSC-2026-64644): “Element Pack” – Version 8.6.0

Plugin Security Certification (PSC-2026-64644): “Element Pack” – Version 8.6.0

Elementor addon suites are security-relevant because they add a large amount of front-end rendering and stored widget configuration into WordPress. These plugins frequently process user-controlled strings (titles, labels, URLs, templates) and expose admin-side builders and settings that, if not defended correctly, can become paths to stored XSS, CSRF-driven configuration changes, privilege boundary issues, or information disclosure via misconfigured endpoints. Element Pack – Widgets, Templates & Addons for Elementor version 8.6.0 has successfully completed the CleanTalk Plugin Security Certification process and received PSC-2026-64644, confirming that the plugin was reviewed from a secure code perspective with attention to the most common exploitation paths for Elementor widget and template libraries.

CVE-2025-15380 – NotificationX – Unauthenticated DOM-Based Cross-Site Scripting via nx-preview – POC

CVE-2025-15380 – NotificationX – Unauthenticated DOM-Based Cross-Site Scripting via nx-preview – POC

CVE-2025-15380 affects NotificationX and it is an unauthenticated DOM based cross site scripting vulnerability that can execute JavaScript in a victim browser on public pages. The attack does not require a WordPress account and it does not require any special permissions. It abuses a front end preview mechanism where the plugin accepts attacker supplied configuration, decodes it, and renders it directly into the DOM. This matters because NotificationX is installed specifically to show attention grabbing UI elements like notification bars and press bars. If the preview path can be triggered by anyone, then any attacker can weaponize it to run script on the site origin and steal session data, run actions in the background, or plant further attacks through social engineering. Even a single successful execution can be enough to compromise administrators if they browse the front end while logged in.