CVE-2017-14226

The Bookly plugin for WordPress (up to and including 28.2) is vulnerable to Insecure Direct Object Reference (IDOR) via the 'bookly_get_form_id', 'bookly_render_complete', 'bookly_add_to_calendar', and 'bookly_rollback_order' AJAX actions. The 'bookly_get_form_id' handler stores an attacker-controlled 'order_id' into a new booking session, which 'bookly_render_complete' then trusts to return the order's secret token without verifying session ownership. This allows unauthenticated attackers to enumerate order IDs, disclose other customers' order tokens, retrieve calendar/appointment information, and permanently delete arbitrary non-completed bookings.

The Customer Reviews for WooCommerce plugin for WordPress (up to and including 5.120.0) is vulnerable to authorization bypass due to improper verification of user permissions. This allows unauthenticated attackers to permanently delete arbitrary attachments from the Media Library (including administrator-owned product images, logos, and documents) by injecting their IDs into a review that is later trashed and purged. Exploitation requires a public review-form link (a 13-hex formId) that exposes the nonce needed to reach the handler without any WordPress account or session.

The Automation Web Platform – Notifications and OTP for WooCommerce, Advanced Country Code plugin for WordPress (up to and including 4.8.6) is vulnerable to privilege escalation due to missing permission enforcement on the publicly accessible REST route `POST /wp-json/wawp/v1/signup/<op>` and the absence of a key allowlist in the `finish_registration_logic` function. The attacker-controlled `wawp_custom_fields` parameter is copied directly into `update_user_meta()`, allowing sensitive meta keys such as `wp_capabilities` and `wp_user_level` to be set. This enables unauthenticated attackers to register an account with the administrator role and gain full administrative access. When OTP verification is enabled, the OTP session token is returned in plaintext in the HTTP response, and the `handle_magic_link_request()` handler marks it as verified on any unauthenticated GET request containing it without checking the OTP code, making the OTP step trivially bypassable.

Prior to 9/18/2026, the iSteamX mobile application's AWS policy could grant authenticated users access to wildcard MQTT topics, which can expose other users' device data and allow the attacker to start and stop other connected users' devices. This risked exposing user profile information and potential scalding due to unintended device activation.

Omni C20 lacks proper certificate validation which could allow an attacker to perform a man-in-the-middle attack which could allow them to execute arbitrary code.

ServiceNow has remediated a missing authorization vulnerability that was identified in the ServiceNow AI Platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to extract instance data beyond what was intended, resulting in privilege escalation.

An unauthenticated Remote Code Execution via Arbitrary File Upload vulnerability in the web management interface in Honeywell PD45 Industrial Printer version F10.19.010040, allows upload of attacker controlled files without requiring authentication.

ServiceNow has remediated a SQL injection vulnerability that was identified in the ServiceNow AI Platform. This vulnerability could enable an unauthenticated user, in certain circumstances, to execute arbitrary SQL statements against the instance's underlying database and gain access to, or modify, instance data beyond what was intended.

DBHub, a database MCP server, in versions prior to 0.22.5 exposes an unauthenticated HTTP MCP endpoint when started in HTTP transport mode. Its protection based on comparing Origin and Host headers does not prevent DNS rebinding, allowing a malicious website to invoke MCP tools from the victim's browser. Depending on configuration, this can lead to reading, enumerating, and potentially writing database contents.

The http4s-scala-xml library in versions prior to 0.24.1 and 1.0.0-M39 uses a SAXParserFactory without security configuration to decode XML message bodies. With default JDK settings, the parser resolves DOCTYPE declarations, external entities, and external DTDs. Applications parsing untrusted XML are vulnerable to XXE, SSRF, and resource exhaustion attacks.