The Complianz GDPR/CCPA Cookie Consent Banner plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Elementor Cookie Blocker Regex in all versions up to, and including, 7.5.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 an administrator to approve the attacker's comment, and the site must have both the Elementor plugin installed and Complianz configured with the Twitter or Facebook cookie/script blocker enabled.
Open Access Management (OpenAM) is an access management solution. From 13.0.0 until 16.1.2, the OAuth2 authorize endpoint's display=wap consent page reflects request-derived values through ConsentRequiredResource and wap/authorize.ftl without HTML escaping. An attacker can induce a user with an active OpenAM session to follow a crafted authorization link and execute JavaScript in the OpenAM origin, enabling session or cookie theft, CSRF-token disclosure, and actions with the victim's privileges. At least one registered OAuth2 client is required, but the attacker does not need to control that client. This issue is fixed in version 16.1.2.
The Cookie Banner for GDPR / CCPA – WPLP Cookie Consent plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpl_user_preference' parameter in all versions up to, and including, 4.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. The consent-logging AJAX endpoint is registered for unauthenticated users and its required nonce (wpl_consent_logging_nonce) is publicly emitted via wp_localize_script on the frontend, meaning any unauthenticated site visitor can plant a payload without any prior authentication or privileged access.
The npm package easypanel-deploy version 1.0.0 contains malicious code that executes during the preinstall lifecycle script. This code collects host identifiers such as hostname, username, current directory, and CI environment variables, encodes them, and sends them to an attacker-controlled domain without user consent. The package behaves like a dependency-confusion beacon, exfiltrating reconnaissance data to a hardcoded third-party endpoint. Although labeled as a 'benign canary' in the source, the behavior is consistent with malicious activity.
In buildMiniResolver of IntentForwarderActivity.java, there is a possible consent bypass due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
In handleBondStateChanged of AdapterService.java, there is a possible way to skip pairing due to a logic error in the code. This could lead to remote escalation of privilege without user consent with no additional execution privileges needed. User interaction is not needed for exploitation.
The iubenda All-in-one Compliance for GDPR / CCPA Cookie Consent + more WordPress plugin up to version 3.13.4 is vulnerable to stored cross-site scripting (XSS) via comment content. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute in the context of any user visiting the affected page, including administrators. The exploit leverages KSES-allowed markup mutations to transform inert tags into executable elements.
The Social Chat – Click To Chat App Button plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'consent_message' JSON Attribute in .qlwapp data-box in all versions up to, and including, 8.6.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit requires no user interaction beyond page load, as setting auto_open and consent_enabled to 'yes' in the injected data-box JSON causes the consent box — and the embedded script — to execute immediately on page load.
The iubenda All-in-one Compliance for GDPR / CCPA Cookie Consent + more WordPress plugin is vulnerable to a stored Cross-Site Scripting (XSS) flaw in all versions up to and including 3.13.4. This vulnerability arises from insufficient input sanitization and output escaping in the Comment Content via AdSense Regex Rewrite feature. It only occurs when the 'Secondary' parser engine (parser_engine=default) is active and does not affect the default 'new' DOM-based parser engine. An unauthenticated attacker can inject arbitrary scripts that execute when users access the affected pages.
The pymaas package on PyPI, version 99.99.0, contains malicious code that executes upon import. It collects all environment variables and the hostname, serializes this data as JSON, and sends it to a hardcoded external URL without user consent. This behavior is indicative of a dependency confusion attack designed to exfiltrate sensitive credentials such as CI tokens, cloud keys, and passwords from the environment.
A vulnerability in Hugging Face Transformers (versions 4.57.0 to 5.16.1) allows remote Python files to be written to local disk without user consent when using GenerativePreTrainedModel.load_custom_generate(). The function fetches and caches a remote module file before performing the required trust_remote_code consent check, inverting the security model enforced by other code-loading paths (such as AutoConfig, AutoModel, and AutoTokenizer). As a result, attacker‑controlled Python code from custom_generate/generate.py is copied into the user’s ~/.cache/huggingface/modules directory even if the user declines the trust prompt. Although execution is correctly gated, the file write is not reversible and can persist across sessions. This can lead to persistent, unauthorized files on disk and stale cache collisions where cached attacker code may later be executed during trusted model loads. The issue stems from an unconditional file write in dynamic_module_utils.py prior to any trust verification.
The WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode plugin for WordPress is vulnerable to arbitrary file upload due to missing file type validation in the saas_upload_logo() function combined with an authorization bypass on the WPLP connector REST endpoints in all versions up to, and including, 4.4.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
The npm package 'cre-setup' version 1.0.0 contains malicious code that collects user and system information and sends it to a hardcoded external endpoint without user consent. This behavior is indicative of reconnaissance activity typical in dependency confusion attacks. Installation or execution of this package may lead to full system compromise, requiring immediate secret and key rotation and removal of the package.
The npm package 'verify-contract-viem' version 1.0.0 contains malicious code that executes system commands and collects host information, sending it to an attacker-controlled Cloudflare Workers URL. This behavior occurs when the CLI is invoked, transmitting sensitive host identifiers without user consent or disclosure. The package is considered fully compromising to any system where it is installed or run.
The npm package 'generate-schema-ethers' version 1.0.0 is identified as malicious. Upon execution, it runs the 'whoami' command and sends system information including OS username, hostname, platform, and package name to a hardcoded external URL without user consent. This behavior is consistent with reconnaissance activity typical of typosquatting or dependency confusion attacks. The package is considered fully compromising any system where it is installed or run.
The npm package 'techportal' version 4.0.10 contains malicious code that executes automatically during installation via a preinstall hook. This code collects host identity information including hostname, username, and current working directory, encodes it, and sends it to a hardcoded attacker-controlled IP address via HTTP headers. If the HTTP request fails, the data is exfiltrated using DNS queries to attacker-controlled domains, bypassing typical HTTP egress controls. There is no user consent or configuration option to disable this behavior, and the package self-labels the data exfiltration as a bug bounty or dual-use tool, which does not mitigate the risk.
Improper neutralization of input used for LLM prompting in the python_repl tool in Amazon Strands Agents Tools before 0.8.5 might allow remote actors to execute arbitrary Python code on the agent's host by bypassing the human consent gate, via a crafted prompt that forwards non_interactive_mode as a keyword argument through the batch tool. To remediate this issue, users should upgrade to version 0.8.5 or later.
The npm package amundi-compare version 999.9.12 contains malicious code that executes automatically during installation via a preinstall hook. This code collects extensive system and network information, including hostname, user details, IP addresses, and metadata from the parent project. The collected data is exfiltrated through multiple channels, including HTTP, HTTPS, and a covert DNS channel designed to evade network egress filters. The package falsely claims to be authorized security research, but it transmits sensitive information without user consent.
The npm package @sdgdfgdfhhhfd/chainvista contains malicious code that exfiltrates private keys and other sensitive cryptographic material from users' wallets to a hardcoded backend. It also allows remote operators to execute signed transactions across multiple EVM chains without user consent, effectively giving persistent control over victim wallets. Additionally, it exposes private keys to any calling dapp origin without user confirmation, creating a second exfiltration vector. Installation of this package compromises the host system, requiring immediate secret rotation and package removal.
The npm package stillm4ddpocs-rtest-bravo versions 999.9.9 and 999.9.10 contains malicious code that executes automatically during installation. This code collects sensitive environment information including hostname, username, home directory, local and public IP addresses, and details about the consuming project. The collected data is exfiltrated to a third-party server via HTTPS POST and also covertly via DNS queries, bypassing some network filters. The package claims to be a dependency-confusion research proof-of-concept, but it transmits identifying information without user consent.