Swift Performance Lite WordPress plugin versions up to 2.3.7.5 contain a stored cross-site scripting (XSS) vulnerability. This flaw arises from insufficient input sanitization and output escaping of an attacker-controlled parameter, allowing unauthenticated attackers to inject malicious scripts. Exploitation requires that an administrator has enabled at least one Cacheable AJAX Action via the plugin's AJAX Cache feature. Attackers can verify this condition by detecting a specific response header. The vulnerability has a high severity rating with a CVSS score of 7.2.
ProfilePress WordPress plugin versions up to 4.18.0 have a vulnerability allowing unauthenticated attackers to extract full email addresses and enumerate usermeta keys via crafted parameters. This occurs because the plugin's directory page exposes searchable email fields without access controls.
The ProfilePress WordPress plugin (versions up to and including 4.18.0) contains a stored cross-site scripting (XSS) vulnerability via the 'reg_bio' parameter. This flaw allows unauthenticated attackers to inject arbitrary scripts through a raw POST request, even when the registration form does not display a biography field. The vulnerability arises from insufficient input sanitization and output escaping, enabling script execution when users access the affected pages.
The WP Custom Admin Interface plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'first_name' parameter affecting all versions up to and including 7.43. This flaw allows authenticated users with subscriber-level access or higher to inject malicious scripts that execute when other users view the affected pages.
AutomatorWP – No-Code Workflow Automation, Integration & Webhooks Plugin for WordPress versions up to 6.0.9 is vulnerable to a stored cross-site scripting (XSS) flaw. The vulnerability arises from insufficient input sanitization and output escaping of the 'your-message' parameter used in form_field tags. An unauthenticated attacker can inject malicious scripts that execute when a user views an affected email log entry, provided an administrator has configured a specific public automation involving guest form submissions and email actions.
CVE-2026-128361 is an improper input validation vulnerability in the Phoenix framework's Presence module. It allows an attacker who can join a channel to cause a denial of service by submitting a non-string presence key, such as a JSON object. This leads to crashes in processes listing presences and can ultimately take down the application supervisor due to repeated failures. The issue affects multiple versions of Phoenix prior to fixed releases.
CVE-2026-129344 is an uncaught exception vulnerability in the Phoenix framework's channel broadcasting mechanism. It allows an unauthenticated attacker to cause denial of service by exploiting client-selected legacy serializers on binary channel broadcasts. When a client connects without a version parameter or with version 1.0.0, broadcasts containing binary payloads fail, causing the broadcasting process to crash and disrupting message delivery to other subscribers. This issue affects multiple Phoenix versions prior to fixed releases.
MaysWind AriaNg-Native up to version 1.3.14 contains a vulnerability in the IPC Handler component, specifically in the shell.openPath function. This flaw involves improper input validation of the argument 'dir', which can be exploited remotely. The issue is resolved by upgrading to version 1.3.15.
The Product Import Export for WooCommerce – CSV Product Importer & Exporter plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in all versions up to and including 2.6.9. This vulnerability arises from insufficient input sanitization and output escaping of the 'author' field during CSV import. Exploitation requires an attacker to submit a crafted review, which must then be approved by an administrator and re-imported via the plugin's default column mapping. The vulnerability cannot be triggered without administrative actions and specific database table prefix conditions.
The BlockStrap Page Builder – Bootstrap Blocks plugin for WordPress up to version 0.1.65 is vulnerable to stored cross-site scripting (XSS) via the 'comment' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute when users view the affected pages. Exploitation requires that the attacker previously had at least one comment approved with a specific name and email, enabling subsequent comments to bypass moderation under WordPress's default policy. Additionally, exploitation is limited to sites using a block theme, which is the WordPress default.
The MailerLite – Signup forms (official) plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability via the 'form_id' parameter in all versions up to and including 1.7.27. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts. Exploitation requires an administrator to approve a comment containing a malicious shortcode, after which any page displaying the Latest Comments block with excerpts enabled will execute the injected script for all visitors.
The NextGEN Gallery plugin for WordPress, versions up to and including 4.5.6, is vulnerable to stored cross-site scripting (XSS) via the 'comment' parameter. This vulnerability arises from insufficient input sanitization and output escaping. Exploitation requires the site administrator to have enabled the Thickbox lightbox effect with the 'Try to apply to all images' setting and depends on an administrator approving the attacker's initial comment, which then allows subsequent comments from that author to be auto-approved.
The SiteOrigin CSS plugin for WordPress up to version 1.6.9 is vulnerable to stored DOM-based cross-site scripting (XSS) via the 'class' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing attackers with contributor-level access or higher to inject malicious scripts into posts. These scripts execute when users with the edit_theme_options capability interact with the Visual Inspector on the affected post. Unauthenticated exploitation requires additional third-party plugin configurations and moderator approval, which are not present in default installations.
The Contact Form to Any API plugin for WordPress up to version 3.0.7 is vulnerable to stored cross-site scripting (XSS) via the 'your-message' parameter. This vulnerability allows unauthenticated attackers to inject malicious scripts that execute when users access affected pages. The injection occurs through Contact Form 7's public REST feedback endpoint, which does not require authentication.
The Organize Media Folder plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the handling of the EXIF.DateTimeOriginal parameter. This vulnerability affects all versions up to and including 2.00. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view the affected pages. Exploitation at subscriber level requires the presence and configuration of bbPress and gd-bbpress-attachments plugins to allow frontend attachment uploads. Without this configuration, an attacker needs author-level access or higher to exploit the vulnerability.
The WPBot – AI ChatBot for WordPress & Growth Suite plugin is vulnerable to a Stored Cross-Site Scripting (XSS) flaw via the 'text' parameter in all versions up to and including 9.1. This vulnerability allows unauthenticated attackers to inject malicious scripts that execute when an administrator views the Chat Sessions screen. The issue arises from insufficient input sanitization and output escaping, specifically involving the plugin's use of Bootstrap 3.3.7 affix data-API passing attacker-controlled data to jQuery as HTML.
The Forminator Forms plugin for WordPress up to version 1.58.4 is vulnerable to stored cross-site scripting (XSS) via the 'textarea-N' parameter used for rich-text draft values saved as Save-and-Continue drafts. This vulnerability allows unauthenticated attackers to inject malicious scripts that execute when any user, including administrators, resumes the draft or accesses the draft link. The exploit requires the targeted form to have a Rich-Text Textarea field with Save-and-Continue enabled and public submission permissions.
The Shortcodes Ultimate WordPress plugin up to version 7.9.1 contains a Local File Inclusion (LFI) vulnerability. This arises from unsafe handling of the Host header in URL construction and subsequent shortcode processing, allowing unauthenticated attackers to include arbitrary PHP files from the active theme's root directory. Additionally, if the 'Unsafe features' option is enabled, attackers can read arbitrary post meta data on any front-end page rendering the vulnerable shortcode.
The EZ SQL Reports Shortcode Widget and DB Backup plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in all versions up to and including 5.26.45. This vulnerability arises from insufficient input sanitization and output escaping of the User-Agent header, which is stored in the comment_agent field. An unauthenticated attacker can inject malicious scripts that execute when a user accesses a page containing the injected report. Exploitation requires that an administrator saves a report with an SQL query selecting attacker-controlled data such as comment_agent and that the attacker knows the report's slug, which is easily obtained if the report is published publicly via the [SQLREPORT] shortcode.
The Admin Columns plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'url' parameter affecting all versions up to and including 7.1.8. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts. Exploitation requires that an administrator has added the Author URL column to the Comments screen and that the site accepts unauthenticated comments, which are default settings.