Nezha versions from 1.8.0 up to but not including 2.3.13 contain a race condition due to a lock-order inversion in the UpdateGroup and DeleteGroup functions. This flaw allows authenticated non-admin users to cause a deadlock in the alerting subsystem by concurrently invoking notification-group and batch-delete endpoints with oversized ID lists. The deadlock can permanently disrupt alert delivery until the system is restarted.
CVE-2026-71892 is a vulnerability in Bouncy Castle for Java before version 1.86 and certain FIPS versions where the key-size validation for CMS key-transport recipients using RFC 9709 content-encryption key derivation (id-alg-cek-hkdf-sha256) was bypassed. The validation logic incorrectly compared incompatible data types, causing the key size check to be skipped entirely for these messages. This allowed acceptance of keys with mismatched sizes despite validation being enabled. The issue affects BC-JAVA versions >=1.78 <1.86 and FIPS versions >=2.0.7 <2.0.13 and >=2.1.0 <2.1.13. The flaw is fixed in versions 1.86, 2.0.13, and 2.1.13.
The WPZOOM Connect: AI Chat, Click to Chat, Social Icons & Share Buttons plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.7.3 via the 'x-yamidoo-signature (attacker-obtained via inline_js identify payload)' parameter. This makes it possible for unauthenticated attackers to extract the full customer card — including name, WordPress user ID, order history, order totals, purchased products, payment method labels, and EDD Software Licensing license keys with status and activation counts — for any arbitrary victim email address on the site. Exploitation requires the attacker to register a WooCommerce customer or subscriber-level account with a crafted email address whose local part encodes the target timestamp and victim email, allowing the signature printed into the page HTML by inline_js() to pass verify_request() for an arbitrary victim; both the share_customer_data and identify_logged_in settings are enabled by default, so no non-default configuration is required.
The Photo Reviews for WooCommerce plugin for WordPress is vulnerable to Arbitrary Content Deletion in versions up to, and including, 1.2.30. This is due to the plugin storing attacker-controlled post IDs from the wcpr_image_upload_id parameter of a public review submission into the review's reviews-images comment meta without verifying that the IDs correspond to attachments owned by the submitter, combined with the delete_reviews_image() handler unconditionally calling wp_delete_post( $id, true ) on every stored ID when the review is deleted. This makes it possible for unauthenticated attackers to permanently delete arbitrary posts, pages, products, or media attachments on the site whenever an administrator subsequently deletes the attacker's review (or when WordPress's built-in wp_scheduled_delete cron empties the comment trash after 30 days).
The GeoDirectory plugin for WordPress is vulnerable to SQL Injection via the stored latitude/longitude coordinates of a listing in versions up to, and including, 2.8.186. This is due to insufficient escaping and the absence of numeric validation on coordinate values when a listing is saved, combined with the direct string interpolation of those values into a distance sub-expression in geodir_gps_query_part() that is later executed by the public wp_ajax_nopriv_geodir_widget_listings handler when a caller supplies set_post=<pending-listing-id> and sort_by=distance_asc. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
The Helpdesk Support Ticket System for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.1.6 via the 'id' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary ticket responses belonging to other users by supplying any stsw_responses row ID to the deletion handler after obtaining the nonce from the admin footer.
The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to Privilege Escalation via Contact Identity Rebinding in all versions up to, and including, 4.9 The vulnerability exists because the `create_contact` function in the v3 REST endpoint (`POST /gh/v3/contacts`) is gated solely by the `add_contacts` capability and forwards the full request payload — including the security-bearing `user_id` column — into the upsert path of `Contacts_DB::add()`, which bypasses the ownership guard that `Contacts_DB::update()` enforces, allowing an attacker to rebind any existing contact record to an arbitrary WordPress user ID. This makes it possible for authenticated attackers with Sales Representative-level access and above to upsert their own contact row to point to an Administrator's user ID, then invoke the v4 email-test endpoint (`POST /gh/v4/emails/test`) — also accessible to the Sales Representative role via the `send_emails` capability — to generate an `{auto_login_url}` one-time permissions key bound to the rebound contact, and consume that link to call `wp_set_auth_cookie()` and gain a fully authenticated session as the WordPress Administrator.
A stack buffer overflow vulnerability exists in Apache Thrift's C++ implementation in the function THeaderTransport::writeVarint32() when handling a negative protocol id. This flaw could lead to memory corruption due to improper handling of input values.
Vibe-Trading AI version 0.1.0 through 0.1.6 contains multiple critical security vulnerabilities, including unauthenticated full API exposure and remote code execution (RCE). The primary critical issue allows unauthenticated attackers to execute arbitrary shell commands as root inside the container via the /sessions/{id}/messages endpoint due to missing authentication enforcement when API_AUTH_KEY is unset. Additional findings include authorization gaps, unauthenticated file uploads, permissive CORS configurations, and partial API key disclosure. The Docker container runs as root by default, increasing the impact of exploitation. A patch is available to address these issues.
Trigger.dev has a vulnerability where the deployment cancel operation is scoped only by project ID and not by environment ID. This allows an API key for a lower-trust environment (e.g., dev) to cancel deployments in higher-trust environments (e.g., production) within the same project. The deployment GET route correctly enforces environment scoping, but the cancel route does not, creating an authorization bypass. This affects both self-hosted and cloud deployments of Trigger.dev prior to version 4.5.6.
Trigger.dev versions prior to 4.5.4 contain multiple critical vulnerabilities in the self-hosted coordinator Socket.IO namespace. A hardcoded default secret allows unauthenticated access, enabling attackers to retrieve decrypted environment variables from any run if they know the run's internal ID. Additionally, unauthenticated write handlers allow attackers to send forged messages affecting arbitrary runs. These issues were fully resolved by removing the vulnerable V1 execution stack and default secrets in version 4.5.4. Managed cloud deployments were not affected due to non-default secrets.
CVE-2026-12392 is an information exposure vulnerability in Canonical MAAS that allows unauthenticated attackers to retrieve the RPC secret in plaintext via the vendor data metadata endpoint. This affects versions prior to 3.4.10, 3.5.14, 3.6.5, 3.7.3, and 3.8.0. The vulnerability requires that the target machine was deployed with the 'register as rack' option enabled and that the attacker can obtain or infer the machine's system ID to exploit the flaw.
MISP contains a cross-site scripting (XSS) vulnerability in the ID Translator feature affecting versions prior to 2.5.48. This vulnerability arises because event IDs returned from linked remote MISP servers are rendered without proper output encoding. An attacker controlling or compromising a linked server could inject malicious HTML or JavaScript that executes in the browser of authenticated users viewing the ID Translator page. Exploitation requires an authenticated user, a configured linked server, and navigation to the vulnerable page.
MISP versions prior to 2.5.48 contain an improper input validation vulnerability in the decaying model import functionality. This flaw allows authenticated users with decaying-model permissions to overwrite or modify decaying models belonging to other organizations, including changing ownership and default flags. The vulnerability arises because nested model keys with primary key, organization ID, and default flag can bypass input validation during import.
Nx is a monorepo solution for TypeScript and polyglot codebases. From 13.10.0 until 22.7.10 and 23.2.1, Nx migration planning reads the nx-migrations.migrations value from a target package manifest without validating that it is a contained relative path. A hostile direct dependency or a package introduced through a trusted package's packageGroup can supply .. segments or an absolute path, causing nx migrate to join an escaping destination onto its temporary directory. The migration archive can then write attacker-controlled bytes outside the temporary directory, while opening the destination stream can truncate an existing writable file even when no archive entry matches. This occurs during migration planning before review of the migration list or use of --run-migrations; the vulnerable installed Nx copy is reached when the normal nx@latest handoff is bypassed with NX_USE_LOCAL, NX_MIGRATE_USE_LOCAL, NX_MIGRATE_CLI_VERSION, --run-id, or fallback after a temporary-install failure. This issue is fixed in versions 22.7.10 and 23.2.1.
CVE-2026-96613 is an authorization vulnerability in the Meari IoT Cloud Platform OpenAPI Service. Authenticated users can access the full device shadow of any device by specifying its device ID without proper authorization checks. This flaw exposes sensitive data including device credentials, owner information, network details, and telemetry data. The vulnerability has a high severity rating with a CVSS score of 7.1. No affected versions or patch information are currently provided.
PostCSS Selector Parser is a CSS selector parser that integrates with PostCSS but does not require it. Prior to 7.1.6, src/parser.js splitWord() can receive a flat selector as one word token carrying many class or ID indexes because period and hash characters are not tokenizer word delimiters. The uniqs() deduplication and per-index class and ID membership checks repeatedly scan the class and ID index arrays, while a separate Sass-interpolation filtering pass also performs repeated linear scanning. Together, these passes make parsing quadratic in the number of indexes and allow a crafted selector to occupy a synchronous parser thread. The maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.
A security vulnerability has been detected in onetwothreeneth HospitalManagementSystem up to 9ef91ed6007314b6473110ed699dff76d158f61d. The impacted element is an unknown function of the file php/sessions.php. The manipulation of the argument ID leads to improper authentication. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.