Authentication Bypass

Privilege escalation in the Ultimate Member WordPress plugin affects all versions through 2.13.1, allowing an authenticated attacker to manipulate a user-controlled key that the plugin fails to bind to the requester's own account or privileges, thereby elevating a low-privilege account to a higher role such as administrator. The flaw requires an authenticated account (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base score 8.8), but because Ultimate Member supplies front-end user registration, an attacker can typically self-register on sites with open registration enabled - the common deployment mode - lowering the practical barrier to entry; sites that disable open registration require a pre-existing credential. Exploitation status at time of analysis: no public exploit identified at time of analysis, and the vulnerability is not confirmed actively exploited (CISA KEV), though the low attack complexity and high confidentiality, integrity, and availability impact make rapid patching a priority, with no EPSS score supplied in the available intelligence.

OAuth 2.0 PKCE enforcement bypass in OpenAM before 16.1.3 allows an attacker who intercepts an authorization code issued through OpenID Connect hybrid flows to redeem it for a public client's tokens using any non-empty code_verifier, because PKCE is applied only when response_type is exactly code. The attack is remote and unauthenticated from the token endpoint perspective but requires user interaction and the ability to intercept the code; deployments not using hybrid flows are not affected. No public exploit identified at time of analysis, and a vendor fix is available in OpenAM 16.1.3; this is a credible mid-tier priority rather than a drop-everything emergency.

Unauthenticated remote attackers can instantiate arbitrary Java classes in OpenIdentityPlatform OpenAM before 16.1.3 through the legacy JAX-RPC SOAP interface, leading to server crashes, classpath probing, and potential code execution via gadget chains. The vulnerability requires the JAX-RPC endpoint to be present and network-reachable at /jaxrpc/*, but no authentication or user interaction is needed because the session identifier is accepted without validation. No public exploit code has been identified at time of analysis; the CVSS 4.0 score is 8.8, and the independent assessment rates it as a credible high-priority issue rather than an inflated score.

Unauthenticated spacecraft command injection and telemetry exfiltration in NASA-AMMOS AIT-Core through 3.1.1: the ait-server ZeroMQ telemetry and command broker binds its XSUB (TCP 5559) and XPUB (TCP 5560) sockets to all network interfaces by default with no authentication or transport security, so any unauthenticated remote attacker with a network path to the ground bus can publish onto internal topics including __commands__, push forged commands through command_stream onto the command-uplink UDP path, subscribe to live command and telemetry traffic, or disrupt the bus outright. The assessed CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting unauthenticated, low-complexity remote exploitation that fully compromises confidentiality, integrity, and availability of the command and telemetry path; no public exploit code has been identified at time of analysis, and this CVE is not in CISA KEV. The exposure is conditional on the shipped default configuration - exploitation requires network reachability to ports 5559 and/or 5560, which is typically an isolated or segmented mission network rather than the public internet - and the fix is AIT-Core 3.1.2, which rebinds these ZeroMQ sockets to loopback by default.

Bouncy Castle for Java before 1.86 fails to tie a Remove proposal in an MLS (RFC 9420) external commit to the joining party, allowing any holder of the group's public GroupInfo to evict an arbitrary member and take over that member's slot in the ratchet tree. Exploitation requires only that an application use the library's MLS module and accept external commits through the public Group.externalJoin / Group.handle API on an affected version; no group membership, credential, or user interaction is needed, and the missing credential check existed only in the gRPC interop harness, protecting none of the other API callers. The vendor rates this 8.7 (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N), and there is no public exploit identified at time of analysis, though the flaw is trivially reachable by anyone who legitimately receives GroupInfo.

Bouncy Castle for Java 1.81 through 1.85.2 fails to verify that a third-party OpenPGP signature was issued by a component key actually granted certification authority, so the high-level certificate API will attribute an attacker-made certification or trust delegation to the certificate's offline primary key. An attacker must already hold the private key of a restricted subkey (one bound only with SIGN_DATA, or a legacy RSA encryption subkey whose algorithm can still sign) that lacks the RFC 9580 sec. 5.2.3.29 CERTIFY_OTHER flag; they can then issue a positive User ID certification or a full-trust depth-one direct-key delegation that getCertificationBy()/getDelegationBy() report as a valid chain, and any application treating isValid() as an identity or trusted-introducer decision will accept the forged assertion at the primary key's authority. The flaw is a privilege promotion of an already-compromised subkey rather than a key-recovery attack, no public exploit code has been identified at time of analysis, and vendor fixes are available in 1.86.

Unauthenticated attackers can seize a privileged point-of-sale session on WordPress sites running the TillKit plugin before 1.0.5, letting them read customer and site-user personal data and modify store records. On activation the plugin creates a privileged POS account protected by a hard-coded, publicly known PIN that it never forces administrators to change, and its public POS login endpoint authenticates on that PIN alone with no identity or capability check (CWE-287); the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N confirms this is remotely reachable with no credentials and no user interaction. Publicly available exploit code exists, but there is no confirmed active exploitation (CISA KEV) and EPSS is low at 0.14% (3rd percentile), so real-world urgency depends on whether TillKit is actually deployed and whether the default PIN is still in place.

TOTP replay in the WP 2FA WordPress plugin (versions before 4.1.0) allows an attacker who already knows an account's password and can capture a valid time-based one-time passcode within its ~30-second validity window to reuse that same code and complete login without ever knowing the second factor - including on administrator accounts. The defect (CWE-287, improper authentication) is that consumed codes are never invalidated, so replays succeed while the code is still live; this does not allow bypass from scratch, since it requires prior credential compromise plus real-time observation of a code via phishing, a proxy, MITM, or logging. Exploitation is conditional and targeted rather than scalable, consistent with the assessed CVSS:3.1/AV:N/AC:H/PR:L/UI:N (7.5) and the very low EPSS of 0.19% (8th percentile); publicly available exploit code exists, but there is no CISA KEV evidence of active exploitation. The vendor has released a fix in WP 2FA 4.1.0, and the issue is tracked as EUVD-2026-91934.

Unauthenticated attackers can permanently delete arbitrary posts, pages, products, and media attachments on any WordPress site running the Photo Reviews for WooCommerce plugin through version 1.2.30. The plugin accepts attacker-controlled post IDs in the public wcpr_image_upload_id parameter of a review submission and stores them as the review's 'reviews-images' comment meta without verifying that those IDs belong to attachments owned by the submitter; when the review is later deleted, the delete_reviews_image() handler unconditionally calls wp_delete_post( $id, true ) on every stored ID. Because the trigger is a privileged action - an administrator deleting the planted review, or WordPress's built-in wp_scheduled_delete cron emptying the comment trash roughly 30 days after the review is trashed - this is a credible high-integrity, high-availability issue rather than an instantly weaponizable one, and no public exploit code or CISA KEV entry was identified at time of analysis.

Unauthenticated attackers can redirect activation and registration-complete emails to an arbitrary address in Simple Membership (WordPress plugin) versions up to and including 4.8.3, leading to disclosure of a pending member's username and plaintext password, and can activate that member's account without consent. The flaw resides in the resend-activation and email-activation endpoints, which are invoked on frontend init without authentication, nonce, capability, or ownership checks, and accept a recipient address from attacker-controlled POST data. Exploitation requires the target site to have at least one pending, unactivated member account; no public exploit code has been identified at time of analysis.

Unauthenticated attackers can read privacy-restricted member profile field data in the WordPress plugin Ultimate Member (all versions up to and including 2.13.1) by calling the publicly reachable AJAX endpoint wp_ajax_nopriv_um_get_members, which fails to verify that the requester is authorized to see fields marked owner-only, members-only, or role-restricted. The endpoint's supposed protection, the 'um-frontend-nonce' token, is published to every anonymous visitor through wp_localize_script, so it provides no real access control and any anonymous visitor can satisfy the endpoint's checks; this yields a high-confidentiality, no-integrity/no-availability impact (CVSS 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). No public exploit code has been identified at time of analysis and there is no CISA KEV entry, but the attack surface is default-configuration and remote, so the only practical prerequisite is that the site actually has privacy-restricted profile fields containing sensitive values. The vendor addressed the issue in Ultimate Member 2.14.0, whose release notes explicitly credit Wordfence for reporting CVE-2026-93428.

Armatura One ships with a fixed, vendor-defined password assigned to its database superuser account during database initialization, so it is identical across installations unless an administrator has changed it. Anyone who already has access to the underlying host operating system and knows this value can authenticate to the database as the superuser on any deployment where the default has not been rotated. The flaw is rated 8.6 under CVSS 4.0 (assessed as CVSS 3.1 AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), requires local OS-level access rather than a network path, requires no user interaction or application-level authentication, and there is no public exploit identified at time of analysis; exploitation is fully prevented on systems where the superuser password has been reset.

Unauthenticated WebSocket endpoints in the Monta EV charging platform (monta.app, all versions) allow any network-reachable attacker to impersonate a charging station and thereby read sensitive backend data or perform unauthorized actions on the platform. The weakness is a missing-authentication flaw (CWE-306) rated 9.3 under CVSS 4.0 and mapped by the independent assessment to CVSS 3.1 AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact and low availability impact, meaning unauthenticated remote attackers need no credentials, user interaction, or non-default configuration - network reachability to the charging-station WebSocket service is the only practical prerequisite. There is no public exploit identified at time of analysis and no KEV listing, but ICS-CERT has published an advisory covering all versions, and the absence of a version-based mitigation makes exposure reduction the primary interim control.

Missing rate limiting on the Monta EV-charging platform's WebSocket API authentication endpoint allows unauthenticated remote attackers to send unlimited login requests, enabling either resource-exhaustion denial of service or sustained credential brute-forcing against Monta accounts. The issue affects monta.app (all versions tracked by EUVD) and carries a CVSS 4.0 base score of 8.7 (High), with the assessed impact concentrated on availability (VA:H) and no direct confidentiality or integrity effect in the base vector; credential compromise via brute force is a downstream outcome that additionally requires weak, guessable, or non-MFA-protected credentials. No public exploit code has been identified at time of analysis, and the flaw has not been confirmed as actively exploited (CISA KEV); reporting originates from CISA ICS-CERT advisory ICSA-26-274-02.

UTMStack deployments running versions before 11.2.16 can be fully taken over through an authentication bypass in the InternalApiKeyFilter, which accepts the shared Utm-Internal-Key header as proof of identity on every API endpoint rather than only on internal machine-to-machine routes. Tracked as CVE-2026-82042 (CWE-306, missing authentication for a critical function) and rated 9.3 under CVSS 4.0 with an equivalent CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, a single request that presents the correct key value grants full administrative API access without a user account, JWT, or user interaction, allowing the attacker to create accounts, manage users, exfiltrate data, and modify security rules. The decisive limiting factor is obtaining the secret itself: the key is a shared machine-to-machine credential held by sibling components such as agent-manager, the event-processor plugins, and the installer/updater, so realistic attack paths involve a leaked, default, or weak INTERNAL_KEY value, read access to the deployment environment, or compromise of a container that legitimately holds it. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, but the vendor-released fix in 11.2.16 hardens the filter with a fixed route allowlist, constant-time comparison, audit logging, and an optional INTERNAL_KEY_ALLOWED_CIDRS source-IP restriction.

Incorrect authorization in the LangGraph Python SDK (langgraph-sdk) versions 0.1.45 through 0.4.3 lets an authenticated user read, update, or delete resources belonging to other users, because the resource-scoped decorators @auth.on.threads, @auth.on.assistants, and @auth.on.crons ignore their actions= argument and register the handler as a wildcard for every action on that resource. That wildcard handler is matched ahead of broader fallback handlers, so any action, ownership, or permission checks implemented in those fallbacks are silently skipped. The flaw is conditionally scoped: a deployment is only exposed if it uses these decorators together with actions= and relies on separate fallback handlers for enforcement, and authentication requirements are confirmed as authenticated (CVSS PR:L) with no public exploit identified at time of analysis. This is fixed in langgraph-sdk 0.4.4.

Dogtag PKI (pki-core) and its commercial counterpart, Red Hat Certificate System 9/10/11, contain a fail-open authentication flaw in the CMCAuthForEST plugin that lets an authenticated, low-privileged EST enrollment user obtain CA-signed certificates bearing arbitrary subject names. The bug is triggered when an EST fullcmc enrollment request is sent over BasicAuth without an end-user TLS client certificate; the SSL_CLIENT_CERT session attribute then retains the EST subsystem's agent certificate, so downstream authorization logic wrongly grants agent-level privileges. Exploitation is assessed as requiring only a valid EST user account (CVSS 8.1, PR:L, unauthenticated by client certificate, no user interaction), making it a realistic privilege-escalation path for any provisioned EST user or insider; however, no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (not in CISA KEV).

Authenticated API key holders can read restricted issue contents and comments in Phproject (versions 1.1.6 through 1.8.6) because the REST API issue endpoints single_get, single_comments, and single_comments_post never invoke the allowAccess() authorization routine, silently bypassing the security.restrict_access confidentiality control. Attackers with any valid, active API key can retrieve restricted issues and comments - including owner and author email addresses - and post unauthorized comments to issues they should not be able to access. Exploitation requires the target instance to have 'Restrict issue access' enabled and a valid API key; no public exploit code has been identified at time of analysis, and impact is bounded to information disclosure plus limited unauthorized writes with no availability impact. Fixed in Phproject 1.8.7.

Loom for AWS deployments running a version before 1.6.1 with no identity provider configured expose an unauthenticated super-admin takeover of the agent control plane, allowing any remote party to register tool servers, read stored integration credentials, and rewrite the IAM role policies attached to managed agent roles simply by sending requests to the application API; no credentials, user interaction, or crafted payload are required. The flaw is a missing-authentication-for-critical-function (CWE-306) defect in the authentication dependency, where the local-development bypass intended for environments without Cognito/OIDC activated automatically for every request instead of failing closed. Exploitation is conditional on that IdP-less configuration, so environments with a properly configured identity provider are not reachable through this path; a vendor patch ships in 1.6.1, and no public exploit code or confirmed active exploitation was identified at time of analysis.

Improper access control in Apache Traffic Server 9.0.0-9.2.14 and 10.0.0-10.1.3 allows unauthenticated remote requests that should have been denied to be forwarded to backend systems the proxy is meant to protect, yielding high confidentiality and integrity impact on those subsequent systems (SC:H/SI:H) with no direct impact on the Traffic Server host itself (VC:N/VI:N/VA:N). Exploitation is conditional, not routine: the CVSS 4.0 vector carries AT:P, meaning a specific attack requirement outside the attacker's direct control must be satisfied before a request succeeds, and this is corroborated by the independent assessment as a genuine but conditional risk rather than an urgent emergency. No public exploit code or confirmed active exploitation was identified at time of analysis; fixed versions are 9.2.15 and 10.1.4, and this CVE supersedes CVE-2026-41920, whose record understated the 9.x affected range as 9.0.0-9.1.14.

Sandbox escape and arbitrary code execution in Google Chrome on Windows (versions prior to 154.0.8037.97) arise from incorrect authorization in the browser's FileSystem component, letting a remote, unauthenticated attacker break out of the renderer sandbox and run code at the browser's privilege level after convincing a victim to open a crafted HTML page. Exploitation requires the user to visit an attacker-controlled page (CVSS PR:N/UI:R, scope changed) and is neither automatic nor zero-click; no public exploit identified at time of analysis, and CISA's SSVC rates exploitation as none with automatable flagged no. That said, the signal is mixed: 9.6 CVSS with total technical impact contrasts with a low EPSS of 0.21% (10th percentile) and a platform-restricted, interaction-dependent attack path.

Improper authorization in MISP's correlation handling lets an authenticated user with at least read access to some events retrieve attribute values and event metadata from events they are no longer permitted to view, in deployments running MISP before v2.5.48. The leak occurs because correlation lookups are authorized against a point-in-time distribution snapshot stored on the correlation row, which carries no published flag, so the check diverges from the live event ACL once a correlated event is unpublished or moved to a different sharing group; the CVSS vector (PR:L) confirms the attacker must be authenticated, and no public exploit code has been identified at time of analysis. Impact is confined to confidentiality - read-only exposure bounded to those correlated events that were restricted after the correlation was created - making this a moderate-severity, measured-priority patch rather than an emergency.

Improper input validation in MISP's decaying model import endpoint allows an authenticated user with the perm_decaying permission to overwrite, re-own, or re-flag decaying models belonging to other organisations in MISP versions before 2.5.48. The import handler strips only the top-level id and uuid fields and pins org_id/default on the outer array before saving the record flat, so a nested 'DecayingModel' key can smuggle its own primary key, organisation identifier, and default flag past those guards, letting an attacker modify an existing model in place, reassign its organisation, or set it as the organisation default and thereby alter scoring behaviour for other users. This is a bounded authorization/mass-assignment flaw rather than an unauthenticated critical: successful exploitation requires network access to the instance plus an account holding perm_decaying (not granted to ordinary users by default), and there is no confidentiality or availability impact; no public exploit code or confirmed active exploitation was identified at time of analysis, and an upstream fix commit (70e319e4b) exists.

User impersonation in the ProcessOne ejabberd XMPP server, affecting all releases from the initial version through 26.04, allows any party that holds valid credentials for a single account to authenticate as an arbitrary other user by supplying an unchecked authzid value in the SASL-PLAIN exchange. Because the server fails to bind the requested authorization identity to the authenticated one, a low-privileged, authenticated attacker can act with the confidentiality and integrity privileges of any targeted account - including administrative or federated identities - across the XMPP service. The flaw is not listed in CISA KEV (no confirmed active exploitation), although the reported CVSS 4.0 vector carries an exploit-maturity metric of Proof-of-Concept (E:P), indicating proof-of-concept-level exploit code maturity; the independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, framing it as a credentialed authentication/authorization flaw rather than a fully unauthenticated takeover.

Unauthenticated attachment disclosure in YesWiki before 4.6.7 allows remote attackers to bypass page read ACLs and retrieve confidential files by directly invoking the attachment download handler with a known page tag and file parameter. The missing authorization check (CWE-862) yields high confidentiality impact with no integrity or availability impact, reflected in the independent CVSS 3.1 assessment of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and the CVSS 4.0 score of 8.7. No public exploit code has been identified at time of analysis, but exploitation requires only knowledge of the page tag and attachment name and works against default deployments where ACLs are the sole protection.

Authorization bypass in YesWiki before 4.6.7 lets unauthenticated remote attackers call admin-only API routes when the instance has public API mode enabled, enabling configuration overwrites via api/ci/update_config and listing, downloading, or deleting backup archives via api/archives. The vulnerability is a missing-authorization flaw in ApiService::isAuthorized(), rated 9.2 under CVSS 4.0 but with a significant prerequisite: public API mode is a non-default administrative setting, so default installations are not exploitable through this path. No public exploit code or confirmed active exploitation is identified in the available intelligence, but the impact is high for exposed instances and patching to 4.6.7 is the primary fix.

Unauthenticated attackers can overwrite any existing wiki page in YesWiki versions before 4.6.7 by exploiting an authorization bypass in the Bazar entry-creation flow, where a crafted id_fiche matching an existing page is accepted without enforcing that page's write ACL. This enables mass defacement and content destruction, though exploitation requires the Bazar feature to be reachable without authentication and knowledge or guessing of valid page identifiers. A vendor patch is available in YesWiki 4.6.7, and no public exploit code has been identified at time of analysis.

Unauthenticated attackers can delete or overwrite federated entries in YesWiki instances before 4.6.7 that have ActivityPub federation enabled and mirror at least one remote entry, because the ActivityPub inbox does not bind the verified HTTP signature signer to the activity actor. Any party can generate their own ActivityPub keypair and sign a Delete or Update activity that references a mirrored entry's sourceUrl, causing the target instance to act on another actor's entry. No public exploit code has been identified at time of analysis, and the impact is limited to integrity and availability of federated entries - it does not allow reading private data or compromising the host.

Authenticated low-privilege users of YesWiki before 4.6.7 can bypass per-page write ACLs through the comments API editComment route (api/comments), overwriting arbitrary pages or comments and reparenting existing content by placing a victim page's identifier in the pagetag field. Because the route trusts the attacker-supplied key rather than validating it against the caller's write permissions, the flaw yields high integrity impact with limited availability impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L) and requires only a valid account, so instances with open or self-service registration are most exposed. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fix in YesWiki 4.6.7.

Authenticated users on YesWiki instances running versions prior to 4.6.7 can bypass ownership scoping in the triples delete API by submitting an empty filter, letting them delete or forge arbitrary semantic triples regardless of who owns them (CWE-863, CVSS 7.2). The most damaging abuse path removes the triple that records admins-group membership, emptying the administrator group and locking every administrator out of the site's authorization layer. The flaw is network-reachable and requires only a low-privilege authenticated account (CVSS PR:L) with no user interaction; no public exploit code has been identified at time of analysis, and the vendor has released a fix in 4.6.7.

Missing authorization in the YesWiki tags tool (listpagestag and includepages actions) lets unauthenticated remote attackers enumerate ACL-restricted pages and read their names along with body-derived titles on any instance running YesWiki before 4.6.7. Because the CVSS 4.0 vector carries PR:N/UI:N/AC:L, no credentials, no user interaction, and no non-default configuration are needed - the affected actions simply fail to apply read-ACL filtering, so default installations are exposed whenever ACL-restricted pages exist. The leak is limited to page names and derived titles rather than full page bodies, and no public exploit code or confirmed active exploitation was identified at time of analysis, though EPSS-style urgency is tempered by the low-value, low-bandwidth nature of the disclosure.

Missing authorization in the SiYuan note-taking server before 3.8.5 allows any unauthenticated visitor to a published document to read database rows that were explicitly marked password-protected or publish-disabled, by invoking the /api/export/preview endpoint against a public document that embeds a database view. Rated CVSS 4.0 8.7 (HIGH) and CWE-862, the issue is a clean remote-unauthenticated disclosure profile (AV:N/AC:L/AT:N/PR:N/UI:N, VC:H with no integrity or availability impact), so exploitation is limited to reading protected rows' primary-key text and cell values; no public exploit code has been identified at time of analysis, and the vendor has shipped 3.8.5 as the fix.

Firmware images pushed to Moxa MGate MB3170 and MB3270 series protocol gateways are not cryptographically validated before installation, so a modified or counterfeit image is flashed with the same trust as a vendor-signed one. Exploitation requires an attacker to already hold high-privilege (administrative) access to the device's firmware update interface and to reach it over the network; once that access exists, no additional weakness is needed and no user interaction is required. Successful abuse yields code execution on the gateway plus persistence across subsequent firmware updates, but the impact is confined to the device itself rather than downstream OT systems. There is no public exploit identified at time of analysis, no CISA KEV listing, and no EPSS score supplied. This is a genuine but access-gated integrity flaw rather than a mass-exploitation threat.

Unauthenticated attackers can hijack arbitrary WordPress accounts, including administrators, on sites running the WPMobile.App - Android and iOS App Builder plugin (wpappninja) in all versions up to and including 11.82, because a missing authorization check exposes password-reset URLs that the plugin's push queue has mirrored from outbound emails. The issue carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and the assessed vector matches the vendor listing; exploitation is contingent on the non-default mail-to-push setting (wpmobile_auto_mail=1) being enabled and on a password-reset email existing in the queue, which an attacker can induce through WordPress's standard lost-password flow. No CISA KEV entry and no public exploit code were identified at time of analysis, so the flaw is not confirmed as actively exploited, but the combination of unauthenticated reach, low complexity, and full account-takeover impact makes it high priority wherever the prerequisite configuration is in place.

Authentication bypass in the WordPress plugin JSON API Auth (all versions up to and including 3.1.2) lets unauthenticated remote attackers harvest a live Administrator logged_in cookie from a cached JSON response and use it to take over the site. The underlying defect sits in the required PI-Media/json-api parent plugin, whose controller-dispatch transient cache is keyed only by URI and query string with HTTP method and POST body ignored, so the authenticated /api/auth/generate_auth_cookie/ response - which embeds a wp_generate_auth_cookie() session cookie directly in its JSON body - is replayed to any subsequent unauthenticated GET, with the plugin's nominal HTTPS enforcement trivially defeated by passing insecure=cool. Our independent assessment keeps the full confidentiality and integrity impact of the vendor vector but treats the access complexity as High (base 8.1 rather than 9.8) because exploitation is opportunistic and conditional: both plugins must be installed and active with the Auth controller enabled, and a legitimate Administrator must have POSTed to the cookie-generation endpoint within the preceding 24-hour transient TTL; no public exploit identified at time of analysis.

Uniform Resource Identifier name-constraint bypass in Bouncy Castle .NET (bc-csharp) before 2.7.0 allows a name-constrained subordinate CA - or anyone able to obtain a certificate with an attacker-chosen subjectAltName URI from that CA - to evade permitted or excluded uniformResourceIdentifier constraints during RFC 5280 certification path validation. Because the PkixNameConstraintValidator helper ExtractHostFromURL slices the host out of the URI string without first isolating the RFC 3986 authority component, a crafted URI containing '@' (userinfo), ':' (port) or path/query/fragment delimiters produces a host value that differs from the URI's true host, so the leaf is judged unconstrained when it should not be; the vendor rates this CVSS 4.0 8.2, exploitation is unauthenticated per the vector (PR:N) but strongly conditional, and no public exploit code has been identified at time of analysis. Deployments that do not rely on bc-csharp for path validation or that never enforce URI-type name constraints on a subordinate CA are not affected.

Any WordPress site running the Divi Membership plugin at version 2.3.0 or earlier can be fully taken over by an unauthenticated remote attacker who simply requests a crafted URL, because the plugin unconditionally trusts an attacker-supplied user ID and issues a valid WordPress authentication cookie for it. Rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and classified as CWE-287 improper authentication, exploitation requires no authentication, no user interaction, and no non-default configuration, making it a top-priority issue for affected sites. Notably, the vulnerable code path is registered on every front-end request even if PayPal is disabled or never configured, so the common assumption that an unconfigured payment gateway is harmless does not hold here; no public exploit code has been identified at time of analysis, but the attack is a single GET parameter and requires no tooling.

Unauthenticated attackers can obtain a full administrator session on any WordPress site running the DevKit Pro plugin at version 2.3.0 or earlier by setting an attacker-controlled `original_user_id` cookie to a known administrator's user ID, harvesting the switch-back nonce the plugin renders publicly in the site footer for any visitor carrying that cookie, and POSTing it to the plugin's `revert_switch` handler. The root cause is a privilege-check logic error rather than a memory-safety bug: the handler's `verify_nonce_and_capability()` routine checks the `manage_options` capability against the user named in the attacker-supplied cookie instead of against the actual requester, so the subsequent `wp_set_auth_cookie()` call mints an authenticated session for the impersonated administrator, resulting in complete site takeover. Our independent assessment confirms the 9.8 CVSS (AV:N/AC:L/PR:N/UI:N) is genuine and not inflated: exploitation needs only a default install of the affected plugin (version 2.3.0 or lower) with the front-end revert path reachable and a valid administrator user ID such as the default ID 1, with no authentication, user interaction, or non-default configuration barrier; no public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV).

Discord libdave before 1.2.0 can accept an unauthorized participant into an end-to-end encrypted media session because it does not reject an MLS Welcome message whose group roster contains an unrecognized user ID. An attacker who controls the DAVE signaling path, such as a malicious or compromised Discord voice gateway or an equivalent position able to add, alter, or withhold MLS signaling, can exploit this to compromise the confidentiality and integrity of voice and video content; no client authentication or user interaction is required, but the signaling-path requirement raises the practical bar. A vendor patch is available in libdave 1.2.0, and no public exploit code was identified at time of analysis.

A hardcoded API key ships inside the GeoVision GV-Eye Android application (V3.6.0) and can be recovered by reverse engineering the publicly distributed APK, allowing anyone who extracts it to invoke whatever GeoVision backend API operations that key authorizes. The impact is confidentiality-only (C:H, I:N, A:N) scoped to a single embedded credential, and the independent assessment scores it as a local-vector issue (AV:L) because the attacker must first obtain and analyze the client package. No public exploit code identified at time of analysis, and the CVE is not listed in CISA KEV; the practical damage ceiling depends on whether GeoVision rotates or revokes the leaked key on the server side.

Hardcoded API key exposure in the GeoVision GV-Eye Android application (V3.6.0) allows unauthenticated remote attackers to extract the key from the publicly distributable APK via reverse engineering and use it to access backend or third-party services, resulting in high confidentiality impact. With a CVSS score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and CWE-798 classification, the vulnerability requires no user interaction or special privileges, though the actual blast radius is limited by the permissions associated with the single exposed key. No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis.

Incorrect access control in TransformerOptimus SuperAGI v0.0.14 lets an authenticated, low-privilege organization user in a multi-tenant deployment supply another organization's agent_id or agent_execution_id to the save_agent_as_template and publish_template endpoints, which perform no ownership check on the referenced agent or execution - enabling cross-organization disclosure of agent data and unauthorized template creation. Exploitation requires a valid authenticated account (PR:L) and a deployment where multiple organizations' agents coexist, so single-tenant installations are essentially unaffected; no public exploit identified at time of analysis, EPSS is 0.21% (10th percentile), and there is no CISA KEV listing. Our independent re-assessment scores this 7.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N) rather than the submitted 8.8, reflecting confirmed confidentiality exposure with more limited integrity impact and no availability impact.

Cross-organization tool metadata read and modification in SuperAGI v0.0.14 allows an authenticated attacker in one tenant to access or alter another tenant’s tool records through /tools/get/{tool_id} and /tools/update/{tool_id} because the tool controller fails to verify organization ownership via the associated toolkit. The issue only creates cross-tenant impact in multi-organization deployments; single-organization installations have no other tenant to target, and authentication is mandatory in the independent assessment even though the supplied CVE vector lists PR:N. EPSS is low (0.23%, 13th percentile), no public exploit was identified at time of analysis, and the independently assessed CVSS (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) indicates materially lower priority than the headline 9.8.

SuperAGI v0.0.14 contains an unauthenticated access control flaw that allows remote attackers to delete arbitrary knowledge objects via the POST /knowledges/delete/{knowledge_id} endpoint. The route lacks authentication and does not verify organization ownership, so any attacker who can reach the service and supply a valid knowledge_id can remove knowledge entries, impacting integrity only. No public exploit code or active exploitation has been identified, but the flaw is remotely exploitable without credentials, and instances exposed to untrusted networks are at risk.

Cross-tenant agent execution manipulation in SuperAGI up to v0.0.14 lets a remote authenticated user in one organization create or start execution records for agents owned by another organization through the /agentexecutions/add and /agentexecutions/add_run endpoints. Exploitation requires a multi-tenant deployment hosting more than one organization plus valid credentials in any one tenant, and the attacker must supply a caller-controlled agent_id-likely an enumerable sequential identifier-belonging to the victim organization. The independent assessment lowers the effective vector to authenticated (PR:L) with high integrity and low availability impact rather than unauthenticated 9.8; no public exploit has been identified, EPSS is low at 0.19% (8th percentile), and the main risk is cross-tenant integrity loss in agent execution records.

Cross-organization agent hijacking in SuperAGI 0.0.14 and earlier lets any authenticated user on a shared multi-tenant instance schedule and run agents owned by a different organization through the /api/agentexecutions/schedule endpoint, which accepts an agent_id but never verifies that the referenced agent belongs to the caller's organization. The result is high confidentiality and integrity impact (CVSS 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) with no availability impact, and an attacker only needs a valid low-privileged account plus knowledge or enumeration of a target agent_id - single-tenant or single-organization deployments have no other tenant to victimize and are effectively unaffected. Publicly available exploit code exists (SSVC Exploitation: poc) and no patch is documented, but EPSS is low at 0.16% (4th percentile) and there is no confirmed active exploitation or CISA KEV listing, making this a genuine second-tier risk rather than an emergency.

Unauthenticated access to Mooncake's HTTP metadata server (all versions through 0.3.13.post1) lets any network-reachable party read, overwrite, or delete transfer-engine metadata keys, allowing segment descriptors such as tcp_data_port to be poisoned or rpc_meta entries to be recreated so that KV cache transfers are redirected to attacker-controlled listeners, or server memory is exhausted. The flaw is a missing-authentication defect (CWE-306) on the /metadata handler and carries a CVSS 4.0 base score of 8.8 (assessed equivalently as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:H), meaning no credentials are required once the server is reachable on the network. Exploitation is therefore limited by network exposure rather than by attacker prerequisites, and no public exploit was identified at time of analysis and the issue is not listed in CISA KEV.

PictShare versions before 3.7.1 generate the per-file delete_code authorization token using PHP's non-cryptographic rand() PRNG, allowing an attacker who knows a hosted file's hash to predict or infer valid delete codes and delete other users' uploads without authorization. The vulnerability is remotely reachable and requires no authentication or user interaction (CVSS:4.0 AV:N/PR:N/UI:N), but exploitation is constrained by HIGH attack complexity (AC:H) because the attacker must reconstruct the PRNG state; the resulting impact is availability-only (VA:H) and grants no data disclosure. No public exploit code was identified at time of analysis and there is no CISA KEV listing; vendor-released patch: 3.7.1.

Hardcoded credentials in Teledyne FLIR Aware2 let unauthenticated attackers within radio or network adjacency (CVSS AV:A) bypass the software's access control and read or reconfigure affected PackBot (Aware2 through 6.9.0.2) and FirstLook (Aware2 through 1.7.9) robots. Because the passwords are embedded in firmware images and reproduced in product documentation, anyone holding a unit image or manual can obtain them without bespoke exploit tooling; no authentication (PR:N) and no user interaction (UI:N) are required, and the assessed scope change (S:C) reflects full compromise of the robot platform. No public exploit code has been identified at time of analysis, but the design-level flaw (CWE-798) means the credentials themselves are the attack vector, and Mandiant's disclosure (MNDT-2026-0031) frames this as a genuine high-priority issue rather than an inflated CVSS score.

Unauthenticated denial of service against Teledyne FLIR PackBot robots running the Aware2 web interface, where the reboot endpoint is exposed without any authentication control. Attackers who already hold a position on the local or adjacent network segment (CVSS AV:A) can trigger a robot reboot with no credentials (PR:N) and no user interaction (UI:N), disrupting operational availability of the platform. According to our independent assessment, this is a genuine but bounded operational-availability issue rather than a top-tier emergency: exposure is confined to field/operational networks rather than the open internet, impact is limited to denial of service with no data exposure or code execution, and no public exploit had been identified at the time of analysis (Mandiant disclosure MNDT-2026-0027; EUVD-2026-91048).

A write-protection bypass in the CANopen SDO server of RT-Labs AB C-Open (all versions before 1.1.1) allows any device on the same CAN bus to overwrite read-only Object Dictionary entries, corrupting protected configuration and process data on affected nodes. No authentication is required - the CANopen protocol has no built-in authentication (CVSS vector PR:N) - but the attacker must be able to send SDO frames to the target node's SDO server, meaning they need a presence on the same CAN segment; this adjacent-access requirement (AV:A) is the primary limiting factor. Impact is integrity-only (C:N/I:H/A:N): an attacker can point the data pointer at a read-only OD entry via an SDO upload for that entry, then send download-segment frames that the handler processes without verifying that a download session is active, overwriting the protected object in as few as two SDO frames. There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis.

Command execution and administrative-session bypass in TP-Link Tapo C120 v1 and C200 V5 cameras let an unauthenticated attacker on the same local network replay login challenge data, enable a privileged service that becomes reachable after reboot, and inject commands via the MacTool handler. The vendor reports a patch is available, and no public exploit code or CISA KEV active-exploitation entry was identified at time of analysis. Our independent assessment rates this as a credible, above-average-priority issue but not a drop-everything emergency because the attack requires same-LAN access, successful challenge replay, service activation, and a reboot.

Denial of service in TP-Link Tapo C120 v1 and C200 v5 cameras allows an unauthenticated attacker on an adjacent network segment to overwrite the device's wireless onboarding parameters and force it to join a different network, after which the camera becomes unreachable at its management address. The root cause is a missing-authentication condition (CWE-306) in the HTTPS onboarding 'do' method connect actions that persists after initial setup, so no credentials and no user interaction are required, although exploitation is limited to attackers on the same local or wireless segment and the outcome is availability-only with no confidentiality or integrity impact. No public exploit identified at time of analysis, and a vendor firmware update addressing the issue is available per TP-Link's advisory and download pages.

Unauthenticated remote attackers can pull the kickstart provisioning template from Red Hat Satellite 6's /unattended/provision endpoint without supplying any token, provided a host is currently mid-provisioning and therefore has an unexpired token recorded in the Satellite database. The flaw is a semantic logic error in Foreman's host_verifier.rb: valid_host_token? validates database state rather than the token presented in the HTTP request, so the check passes even when the request carries no token. Rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N), the exposure is gated by the provisioning window and yields information disclosure of the rendered template, not code execution; no public exploit code or active exploitation has been identified at time of analysis.

Authentication bypass in the mod_auth_digest module of Apache HTTP Server 2.4.x allows a man-in-the-middle attacker to capture a victim's HTTP Digest authentication credentials and replay them to impersonate that user against the server. Exploitation is conditional: the server must have mod_auth_digest enabled and the non-default directive AuthDigestNonceLifetime must be explicitly set to 0, and the attacker must additionally occupy a network interception position to capture the digest exchange and send crafted requests that force garbage collection of the client's shared-memory nonce entry. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) reflects high confidentiality impact but a high attack-complexity and MITM prerequisite; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the source supplied no CVSS score or EPSS estimate.

Forward proxy deployments of Apache HTTP Server through 2.4.68 that relay FTP traffic can be manipulated by an untrusted FTP server into opening a data connection to an arbitrary third-party host, because mod_proxy_ftp fails to validate the address returned in an FTP PASV reply. Only non-default configurations with forward proxying enabled (ProxyRequests On) and mod_proxy_ftp loaded are affected, and the primary impact is a misdirected outbound data connection rather than compromise of the proxy host itself. No KEV entry, EPSS score, or POC was supplied and no public exploit has been identified at time of analysis, so prioritization signals are limited and authentication requirements are not confirmed from the supplied data.

The Kernel Memory Access Driver (PSKMAD) shipped with WatchGuard endpoint security products fails to enforce its access-control handshake, so a local authenticated user who can open a handle to the driver can issue arbitrary privileged commands and read kernel and process memory (CWE-306). The issue is strictly local (AV:L, PR:L, UI:N) and requires the attacker to already hold a working account on a managed endpoint where the driver is loaded, making it a privilege-escalation and memory-disclosure primitive rather than a remote entry path. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; scope is assessed as changed (S:C) because driver-level compromise extends beyond the caller's security context.

Apache HTTP Server before 2.4.69 can be forced into repeated re-authentication by unauthenticated remote attackers sending forged Authorization headers when Digest authentication is enabled with the non-default AuthDigestNcCheck directive. Successful exploitation causes a limited availability impact, denial of service through forced re-authentication, without compromising data confidentiality or integrity. No public exploit code was identified at time of analysis, and the flaw is constrained to the uncommon Digest-auth-plus-AuthDigestNcCheck configuration.

Missing authorization checks in the Gratisfaction WordPress plugin (versions up to and including 4.6.3) allow authenticated Subscriber-level attackers to bypass access controls, potentially leading to high confidentiality impact and limited integrity/availability impact. The flaw is network-reachable with low complexity (CVSS 7.6 HIGH, PR:L) and requires only a low-privileged account, which may be obtainable via open registration on sites using the plugin. No public exploit code or active exploitation has been identified at time of analysis.

Broken access control in HCL iControl (CVSS 3.1 score 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) allows a low-privileged authenticated user to bypass authorization checks or manipulate object identifiers directly, resulting in privilege escalation and unauthorized modification or deletion of sensitive application data. Because the exploit requires a valid low-privilege account (PR:L), an unauthenticated external attacker cannot exploit this despite the 'Authentication Bypass' tag on the report, but any user with even minimal credentials can escalate to full confidentiality, integrity, and availability impact without user interaction. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; prioritization should focus on environments where low-privilege accounts are broadly provisioned or externally reachable.

Ghost 6.20.0 before 6.57.1 contains an improper session management flaw that allows an authenticated staff user who knows another staff member's password to log in as that staff user and bypass two-factor authentication. Successful exploitation can give the attacker the victim's administrative permissions, enabling unauthorized access to staff and admin functions. The issue requires valid staff credentials plus the target's password, so it is primarily an insider, credential-reuse, or post-phishing risk; no public exploit code was identified at time of analysis, and a vendor patch is available in 6.57.1.

Unauthenticated visitors can pull the full body of gated, members-only and paid-tier posts from Ghost 4.0.0 through 6.62.x by querying the platform's Content API directly, bypassing the membership restrictions that are supposed to withhold that content. The flaw is an authorization-checking failure (CWE-863) in post visibility filtering, scored 8.7 under CVSS 4.0 and assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - fully remote and unauthenticated, with high confidentiality impact and no integrity or availability effect. Impact is confined to sites that actually host gated content, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis; a vendor patch is available.

Suspended staff accounts in Ghost CMS can be reactivated through the self-service password reset flow, allowing a suspended user to restore their account and its original privileges in all versions before 6.62.0. The issue is an authenticated, post-login authorization gap rather than an anonymous takeover: the attacker must already hold valid credentials for a staff account that an administrator has suspended, which makes this primarily an insider, offboarding, or stolen-credential threat. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (CISA KEV), but the vendor-assigned CVSS 4.0 score of 8.7 and the independently assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8) reflect high confidentiality, integrity, and availability impact wherever account suspension is the sole remaining control.

Unauthenticated remote attackers can abuse the Stripe Checkout flow in Ghost CMS versions 5.2.0 through those prior to 6.62.0 to attach a paid subscription to an existing member account, change that member's stored name, and inject attacker-controlled markup into newsletters subsequently sent to that member. Depending on the recipient's email client, the injected content may render, degrading into HTML injection/content spoofing and, in clients that execute embedded script, cross-site scripting (XSS). Exploitation requires a Ghost instance with Stripe-backed paid memberships enabled and the newsletter feature in active use, plus a newsletter recipient opening the message (UI:P), so impact is conditional rather than immediate; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV).

Unauthenticated attackers can bypass authentication in Fleet (versions before 4.87.0) by using non-secret device identifiers like hostnames or hardware serials as tokens, allowing them to impersonate iOS/iPadOS hosts, read device data, and trigger device-scoped actions such as software installation and MDM migration. Exploitation requires knowledge of a valid identifier but no privileges or user interaction; no public exploit code has been identified at time of analysis. This is a high-priority vulnerability (CVSS 9.3) with a vendor patch available in version 4.87.0.

Authorization bypass in the n8n workflow automation platform lets an authenticated, low-privileged user exfiltrate project-scoped variables by supplying an arbitrary project ID to the credential test endpoint, which resolves those variables without validating that the caller may access the referenced project. The interpolated secrets are then embedded into the outbound credential test request, which the attacker directs at a host they control, turning a legitimate diagnostics feature into a data-exfiltration channel. All deployments on versions before 1.123.80, 2.0.0 through 2.39.5, and 2.40.0 are affected, with cross-project isolation loss being most consequential in multi-project or multi-tenant instances; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV.

n8n deployments running in queue mode can have arbitrary npm packages installed across every cluster worker by an attacker who holds write access to the deployment's Redis instance, bypassing package name validation, permission checks, checksum verification, and npm safety checks in the community-package installation handler. Affected builds are n8n before 1.123.80, 2.0.0 through 2.39.5, and 2.40.0; vendor fixes ship in 1.123.80, 2.39.6, and 2.40.1. No public exploit code has been identified at time of analysis, and practical risk is gated by the network-position prerequisite - the attacker must already be inside the Redis trust boundary - with single-instance 'main' mode deployments unaffected.

Unauthenticated attackers with network access to a ground-station instance running a version before 0.8.0 can achieve complete application takeover by invoking the setup.restore Socket.IO command while the server is in first-run setup mode. That command was whitelisted as an unauthenticated operation and passed attacker-supplied SQL straight to the application database, letting an attacker plant administrator accounts and forged session tokens and then authenticate as an administrator with no credentials. The flaw is critical severity (CVSS 9.3, CVSS 4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N) and is exploitable with no privileges and no user interaction; the practical prerequisite is that the instance must still be in its uninitialized first-run setup state, which makes freshly deployed, re-provisioned, or not-yet-configured servers the realistic targets. This is a pre-authentication total-compromise issue rather than an inflated score; a vendor patch is available in 0.8.0 and no public exploit code has been identified at time of analysis.

Unauthenticated container image tampering in oc-mirror, the mirroring utility shipped with Red Hat OpenShift Container Platform 4 and the Assisted Installer for Red Hat OpenShift Container Platform 2, lets any host on the same adjacent network segment push attacker-controlled images, delete cached images, or read mirrored content while a mirroring operation is running. The embedded local cache registry binds to all network interfaces (0.0.0.0) with neither authentication nor TLS, matching CWE-306, and carries a CVSS 3.1 score of 7.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N). No public exploit code has been identified at time of analysis, and the exposure window is transient because the vulnerable registry only exists during an active mirroring run.

MISP (Malware Information Sharing Platform) versions before v2.5.48 accept the same TOTP one-time code more than once, allowing a captured second-factor code to be replayed to open an additional authenticated session. The flaw is a CWE-294 capture-replay weakness: the login flow never recorded that a given TOTP time-step had already been consumed, so a code remained usable for its entire ~30-second validity window. Exploitation is conditional rather than drive-by - the targeted user must have TOTP enabled, the attacker must be able to observe or intercept the live code (network interception, shoulder surfing, or a compromised client) and in practice also hold the first-factor credentials, and the replay must land inside the same TOTP period; the vendor has released a fix in v2.5.48, and no public exploit code has been identified at time of analysis.

Unauthenticated attackers can obtain full WordPress session cookies - including for a Network Super Admin - on any Multisite installation running the Ultimate Multisite (WaaS/SaaS) plugin through version 2.15.0. The flaw lies in the publicly reachable wu_ajax_nopriv_wu_validate_form AJAX handler: supplying checkout_form=wu-finish-checkout discards all validation rules and forces is_last_step() to true, routing the request straight into order processing, where the attacker-supplied email_address is resolved to an existing WordPress user ID without ownership verification and login_customer_after_checkout() issues a passwordless wp_set_auth_cookie() for that user. Exploitation requires only a freely obtainable checkout nonce and the victim's email address (remote, unauthenticated, no user interaction per the CVSS vector PR:N/UI:N), but it succeeds only against accounts that have no pre-existing Ultimate Multisite customer record - such as a Network Super Admin on a fresh Multisite install or any administrator/editor created before the plugin was configured. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, though the 9.8 score and authentication-bypass-to-admin impact make this a high-priority patch.

Second-factor authentication bypass in MISP versions before 2.5.48 lets an attacker who already holds a session past the password step and a copy of the HOTP paper-token list replay a previously consumed HOTP token, because the OTP check compared the submitted token against a counter cached in the user's session rather than the authoritative database counter; the stale cached value still matches the burned token, yielding a second successful login and rewinding the counter state. Exploitation is not anonymous: it requires an authenticated session (PR:L per the assessed vector, implying prior password compromise), HOTP paper-token 2FA explicitly enabled on the target account, and knowledge of at least one valid token value, per the assessed CVSS:3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N (vendor CVSS 4.0 score 7.6, High). No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is fixed in MISP 2.5.48 by commit f34aee2c7.

The Comelit Multi-User Gateway for the VIP System (model 1456B) running firmware 2.9.1 or 2.10.0 exposes a network-reachable management interface that performs no authentication, allowing a remote attacker to read sensitive device configuration in cleartext - including the Remote Configuration Password. With CVSS 3.1 base 7.5 (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N), the exposure is fully remote, low-complexity and requires no credentials or user interaction; the only practical preconditions are network reachability to the interface and the device running an affected firmware build. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV); EPSS data was not provided, so no exploitation-probability estimate is available.

Missing authentication for a critical function in Hitachi Coding Software Suite (all versions through 3.3.0) allows a remote, unauthenticated attacker who can reach the exposed API to read or modify sensitive data and manipulate the affected system, with full loss of confidentiality, integrity, and availability. The flaw is a straight CWE-306 authentication gap on a critical API endpoint, scored 9.3 under CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:N with all three impact metrics rated High) and assessed independently at CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. No public exploit code has been identified and the issue is not listed in CISA KEV, so the practical risk is driven by network exposure rather than observed exploitation - the product is specialized industrial coding/marking software typically deployed on operational technology networks, which limits realistic internet-facing reach.

Authentication bypass in Hitachi Coding Software Suite through 3.3.0 lets remote, unauthenticated attackers forge JSON Web Tokens (JWTs) using a hard-coded signing secret and invoke administrative functions. The affected software exposes a JWT/Bearer-token-authenticated API; the only prerequisite beyond network reachability is extraction of the shared hard-coded secret from the distributed product, so no victim credentials, user interaction, or non-default configuration are required. No public exploit code has been identified at time of analysis, but the issue carries a CVSS 4.0 base score of 9.3 and can result in high confidentiality, integrity, and availability impact where the management/API endpoint is reachable; in typical OT deployments, network segmentation may be the main practical barrier.

Hard-coded credentials and undocumented hidden accounts in Hitachi Coding Software Suite (versions through 3.3.0) allow a remote attacker who possesses those credentials to bypass authentication entirely and obtain full read/write/execute-level control of the affected installation, matching the vendor's CVSS 4.0 rating of 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H). The only prerequisites are network reachability to the host plus knowledge of the embedded credentials, which is consistent with the independent CVSS 3.1 assessment of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. No public exploit code and no public disclosure of the specific credentials have been identified at time of analysis, and the issue is not confirmed actively exploited (CISA KEV); because these systems are industrial coding/marking control platforms often deployed on segmented OT networks, actual exposure depends on whether an attacker has a viable network path to the installation.

Multi-factor authentication bypass in Genian SSL PNS (Frodo-Core) lets an attacker who already holds valid first-factor credentials reach an authenticated session without completing the MFA step by manipulating a login request parameter, as the login handler fails to enforce authorization checks on that parameter (CWE-862). The vendor's CVSS 4.0 score is 7.3 (AV:N/AC:L/AT:P/PR:L/UI:N), while an independent assessment rates it CVSS 3.1 7.3 with a high attack complexity (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L), reflecting that the bypass requires a present attack-requirement condition and a working password or low-privilege account rather than being unauthenticated; no public exploit code has been identified at time of analysis, and no CISA KEV entry exists, so the practical risk is concentrated in organizations that actually operate Genian SSL PNS with MFA enforced.

Unauthenticated invocation of internal functions on the Genian NAC/ZTNA policy server's internal-only IPC SOAP endpoint allows a network-reachable attacker to manipulate protected data and degrade or shut down the service, scoring 9.3 (CVSS 4.0) and assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H. Affected builds are Genian NAC 5.0.75 LTS, 5.0.85 Stable and 5.0.86, and Genian ZTNA 6.0.35 LTS, 6.0.45 Stable and 6.0.46. Exploitation is gated almost entirely by network exposure: the endpoint is not reachable in properly segmented management planes, while flat networks or an internet-exposed policy server are directly exploitable - no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV) signal.

Authorization bypass in DeepTutor 1.4.0 allows an unauthenticated remote caller to enumerate bot identifiers and overwrite another user's whitelisted control files through the HTTP tutorbot file route, because TutorBotManager.write_bot_file trusts a user-supplied object identifier instead of verifying ownership. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no user interaction and no special conditions are needed beyond network reachability of the tutorbot endpoint; our independent assessment keeps integrity impact at High but reduces confidentiality impact to Low (C:L/I:H), whereas the published 9.1 score assumes full confidentiality loss. Publicly available exploit code exists (SSVC Exploitation: poc, with a public gist linked in the references), and SSVC rates the issue Automatable: yes with Technical Impact: total, although the EPSS score is only 0.15% (4th percentile) - consistent with a niche open-source project rather than widely deployed enterprise software.

Unauthenticated network attackers can reach the get_dataset entry point in RAGFlow 0.24.0's evaluation_app API and, depending on which entry is exposed, trigger attacker-controlled code or command execution as a result of a missing authorization check (CWE-284). The flaw scores CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting a worst-case path where no credentials and no user interaction are required, though exploitability is conditional on the evaluation_app interface being reachable by the attacker and on the specific exposed entry that enables execution. There is no public exploit identified at time of analysis and the EPSS score is low (0.32%, 22nd percentile); CISA KEV status is not indicated.

Unauthorized overwrites of persisted book metadata and spine content are possible in DeepTutor 1.4.0 because the book confirmation flow does not verify that the caller is authorized to act on the referenced book. An attacker who knows a valid, publicly exposed book_id can submit a confirm-proposal request remotely over the network to modify an existing book's stored metadata and spine, with no authentication, privileges, or user interaction required per the assessed vector (AV:N/AC:L/PR:N/UI:N). Impact is integrity-only per the assessed analysis (C:N/I:H/A:N), meaning data modification rather than data disclosure or system compromise; EPSS is low at 0.15% (4th percentile), no CISA KEV listing is present, and no public exploit code has been identified at time of analysis.

Incorrect access control in infiniflow RAGFlow 0.24.0 lets remote attackers reach the trace_mindmap path, supply a caller-chosen object or tenant identifier, and have that identifier flow into a data-access operation that enforces no owner, tenant, workspace, or membership binding - effectively an IDOR that exposes another tenant's RAG data. The vendor-agnostic description and the NVD-listed CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) conflict with our independent assessment, which carries the same network reachability and low complexity but scores it PR:L with confidentiality-only impact (C:H/I:N/A:N), and that discrepancy should be resolved before treating the flaw as unauthenticated pre-auth data compromise. CISA KEV does not list this CVE and EPSS is only 0.14% (3rd percentile), so confirmed active exploitation is absent; no public exploit code is identified at time of analysis, although the referenced GitHub gist is publicly accessible technical material that should be reviewed as a likely proof-of-concept.

Authentication bypass in Kiteworks Email Protection Gateway (versions before 9.5.0) lets unauthenticated remote attackers reach administrative functions simply by citing a valid administrator account identifier, without supplying the corresponding password or any token. Exploitation allows creation, modification, or deletion of internal users and managed domains and changes to security-feature configuration; deleting a managed domain also removes its user accounts and can lock legitimate administrators out of the gateway, consistent with the assessed vector's high integrity and availability impact and no confidentiality impact. The vendor has released fixed version 9.5.0, no public exploit code has been identified, and the vulnerability is not listed in CISA KEV at time of analysis; the main gating factor is that the attacker must know or guess an existing administrative account reference and be able to reach the administrative service over the network.

Improper authentication in Kiteworks Email Protection Gateway allows a remote, unauthenticated sender to make the gateway act against the Kiteworks platform as an identity it never verified, and to provision a new platform account for an identity the gateway does not already know - ultimately yielding control of a single platform account. Exploitation requires only network reachability to the gateway's message-processing path plus an inbound message asserting an identity; no credentials, privileges, or user interaction are involved (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). No public exploit identified at time of analysis, and there is no evidence of active exploitation or public tooling; the vendor's CVSS 3.1 score is 7.5 with integrity-only impact, while independent assessment raises the confidentiality component to High (C:H/I:H/A:N) because account takeover implies read access to that account's data, though the realistic blast radius remains a single platform account rather than the underlying appliance.

Privilege escalation in Kiteworks Core versions before 9.5.1 allows an authenticated delegated administrator holding only a single narrowly scoped administrative permission to obtain full system administrator privileges by abusing the administrative import function for integration credentials, which fails to verify that the requesting administrator is entitled to create the privileged credential being imported (CVE-2026-102132, CVSS 7.2 High). The attacker must already possess a valid delegated-admin account (PR:H), so this is an insider or lateral privilege-escalation issue rather than an unauthenticated internet-facing takeover, and no action by an existing system administrator is required for the escalation to succeed (UI:N). A vendor patch is available in Kiteworks Core 9.5.1; no public exploit code or confirmed active exploitation has been identified at time of analysis.

Unauthenticated file write in Kiteworks Email Protection Gateway lets any attacker who can reach the appliance's administrative upload endpoint push files containing attacker-controlled content onto the underlying filesystem, because that handler performs no authentication or authorization check (CWE-306, CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N). The directly reachable impact is integrity-only - no standalone code execution is achievable, since achieving RCE would require chaining a separate vulnerability to relocate the written file into an executable location. No public exploit code exists and no confirmed active exploitation was identified at time of analysis, so risk is genuine but bounded, concentrated on deployments that expose the management/upload interface to untrusted networks rather than those that firewall it to a management VLAN.

Unauthenticated access to an internal service function in the Kiteworks Advanced Forms / Secure Data Forms component allows remote attackers who can reach the exposed endpoint to invoke a limited set of backend service operations on the Kiteworks platform. The flaw requires no credentials and no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2) and is bounded by design: the vendor states the reachable function cannot access user accounts, stored files, or form submissions, and exploitation is impossible if the component is not network-exposed. No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS/KEV signals were not provided; overall this represents a moderate real-world risk concentrated on internet-facing Kiteworks deployments that have the Advanced Forms functionality enabled.

Improper certificate-assignment controls in Kiteworks Email Protection Gateway allow a remote, unauthenticated attacker to bind a certificate to another user's account, compromising the confidentiality and integrity of that account's encrypted mail. In deployments where certificate-based login is enabled, this can escalate to unauthorized account access; no public exploit was identified at time of analysis. The flaw maps to CWE-306 and carries a high assessed severity, though impact is bounded to encrypted-mail confidentiality and integrity unless certificate-based login is in use.

Remote, unauthenticated attackers who can reach an explicitly enabled OpenBSD ldapd instance can complete an LDAP Bind as another identity because delegated BSD authentication results are correlated only by the LDAP child process's client file descriptor and LDAP message ID. When a connection closes and a later connection reuses the same file descriptor and message ID, the earlier successful authentication result is delivered to the new connection, granting the attacker the other user's identity (CWE-863, incorrect authorization); the same code path also dereferences a missing connection and crashes the daemon for denial of service. Exploitation is gated by two prerequisites: ldapd must be manually enabled (it is not on by default) and configured to use delegated BSD authentication, and the identity takeover additionally requires winning a timing/resource-reuse race to land on the exact fd+message-ID pair, which is why both the CVSS 4.0 vector (AC:H/AT:P) and the independent CVSS 3.1 assessment (AC:H) rate the attack complexity as high despite PR:N. The defect is confirmed by an upstream OpenBSD source fix and errata 7.8/057 and 7.9/021; no public exploit code and no CISA KEV active-exploitation entry were identified at time of analysis.

Arbitrary command execution on Windows hosts is achievable through OpenClaw Windows Node versions prior to 2026.7.1, where the system.run exec-approval policy can be evaded by an authenticated connected gateway or agent holding the PR:L role. The ExecShellWrapperParser fails to split commands on pipe operators or extract command-substitution/subexpression syntax, so a denied command placed behind an allowed prefix (for example `benign | denied` or `echo $(denied)`) is never surfaced to the allow/deny ruleset and executes anyway; the failure only yields a bypass where a restrictive exec-approval policy is actually configured, and the impact is confined to Windows targets. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (no CISA KEV listing); vendor-released patch 2026.7.1 is available.