Search: xss.is

A reflected Cross-site Scripting (XSS) vulnerability exists in WP Swings Upsell Order Bump Offer for WooCommerce through version 3.1.6. This flaw allows improper neutralization of input during web page generation, potentially enabling attackers to execute arbitrary scripts in the context of the affected website.

A reflected Cross-site Scripting (XSS) vulnerability exists in OceanWP through version 4.2.7. This vulnerability involves improper neutralization of input during web page generation, which can allow an attacker to inject malicious scripts that execute in the context of a victim's browser.

A reflected Cross-site Scripting (XSS) vulnerability exists in PluginUs.Net TableOn posts-table-filterable component. This vulnerability affects versions up to and including 1.0.7. It allows improper neutralization of input during web page generation, potentially enabling attackers to execute arbitrary scripts in the context of the affected application.

The LiteSpeed Cache plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'comment' parameter affecting all versions up to and including 7.9.1. This flaw arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts. Exploitation requires the HTML Minify option to be enabled and a companion plugin that renders stored comment content in a raw-text context such as a JSON-LD script block on the same page.

The HT Mega Addons for Elementor WordPress plugin (up to version 3.2.7) contains a stored DOM-based cross-site scripting (XSS) vulnerability via the href attribute of anchor tags inside the .htmega-tab-nav parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts. Exploitation requires a co-installed plugin like wpDiscuz with its rich editor enabled, an HT Mega Tabs widget on the same page, and a victim clicking the injected link.

The Greenshift WordPress plugin (animation and page builder blocks) is vulnerable to stored DOM-based cross-site scripting (XSS) via the 'comment' parameter in all versions up to and including 13.2.1. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute when users access affected pages. Exploitation requires specific conditions involving administrator-published pages with certain block configurations that trigger the vulnerable script processing comment excerpts.

The Greenshift WordPress plugin, used for animation and page builder blocks, suffers from a Stored DOM-Based Cross-Site Scripting (XSS) vulnerability via the 'comment' parameter in all versions up to and including 13.2.1. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute when users view affected pages. Exploitation requires a specific page configuration involving an Advanced HTML Element block with Split Text animation wrapping a Latest Comments block displaying comment excerpts.

The Sequential Order Numbers for WooCommerce plugin for WordPress versions up to and including 3.6.5 is vulnerable to stored cross-site scripting (XSS) via 'condition' post meta array keys. This vulnerability arises from insufficient input sanitization and output escaping, allowing authenticated users with contributor-level access or higher to inject malicious scripts that execute when other users view the affected pages.

The RSS Aggregator by Feedzy WordPress plugin (up to version 5.2.12) is vulnerable to stored cross-site scripting (XSS) via the media:group/media:description XML element in imported feeds. This vulnerability allows unauthenticated attackers to inject malicious scripts that execute when a user views the affected page. Exploitation requires an administrator to configure a feed import pointing to a malicious feed URL and trigger the import through the plugin's standard workflow.

The Everest Forms WordPress plugin up to version 3.6.2 contains a reflected cross-site scripting (XSS) vulnerability via the 'evf_toast_type' parameter. This flaw allows unauthenticated attackers to inject arbitrary scripts that execute in a user's browser if the user is tricked into clicking a crafted link. Exploitation depends on the 'evf_toast' parameter decoding successfully via atob(), which is attacker-controlled.

The Extensions for Leaflet Map plugin for WordPress contains a stored DOM-based cross-site scripting (XSS) vulnerability in all versions up to and including 5.4. This vulnerability arises from insufficient input sanitization and output escaping of the 'feature.properties[<template-token>]' parameter. An unauthenticated attacker can inject malicious scripts that execute when users access affected pages. Exploitation requires prior configuration of a public map using specific shortcode combinations pointing to a GeoJSON source controlled by the attacker, which can be achieved through external data host compromise, subdomain takeover, or intentional pointing to attacker-hosted feeds.

The Media Library Assistant plugin for WordPress versions up to and including 3.42 is vulnerable to reflected cross-site scripting (XSS) via the 'search-string' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts. Exploitation requires a publicly accessible page with an [mla_gallery] shortcode configured with pagination output mode and an mla_link_href template reflecting a {+request:...+} token, plus enough attachments to trigger pagination. The CVSS score is 4.7, indicating medium severity.

The Mapster WP Maps plugin for WordPress versions up to and including 2.0.5 is vulnerable to stored cross-site scripting (XSS). The vulnerability arises because the REST route /wp-json/mapster-wp-maps/save-mapmaker lacks proper permission checks, allowing unauthenticated attackers to inject scripts. The plugin's sanitization only removes HTML tags but leaves quote characters intact, and the injected value is concatenated into an inline style attribute without proper escaping. This enables execution of arbitrary scripts when a user views an affected page.

The LiteSpeed Cache plugin for WordPress versions up to and including 7.9.1 contains a stored cross-site scripting (XSS) vulnerability via the 'bbp_reply_content' parameter. This flaw arises from insufficient input sanitization and output escaping, allowing authenticated users with subscriber-level access or higher to inject malicious scripts. Exploitation requires that an administrator has enabled Viewport Images (VPI) and configured a VPI filename that attackers can embed in user-generated content such as bbPress topics. The vulnerability has a CVSS score of 6.4, indicating a medium severity level.

Stored Cross-Site Scripting (XSS) vulnerability in SABBATIC application that allows an attacker to store JavaScript code so that when a user views the page, code can be executed in the victim's browser. The list of assigned parameters and identifiers is as follows:  parameter 'observaciones' in  /mis-gastos  endpoint.

Stored Cross-Site Scripting (XSS) vulnerability in SABBATIC application that allows an attacker to store JavaScript code so that when a user views the page, code can be executed in the victim's browser. The list of assigned parameters and identifiers is as follows:   parameter 'companyName' in  /empresa  endpoint;

Stored Cross-Site Scripting (XSS) vulnerability in SABBATIC application that allows an attacker to store JavaScript code so that when a user views the page, code can be executed in the victim's browser. The list of assigned parameters and identifiers is as follows:  parameters 'titulo_es' and 'add_etiquetas%5B%5D' in '/categorías' endpoint;

Stored Cross-Site Scripting (XSS) vulnerability in SABBATIC application that allows an attacker to store JavaScript code so that when a user views the page, code can be executed in the victim's browser. The list of assigned parameters and identifiers is as follows:   parameter 'nombre' in '/usuario' endpoint;