A SQL injection vulnerability was identified and addressed in Tanium Threat Response. This vulnerability allows improper neutralization of special elements used in SQL commands, potentially enabling unauthorized database access or manipulation. The issue affects specific versions of the product prior to fixed releases.
A server-side request forgery (SSRF) vulnerability was identified and addressed in Tanium Threat Response. This vulnerability affects specific versions prior to fixed releases. The CVSS score is 6.5, indicating a medium severity level. The vulnerability allows an attacker with low privileges to cause the server to make unauthorized requests, potentially exposing sensitive information. No known exploits are reported in the wild. Tanium has released fixes for the affected versions.
A SQL injection vulnerability (CVE-2026-87024) was identified and addressed in Tanium Asset. This vulnerability allows improper neutralization of special elements in SQL commands, potentially leading to unauthorized data access or modification. It affects specific versions of Tanium Asset prior to fixed releases. The vulnerability has a high severity rating with a CVSS score of 7.2.
An information disclosure vulnerability (CVE-2026-87076) was identified and addressed in Tanium Discover. This flaw could allow unauthorized actors to access sensitive information. The vulnerability affects specific versions of Tanium Discover prior to fixed releases. The CVSS score is 6.5, indicating a medium severity level. No known exploits are reported in the wild. The vulnerability does not impact cloud services and requires local privileges to exploit.
CVE-2026-86865 is a high-severity SQL injection vulnerability in Tanium Asset. It allows improper neutralization of special elements in SQL commands, potentially leading to full compromise of confidentiality, integrity, and availability. The vulnerability affects specific versions prior to fixed releases. Tanium has addressed this issue in later versions.
Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to modify the scheduled post records of other users. The b2s_calendar_move_post AJAX handler in includes/Ajax/Post.php issues an UPDATE against the b2s_posts table using only the attacker-supplied b2s_id primary key with no blog_user_id ownership constraint, allowing any user with the edit_posts capability to reschedule, suppress, or alter the publication state of any other user's scheduled social media post.
Adenion Blog2Social plugin for WordPress before 9.1.0 exposes the email addresses of all registered WordPress users to low-privileged accounts. The b2s_search_user AJAX handler in includes/Ajax/Get.php invokes B2S_Tools::searchUser() in includes/Tools.php, which returns the email address of every matching user without restricting access to callers holding the list_users capability, allowing any user with the edit_posts capability to retrieve user email addresses including those of administrators.
Adenion Blog2Social plugin for WordPress before 9.1.0 allows low-privileged users to enumerate WordPress user accounts. The b2s_get_select_mandant_user AJAX handler in includes/Ajax/Get.php resolves arbitrary user IDs supplied in the owner parameter to display names without verifying that the caller is authorized to read user account data, allowing any user with the edit_posts capability to map WordPress user IDs to display names and confirm account existence for arbitrary IDs.
The lack of signature verification of firmware update packages in VEO and VEO-XS Wi-Fi monitors, in versions prior to 01.48.001, allows an attacker who controls the delivery of an update to install unauthorised firmware.
The lack of TLS certificate validation when downloading firmware updates in VEO and VEO-XS Wi-Fi monitors, in versions prior to 01.48.001, allows an attacker to perform man-in-the-middle attacks on the update channel.
CVE-2026-87886 is a high-severity insecure file permissions vulnerability in the Acronis Backup plugin for cPanel & WHM and the Backup extension for Plesk. This flaw allows local privilege escalation by enabling attackers to gain elevated privileges on affected systems. The vulnerability has been exploited in the wild in limited, targeted attacks against the cPanel plugin. Acronis has released patches to address this issue and urges users to update immediately.
Transmission of the home Wi-Fi credentials without encryption during the pairing process between the DuoxMe application and VEO and VEO-XS Wi-Fi monitors, in versions prior to 4.3.4 of the application and 01.50.001 of the monitor firmware, allows an attacker on the Wi-Fi Direct network to intercept the network password.
Cleartext storage of sensitive information in the DuoxMe application for Android, in versions prior to 4.3.4, allows an attacker with local access to the device to retrieve the credentials stored by the application and impersonate the user account.
A Broken Access Control vulnerability in NIAEFEUP's tts-be backend prior to version 2.1.0 allows remote attackers to bypass authorization checks by chaining unauthenticated API endpoints. This enables enumeration and extraction of sensitive Personally Identifiable Information (PII) including full names, student IDs, class schedules, and photos. The issue was fixed in version 2.1.0.
miniOrange JWT Authentication for WP REST APIs plugin for WordPress before 4.8.0 contains an authentication method downgrade vulnerability that allows unauthenticated attackers to bypass administrator-configured authentication by supplying a specific GET parameter without any capability check or nonce verification. Attackers can force the plugin to use Basic HTTP authentication regardless of configured JWT or API token settings, then exploit distinguishable error codes and the absence of rate limiting to perform unthrottled username enumeration and credential guessing attacks.
OpenDJ is an LDAPv3 compliant directory service. Prior to 5.1.1, the JMX RMI connector in opendj-server-legacy/src/main/java/org/opends/server/protocols/jmx/RmiConnector.java processes attacker-controlled credential objects before authentication without a restrictive jmx.remote.rmi.server.credentials.filter.pattern, and RmiAuthenticator.authenticate in opendj-server-legacy/src/main/java/org/opends/server/protocols/jmx/RmiAuthenticator.java accepts an unconstrained Object array rather than a two-element String[]. When the JMX Connection Handler is enabled and its TCP listener is reachable, an unauthenticated remote attacker can submit a crafted serialized Java object and achieve code execution in the OpenDJ server process. The handler is disabled by default, and successful exploitation depends on the runtime classpath and Java version; remote code execution was demonstrated against OpenDJ 4.4.15 on JDK 11 with Jackson 2.12.6.1. This issue is fixed in 5.1.1.
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.
CVE-2026-62263 is a critical deserialization vulnerability in OpenIdentityPlatform's OpenAM prior to version 16.1.2. The flaw arises because the WebAuthnAuthentication.deserialize method applies an ObjectInputFilter that insufficiently restricts serialized objects beyond the root AuthenticatorImpl object, allowing nested malicious gadget classes to execute code during deserialization. This vulnerability enables a pre-authentication attacker to bypass previous mitigations by supplying a crafted userHandle with a valid root object but malicious nested payloads. The issue is resolved in OpenAM version 16.1.2.
Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, AuthorizationCodeGrantTypeHandler requires a code_verifier only when the realm-wide codeVerifierEnforced setting is enabled, even when an authorization code stores a code_challenge. Because that setting is disabled by default, an attacker who intercepts a PKCE-protected authorization code can omit code_verifier and redeem the code, while an explicitly incorrect verifier is rejected. Public clients are directly affected, and confidential-client exploitation additionally requires client authentication material or another redemption context. This issue is fixed in version 16.1.1.
Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, the private_key_jwt client authentication path uses ClientJwksResolverCache without reliably binding a cached jwks_uri resolver and verified assertion to the expected clientID in ClientCredentialsReader. An attacker controlling any registered client with published keys, including one obtained through open dynamic registration when enabled, can authenticate as another client whose keys are exposed through jwks_uri and mint tokens in that client's name across realms in the same OpenAM process. This issue is fixed in version 16.1.1.