| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| PMB 7.3.1 before 7.3.15 and 7.4.x before 7.4.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject script through unescaped POST parameter names. Attackers can send crafted parameter names to opac_css/index.php extended_search, which empr.inc.php and languages.inc.php reflect into hidden form inputs to execute JavaScript. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23. |
| The SendPress Newsletters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sp_firstname' parameter in all versions up to, and including, 1.26.1.20 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The public subscriber-management route uses an unsigned, forgeable base64-encoded JSON token, allowing an unauthenticated attacker to impersonate any subscriber and obtain a valid nonce — bypassing the POST handler's only access control check. |
| Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, the OAuth 2.0 and OpenID Connect authorization endpoint does not sufficiently encode user-supplied parameters before FormPostResponse.ftl and checkSession.ftl render them into HTML for the form_post response mode. An unauthenticated attacker can induce a user to open a crafted authorization request and execute script in the OpenAM origin. This issue is fixed in version 16.1.1. |
| Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, certain federation endpoints in a non-default clustered configuration inconsistently encode user-supplied parameters rendered into HTML in the SAML2 cluster cookie-hash redirect path. An unauthenticated attacker can induce a user to follow a crafted request and execute script in the OpenAM origin. This issue is fixed in version 16.1.1. |
| The Geo Mashup plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'author (comment form) / display_name (profile form)' parameter in all versions up to, and including, 1.13.23 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The comment-author path requires the crafted comment to be approved before the payload is served to visitors; the subscriber-level path requires the plugin's user-location mapping feature to be enabled. |
| Hardcoded credentials in the executable file. These can be extracted using the “Strings.exe” tool and could allow an attacker unauthorized access to the database and SMTP server. winCRM.exe |
| The Kirki – Freeform Page Builder, Website Builder & Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (title attribute of <abbr>)' parameter in all versions up to, and including, 6.4.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires an administrator to run the Kirki Convert (migration) workflow on a page containing the attacker's approved comment, as the browser-side DOM parser decodes the kses-allowed abbr title attribute value into a raw XSS payload that is then persisted without sanitization and later rendered unescaped. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| SLiMS Senayan Library Management System 9.4.0 before 9.4.2 contains a reflected cross-site scripting vulnerability in the destination parameter of /index.php?p=member, which is echoed unmodified into the login form action attribute. Unauthenticated attackers can craft a malicious destination value to inject script and hijack PHPSESSID sessions of victims who access the link. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23. |
| phpLDAPadmin 1.1.0 before 1.2.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the dn parameter of cmd.php?cmd=template_engine. Attackers can supply an unparseable dn value that pretty_print_dn returns unescaped in the 'No such entry' error, executing JavaScript in victims' browsers. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23. |
| Retool versions 3.253.0 before 3.253.19, 3.254.0 before 3.284.12, and 3.285.0 before 3.300.4 contain a DOM-based cross-site scripting vulnerability in the custom-component-collections.html postMessage handler that imports received code without origin validation. Unauthenticated attackers can send crafted postMessage events that load attacker-controlled code via data:text/javascript URIs to execute arbitrary JavaScript in the victim's context. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-04-22. |
| The Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'mjsupport_message' parameter in all versions up to, and including, 1.2.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that a staff member or administrator opens the affected ticket and clicks the attacker-planted link on the ticket-detail screen, as the VenoBox payload is triggered on click rather than on page load. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.1.19 via comment content rendered on AMP post pages. The plugin registers an output-buffer callback ampforwp_the_content_filter_full() on the 'wp' action (priority 999) that applies a set of tag-agnostic and quote-agnostic regular expressions — notably /onclick=[^>]*/ — to the entire AMP page output after approved comments have already been echoed into it; these regexes do not understand HTML tag or attribute-value boundaries, so a kses-legal comment that places strings like 'onclick="' inside a title attribute value can trigger deletion of the title's closing quote, causing the browser to re-parse what was previously textual content inside the attribute value as live HTML attributes. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, after an administrator has approved the comment. |
| A stored cross site scripting attack when viewing email aliases in postfixadmin 4.0 before 4.0.7, and postfixadmin 3.3 before 3.3.17 could be caused by signed in admins able to inject aliases. |
| A use of default credentials vulnerability could allow an attacker to gain unauthorised root-level access to the product via SSH. |
| SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability in genAVValueHTML() that allows attackers who can store Attribute View asset values to inject script through an unescaped image src attribute. Attackers can store an image URL containing a double quote and onerror handler that executes OS commands via Node.js in the desktop app when victims open the bound note or row attribute panel. |
| SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to execute script by storing malicious Attribute View column names rendered unescaped in col.ts. Attackers can inject HTML via addAttributeViewKey, .sy.zip import, or sync, and when a victim adds or duplicates the column, insertAdjacentHTML runs JavaScript with Node.js privileges for desktop code execution. |
| SiYuan from 3.3.0 before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to inject HTML via unescaped checkbox column names in Gallery and Kanban AttributeView renderers. Attackers can share a crafted .sy.zip document whose rendering in the Electron desktop client with nodeIntegration enabled executes Node.js and host OS commands. |
| SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability, an incomplete fix for CVE-2026-44670, because renderAVAttribute() inserts an Attribute View name unescaped into the database row attribute panel header. Attackers who can persist the name, such as via the setAttrViewName action, can inject an onerror handler that runs OS commands through Node.js when a desktop user opens the panel. |
| The WEB-Translation – eTranslation Multilingual plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.0.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit requires that at least one secondary language is configured in the plugin and that comments are open on the target post; because the stored payload contains no literal HTML brackets at save-time, WordPress core KSES filtering does not remove it, and the malicious script is only materialized when a visitor loads the post under a secondary-language URL slug. |
| The Jeg Kit for Elementor – Powerful Addons for Elementor, Widgets & Templates for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'description' parameter in all versions up to, and including, 3.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful execution requires a published page containing both a Post Author widget in user_bio mode (rendering the attacker's biography) and any legitimate jkit_client_logo widget, so that client-logo.js is enqueued and the loadCarousel handler fires against the forged widget markup from the bio field. |