Unauthenticated remote attackers can retrieve server version information from Azure Access BLU-IC2 and BLU-IC4 physical access-control intercom appliances running firmware 1.19.5 or earlier, exposing fingerprinting data that aids follow-on targeting. The CWE-306 classification (Missing Authentication for Critical Function) hints that the underlying weakness may be a missing authentication check rather than a purely cosmetic banner leak, but the description as written establishes only version disclosure, and our assessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - confidentiality-only, no integrity or availability impact. EPSS is 0.35% (27th percentile), there is no CISA KEV entry, and no public exploit code has been identified at time of analysis; the practical risk is gated almost entirely by whether these appliances are reachable from untrusted networks.
Unauthenticated remote access to a critical function in Azure Access BLU-IC2/IC4 firmware through 1.19.5 lets a network attacker reach privileged functionality without credentials, with high impact to confidentiality, integrity, and availability on the device and on subsequent systems. The CVSS 4.0 base score is 10.0, matching the independent CVSS 3.1 assessment (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), so practical risk is driven mainly by whether the management/network interface is reachable; EPSS is low at 0.34% (26th percentile) and no public exploit identified at time of analysis.
BLU-IC2 and BLU-IC4 firmware through version 1.19.5 ships with a non-compliant TLS configuration (CWE-326, inadequate encryption strength), meaning transport sessions can be protected by deprecated protocol versions, weak cipher suites, or insufficient key lengths. An attacker who can obtain a man-in-the-middle position on the network path between a client and the device could intercept, downgrade, or manipulate those sessions to disclose or alter data in transit. The vendor assigns a maximum 10.0 CVSS 4.0 score, but exploitation realistically depends on an on-path presence rather than direct remote access to an exposed service, integrity impact is limited, and no public exploit has been identified at time of analysis; EPSS is 0.24% (14th percentile).
Cross-site request forgery in Azure Access BLU-IC2 and BLU-IC4 firmware through 1.19.5 allows remote attackers to induce an authenticated administrator to submit forged state-changing requests to the web management interface because anti-CSRF tokens are not implemented. Exploitation requires a concurrent privileged session and victim interaction, so the supplied CVSS 4.0 score of 10.0 is likely inflated; the assessed CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. No public exploit was identified at time of analysis, and EPSS is 0.17% (percentile 6%).
Unauthenticated remote code execution in win-cli-mcp-server versions prior to 0.2.0, where the resolveCommandPath helper interpolates a caller-supplied command name into a shell string (`where "<command>"`) executed via Node's child_process exec, letting shell metacharacters break out of the quotes and run attacker-controlled commands as the service account. Because the same helper is used to resolve and validate commands, the injection also sidesteps the project's command-whitelist safeguard, and exploitation only requires that an attacker control the command string reaching the MCP server's execution path - conditions that are broadest when the server is exposed via a network-facing transport rather than a local stdio session. CVSS 3.0 scores this 9.8 (AV:N/AC:L/PR:N/UI:N, full C/I/A impact); no public exploit code or CISA KEV entry was identified at time of analysis, and the flaw is fixed in release 0.2.0, which removes resolveCommandPath entirely.
Unauthenticated remote code execution affects MLflow Tracking Server deployments that expose the REST API, because the /mlflow/model-versions/create endpoint accepts an attacker-controlled model source path without validating it before file operations. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8), and the default configuration is vulnerable since the upstream fix adds an opt-in MLFLOW_CREATE_MODEL_VERSION_SOURCE_VALIDATION_REGEX control that performs no validation when unset. No public exploit code or CISA KEV entry was identified in the provided data; exploitation requires network reachability to the Tracking Server API.
MLflow's built-in basic authentication module (mlflow/server/auth) ships with and accepts trivially weak passwords - including the default admin credential 'password' in basic_auth.ini and self-service signups as short as 4 characters - so remote attackers can gain administrative access to an exposed tracking server simply by guessing or reusing the shipped default. Exploitation is unauthenticated from a network perspective (CVSS PR:N) but is not a true authentication-logic bypass: it requires the basic-auth module to be explicitly enabled and reachable, and it fails outright if the admin credential and user passwords were changed to strong values, which is why the independent assessment raises attack complexity to High and scores the issue 8.1 rather than the submitted 9.8. No public exploit code and no confirmed active exploitation were identified at time of analysis, and upstream has published a password-policy fix through a public commit.
Pre-authentication SQL injection in the WordPress plugin Contact Form CFDB7 (all versions up to and including 1.3.2) cascades into PHP object injection, allowing remote attackers to reach code paths that can fully compromise confidentiality, integrity, and availability of an affected WordPress site. The CVSS vector (AV:N/AC:L/PR:N) confirms the attack is remotely reachable and unauthenticated, and the plugin must simply be installed and active on the target - no valid account or victim action is required in practice. Exploitation status is unconfirmed: there is no CISA KEV entry and no public exploit code identified at time of analysis, and the EPSS score is low at 0.33% (24th percentile), so this appears to be a severe but not yet broadly exploited issue; it was disclosed by Mandiant (MNDT-2025-0006).