EUVD-2023-51795

Malicious code in bioql PyPI...

CVE-2024-6715

The Ditty WordPress plugin before 3.1.46 re-introduced a previously fixed security issue https://wpscan.com/vulnerability/80a9eb3a-2cb1-4844-9004-ba2554b2d46c/ in v3.1.39...

CVE-2024-6715

CVE-2024-6715 affects the Ditty WordPress plugin prior to 3.1.46, specifically versions 3.1.39–3.1.45, where an Author+ stored cross-site scripting (XSS) vulnerability was reintroduced and authenticated users could trigger XSS via the author field. The issue was publicly documented in multiple so...

CVE-2023-47697 WordPress WP Event Manager Plugin <= 3.1.39 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting XSS vulnerability in WP Event Manager WP Event Manager – Events Calendar, Registrations, Sell Tickets with WooCommerce plugin = 3.1.39 versions...

PT-2023-30573 · WordPress · Wp Event Manager

Name of the Vulnerable Software and Affected Versions: WP Event Manager plugin versions prior to 3.1.39 Description: The issue is related to an Unauth. Reflected Cross-Site Scripting XSS vulnerability. This type of vulnerability allows an attacker to inject malicious scripts into a website,...

Ubuntu 18.04 LTS : Smarty vulnerabilities (USN-5348-1)

The remote Ubuntu 18.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-5348-1 advisory. David Gnedt and Thomas Konrad discovered that Smarty was incorrectly sanitizing the paths present in the templates. An attacker could possibly use this u...

Smarty: Multiple vulnerabilities

Background Smarty is a template engine for PHP. Description Multiple vulnerabilities have been discovered in Smarty template engine. Please review the CVE identifiers referenced below for details. Impact Please review the referenced CVE identifiers for details. Workaround There is no known...

PT-2021-6792 · Smarty +2 · Smarty +2

Name of the Vulnerable Software and Affected Versions: Smarty versions prior to 3.1.39 Description: The issue allows a Sandbox Escape because the $smarty.template object can be accessed in sandbox mode. This is due to insufficient access control when handling the $smarty.template object...