Authentication Bypass

Missing authorization controls in the ThemeAtelier Domain For Sale WordPress plugin before 3.5.2 expose unauthenticated REST API endpoints that disclose sensitive business data and permit destructive operations. Remote unauthenticated attackers can enumerate all stored offer records, harvest bidder contact information, verification tokens, and messages, and delete arbitrary offers by iterating numeric identifiers. No public exploit is identified at time of analysis, but SSVC marks this as automatable, meaning scripted mass scanning and exploitation across WordPress installations is technically feasible.

Authentication bypass in ESPHome Device Builder (the esphome-device-builder package powering the `dashboard` subcommand of the ghcr.io/esphome/esphome container) versions before 1.0.12 silently disables dashboard authentication on upgrade for operators who had protected it with the legacy bare $USERNAME/$PASSWORD environment variables. A rename to $ESPHOME_USERNAME/$ESPHOME_PASSWORD (PR #265) dropped the old names with no fallback, so `using_password` becomes false and both the REST auth middleware and WebSocket login gate switch off, leaving the dashboard open to anyone who can reach its port. Because a compromised dashboard caller can compile arbitrary code and read/write config and data directories, this is effectively unauthenticated RCE; publicly available exploit/PoC code exists, though it is not in CISA KEV (SSVC exploitation: none).

Missing authentication on Krayin CRM's admin mail ingest route lets any remote, unauthenticated attacker POST crafted RFC 2822 messages to /admin/mail/inbound-parse and plant arbitrary emails — including forged replies stitched into existing conversation threads — in victim CRM inboxes on every release through 2.2.6. VulnCheck reports proof-of-concept exploit code (SSVC Exploitation: PoC) and the attack is fully automatable, but the issue is not listed in CISA KEV, so active in-the-wild abuse is not confirmed; the CVSS v4.0 base score is 8.8, driven by high integrity impact with no confidentiality impact and only limited availability impact.

Casdoor through 4.4.0 exposes its instance-wide built-in JWT signing private key unmasked through the /api/get-certs and /api/get-cert endpoints, letting an authenticated organization administrator retrieve a key that should never leave the server. Because a single shared key signs tokens for the entire deployment, any one org admin can forge valid JWTs for arbitrary users in any organization - including global administrators - turning a tenant-scoped role into a full cross-tenant authentication bypass (CWE-863, improper authorization). Publicly available exploit code exists (a detailed write-up for finding 3 is linked, described as an incomplete fix of issue #3003), and VulnCheck rates the technical impact as total; EPSS is low at 0.21% (11th percentile), and the flaw is not confirmed as actively exploited. Exploitation requires a prior authenticated org-admin account and is not reachable anonymously.

A local unprivileged user can hijack the Control Interface of another workload in Eclipse Ankaios 0.1.0 through 1.0.2 by pre-creating the agent's predictable run-folder path hierarchy and Control Interface FIFOs under the shared default location `$TMPDIR/ankaios`. Because the agent reuses an existing directory or FIFO based only on an existence/file-type check — without verifying ownership or permissions — it treats the attacker-owned pipes as the legitimate Control Interface and executes requests under that workload's configured `controlInterfaceAccess` permissions, enabling workload impersonation and unauthorized reading or modification of the cluster's desired state. The flaw is CWE-379 (insecure temporary file/permissions), carries a CVSS 4.0 base score of 8.4 (AV:L/PR:L/AT:P, high confidentiality and integrity impact), and has no public exploit code or CISA KEV listing at time of analysis; EPSS is 0.09%, consistent with a local, non-automatable attack. The vendor released v1.0.3 with an ownership/permission validation check (PR #799).

Missing authorization in DotVVM's AuthorizeActionFilter causes any ASP.NET web application that relies on that filter to grant unauthenticated remote access to protected commands, view models, and presenters - the filter performs no check at all, so no bypass technique is required. All DotVVM releases before 4.2.11, the 4.3.0-preview01 through 4.3.15 range, and 5.0.0-preview01 through 5.0.0-preview09-final are affected; the vendor rates this critical (CVSS 4.0 base 9.2, independently assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H with high confidentiality, integrity, and availability impact). Exploitation applies only where AuthorizeActionFilter is actually wired up (CVSS 4.0 AT:P expresses that attack requirement), and no public exploit code and no confirmed active exploitation were identified at time of analysis, with EPSS at just 0.44% (37th percentile).

HTTP/1.1 request smuggling in http4s blaze allows a remote client to desynchronize message boundaries between blaze's hand-written Java wire parser and a fronting proxy, enabling front-end authorization bypass, response-queue poisoning on pooled backend connections, or cache poisoning. All deployments of blaze prior to 0.23.18, and the 1.0.0 milestone line from 1.0.0-M1 through 1.0.0-M41, are affected via five independent parser laxities that are reachable from a default BlazeServerBuilder with no non-default configuration. Exploitation is not confirmed in the wild and no public exploit code was identified at time of analysis; CISA SSVC records exploitation as none and automatable as no, and no EPSS score was supplied with the source data.

Alchemy CMS versions prior to 7.4.15, 8.0.15, 8.1.14, and 8.2.6 expose an unauthenticated API endpoint (GET /api/pages/nested) that returns the complete page tree without any authorization check, leaking restricted (member-only) and unpublished draft page metadata to anonymous callers. Appending the elements=true parameter causes PageTreeSerializer to additionally dump element and ingredient content from those restricted pages, fully bypassing the access control enforced by the sibling show and index actions. The vendor advisory includes working reproduction steps, and SSVC records that proof-of-concept exploitation is available and automatable, though no CISA KEV listing or EPSS score was supplied.

Improper access control in Cisco Secure Email and Web Manager could allow an attacker to bypass intended authorization on the management or administrative interface, with the published CVSS 9.8 vector claiming unauthenticated network exploitation and high confidentiality, integrity, and availability impact. The independent assessment is more measured: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, meaning low privileges are likely required and availability impact is not established, while the exact endpoint or configuration precondition is not documented by Cisco. Affected builds span the EUVD-listed 12.8.1-002 through 16.0.4-010 trains; no public exploit has been identified at time of analysis, EPSS is 0.46% (39th percentile), and CISA SSVC records exploitation as none.

PraisonAI deployments that opt out of authentication by setting PRAISONAI_CALL_AUTH=disabled expose the /api/v1/

Authentication bypass in PraisonAI's `recipe serve` command: when an operator selects `auth: api-key` or `auth: jwt` in a recipe YAML but omits the matching `api_key:`/`jwt_secret:` value and does not export PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET, APIKeyAuthMiddleware and JWTAuthMiddleware take a fail-open branch and forward every non-`/health` request unauthenticated to the recipe execution, input, and output surfaces, potentially triggering connected tools. Remote unauthenticated attackers who can reach an exposed recipe-serve endpoint (CVSS:3.1/AV:N/PR:N/UI:N) can therefore act as if authenticated, though independent analysis raises attack complexity to AC:H because the rawe 9.8 vendor score only manifests under a specific operator mis-deployment - the fail-open does not occur when the secret is set or when authentication was never enabled. Publicly available exploit code exists per the SSVC exploitation signal (poc), EPSS is 0.90% (58th percentile), and the issue is not listed in CISA KEV; it is fixed in 4.6.58.

Unauthenticated tool invocation and potential remote code execution in PraisonAI Agents (praisonaiagents) before 1.6.59, where the MCP SSE transport started by ToolsMCPServer.run_sse() or launch_tools_mcp_server(transport='sse') binds to 0.0.0.0 and builds its Starlette application with no authentication middleware and no Origin validation. Any client that can reach the listening port (default 8080) can list and invoke every registered tool without credentials, and because the bundled SecurityConfig, origin-validation and DNS-rebinding checks in mcp/mcp_security.py are never called, a malicious web page can rebind a hostname to 127.0.0.1 and drive the same JSON-RPC calls against a developer's local instance; the practical impact scales with the registered toolset and becomes full RCE where file, shell, or code-execution tools are exposed. Exposure is gated on an operator actually launching the SSE transport - merely importing the library is not sufficient - and no public exploit code has been identified at time of analysis (EPSS 0.47%, SSVC exploitation: none), with a vendor patch available in 1.6.59.

Improper input validation in Zscaler Client Connector for Android and ChromeOS (builds prior to 4.2.0.152) lets an attacker with elevated local privileges on the endpoint feed malformed input to the connector and bypass Zscaler's traffic inspection and access controls, with a CVSS 8.1 (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L) rating that reflects total loss of the security control's integrity. The flaw is not remotely exploitable and requires high privileges (root or equivalent device-admin context) on the affected Android or ChromeOS device, and there is no public exploit identified at time of analysis. EPSS is 0.12% (2nd percentile) and CISA SSVC records exploitation 'none', automatable 'no' with total technical impact — a low-likelihood, patch-promptly issue rather than an emergency.

Unauthenticated remote code execution in the PraisonAI multi-agent framework lets any network-reachable caller run arbitrary operating-system commands on servers exposing the Jobs API. The attack chains two defects: the POST /api/v1/runs endpoint ships without the verify_token dependency used by the authenticated agent_invoke endpoint (PR:N, no credentials or session required), and an attacker-supplied top-level 'approve' field in the submitted agent_yaml is loaded into a ContextVar that the @require_approval decorator consults before any risk-level check, so listing 'execute_command' makes the critical-tool approval gate a no-op with no operator interaction (CVSS 3.1 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-306). Affected releases are praisonai through 4.6.48 and praisonaiagents prior to 1.6.59, both fixed in 4.6.59 and 1.6.59 respectively; publicly available exploit code exists (a curl-based PoC is published in the GHSA advisory) and CISA's SSVC assessment rates the issue automatable with total technical impact, although no confirmed active exploitation (CISA KEV) has been reported and the current EPSS score is low at 0.41% (35th percentile).

SQL injection in the Alior Bank 'raty' PrestaShop module's toggleCategoryPromotionAction method allows an authenticated backoffice user with product or category edit privileges to inject arbitrary SQL via the unsanitized POST parameter 'status', which is passed directly into SQL UPDATE queries. Affected versions span two release branches: raty 9.0.5-9.0.7 and 8.1.9-8.1.11, with fixes available in 9.0.8 and 8.1.12 respectively. No public exploit code has been identified at time of analysis, and SSVC rates exploitation as none with the attack not automatable.

Authentication bypass in MISP's optional LdapAuth and LinOTPAuth plugins (versions ≤2.5.45) lets a remote unauthenticated attacker log in as any user whose email they know, without a password. Because LdapAuthenticate and LinOTPAuthenticate reimplement CakePHP's FormAuthenticate but omit its _checkFields() non-empty-string guard, an empty/null password reaches ldap_bind() and - per RFC 4513 §5.1.2 - is treated as an unauthenticated bind that many directories accept as success; impersonation grants the victim's full privileges, potentially administrative. There is no public exploit identified at time of analysis, and SSVC lists exploitation as none, but the technical impact is rated total.

LangBot's debug WebSocket server binds to all interfaces on port 5401 and ships with an empty authentication key by default - and the official Docker image together with its docker-compose configuration publish that port to the host, placing every default deployment within reach of any network attacker. A remote unauthenticated attacker who reaches the /plugin/ws endpoint can register an arbitrary debug plugin, after which LangBot broadcasts the full plaintext context of every inbound IM message event to that plugin, enabling mass interception of private chats, forged bot replies, LLM pipeline poisoning via malicious tool registration, knowledge-base enumeration, and persistent denial of service by blocking legitimate plugin installations with the prod_mode flag. No patched version was available at time of publication; SSVC classifies exploitation as proof-of-concept-available and fully automatable.

Symlink path traversal in File Browser ≤2.63.23 lets authenticated low-privilege users bypass configured deny rules to read and overwrite restricted files. The access-control engine evaluates rules against the lexically requested path but does not re-apply those rules after resolving symbolic links to their targets, creating a security boundary gap that is exploitable wherever an attacker can access an in-scope symlink pointing outside their permitted tree. A proof-of-concept exists per SSVC analysis; no public exploit code has been confirmed in CISA KEV at time of analysis.

Incorrect authorization in Apache Syncope (3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2) allows an authenticated principal that holds a search entitlement to retrieve identity and entity records outside its authorized realms by issuing a non-recursive search request. The Realms filter that normally constrains results to the requester's permissions can be rendered empty for non-recursive queries, effectively removing the privilege restriction before the search is translated into SQL, Neo4j, or Elasticsearch/OpenSearch queries; recursive searches are not affected. The exposure is backend-agnostic but gated by authentication and an existing search entitlement, so it is a data-confidentiality bypass rather than anonymous remote code execution - no public exploit code has been identified at time of analysis, EPSS is low (0.48%, ~40th percentile), and there is no CISA KEV listing. Vendor fixes are available in 4.0.8 and 4.1.3.

Broken delegated-administration authorization in Apache Syncope's Reconciliation service lets an authenticated administrator invoke pull and push operations without holding the required entitlements, because the entitlement checks on those endpoints are incomplete. The flaw affects Syncope 3.0.0-M0 through 3.0.16, 4.0.0-M0 through 4.0.7, and 4.1.0-M0 through 4.1.2, and is fixed in 4.0.8 and 4.1.3. There is no public exploit identified at time of analysis and SSVC records exploitation status as none, though CISA's framework rates the technical impact as total and the weakness as automatable.

Sensitive information disclosure in Hiperdino's REST v1.0 API lets a caller holding a valid static bearer token query the public 'customer/check' endpoint with a phone number or email and confirm whether it belongs to a registered customer, returning that customer's email and telephone. The endpoint enforces no per-user authentication beyond a shared static token, applies no rate limiting, and returns distinguishable responses, enabling bulk enumeration of contact details. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

Authentication bypass via ID Token claim spoofing in Ping Identity PingAM allows a remote attacker to inject or override protected ID Token claims through a well-crafted request. In vulnerable configurations this lets an attacker impersonate other identities or escalate privileges by forging trusted claims that downstream relying parties consume. Ping Identity has released a patch; no public exploit is identified at time of analysis, and CISA SSVC records exploitation status as none.

JWT privilege-spoofing in Apache Syncope allows an authenticated attacker to impersonate any other user if the internal JWKS configuration (at minimum the signing protocol and key) has been disclosed. The attacker must first complete a legitimate authentication and obtain a valid JWT, then leverage the disclosed JWKS material to forge tokens carrying another user's identity claims. No public exploit has been identified at time of analysis, and no CISA KEV listing exists, but the impact is complete horizontal and vertical privilege escalation within the identity governance platform.

Unauthenticated remote code execution in Maxim AI's Bifrost LLM gateway (transports v2.0.0 and earlier) allows any network caller to run arbitrary programs as the gateway process user. Bifrost's management API registers MCP stdio clients as a raw command-plus-args pair and launches that program immediately upon registration with no MCP handshake, and because governance.auth_config.is_enabled defaults to false, a single POST /api/mcp/client requires no credentials. A vendor patch exists (transports/v2.1.0), which refuses unauthenticated stdio registration with HTTP 403; no public exploit is identified at time of analysis, though the attack is trivially scriptable.

Apache Doris contains an incorrect authorization flaw (CWE-863) that lets an authenticated user bypass privilege checks and reach data or operations they should not be permitted to touch. Affected branches are 3.1.0 through 3.1.*, 4.0.0 through 4.0.7, and 4.1.0 through 4.1.3; the CVSS 3.1 vector of AV:N/AC:L/PR:L/UI:N with high confidentiality, integrity, and availability impact places this in the critical severity band. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, though the vendor describes the technical impact as total and CVSS 8.8 reflects broad read/write exposure within the cluster.

Missing authentication on a critical function in the Contec CPSL-08P1EN allows a network-reachable attacker to operate the device without supplying credentials. The flaw (CWE-306) means a protected management or control function is reachable directly over the network with no authentication gate, giving an adversary the same effective access as a legitimate administrator. No public exploit or CISA KEV listing exists at time of analysis, but the straightforward exploitation path (no complexity, no user interaction) lowers the bar for opportunistic targeting of Internet-exposed or weakly-segmented devices.

Unauthenticated permanent deletion of arbitrary WordPress content is possible in sites running the MDJM Event Management plugin (before 1.7.8.5) or Mobile Events Manager plugin (through 1.4.8.3). Both plugins expose a playlist entry removal endpoint that performs no capability check, nonce validation, or post-type verification before permanently deleting the post identified in the request, bypassing the WordPress trash mechanism. A publicly available proof-of-concept exploit reported by WPScan makes this trivially exploitable against any affected installation, with irreversible content destruction as the outcome.

Missing authorization on an AJAX endpoint in the CryptoPayment Gateway WordPress plugin (versions 1.2.1 through 1.2.2) lets remote unauthenticated attackers invoke administrative operations. An attacker can delete arbitrary files on the server, overwrite the payment gateway configuration, and read stored wallet credentials in cleartext. Publicly available exploit detail exists (reported by WPScan); there is no public evidence of active exploitation at time of analysis, though the CVSS vector (10.0, AV:N/AC:L/PR:N/UI:N/S:C) marks it as trivially exploitable.

The GenieWords WordPress plugin versions 1.5.27 through 1.5.34 allows unauthenticated attackers to overwrite plugin configuration via unprotected REST API and AJAX endpoints, then achieves persistent stored XSS on every front-end page because stored values are decoded and printed without sanitization. Any site visitor who loads a front-end page becomes an XSS victim, enabling session hijacking, credential theft, or malicious redirects at scale. A publicly available exploit exists (WPScan); no active exploitation is confirmed in CISA KEV at the time of analysis, but the unauthenticated attack path and low complexity make opportunistic mass-scanning feasible.

Authenticated Storm operator sessions are exposed to arbitrary web origin reads via three independent misconfigurations in Apache Storm Webapp 3.0.0: Logviewer CORS origin reflection combined with credentialed responses, a CORS filter initialization parameter mismatch that causes containers to silently apply permissive defaults, and unrestricted JSONP callback wrapping on all GET endpoints that bypasses the Same-Origin Policy entirely. Any malicious web page visited by an authenticated operator can silently exfiltrate cluster topology, configuration, and worker log data on the operator's behalf without requiring any additional privileges. No public exploit has been identified at time of analysis; vendor-released patch version 3.1.0 is available.

Rebalance operations in Apache Storm Nimbus 3.0.0 allow an authenticated attacker with topology rebalance rights to inject unauthorized blobstore map entries into configuration overrides, causing Supervisor nodes to fetch and locally cache blobs whose ACLs do not grant the caller access. A companion authorization-bypass in the listBlobs operation exposes the full blobstore key namespace to any caller reaching the Nimbus Thrift port without any subject check, supplying the key names that make the rebalance bypass actionable. No public exploit is identified at time of analysis; the vendor-confirmed fix is version 3.1.0 of org.apache.storm:storm-server.

Authorization bypass in Apache Storm Client 3.0.0 permits any authenticated Nimbus principal to perform unrestricted user-level cluster operations when access control is configured via `nimbus.groups` alone. The `SimpleACLAuthorizer` evaluates user-level commands by returning early with a grant when `nimbus.users` is empty, never reaching the group evaluation branch, so group restrictions are silently ignored. Operators who followed the documented `nimbus.groups`-only access control pattern in `docs/SECURITY.md` would believe their cluster was restricted while every authenticated credential held full permission to submit topologies, upload files, and retrieve Nimbus configuration. No public exploit code exists and no CISA KEV listing is present at time of analysis.

SSH key injection in Froxlor before 2.3.12 allows authenticated customers to write arbitrary lines into server-side authorized_keys files by embedding newline characters in SSH public key submissions to the SshKeys::add() API endpoint. An attacker with a valid customer account can plant SSH key entries bearing OpenSSH option directives (e.g., command=, from=, restrict) that persist beyond explicit key-deletion and access-revocation actions performed by administrators. No public exploit has been identified at time of analysis, but the vendor advisory confirms the flaw and the fix version.

Two-factor authentication bypass in the Really Simple Security WordPress plugin (versions before 9.8.1) allows an attacker who already holds a target account's password to eliminate that account's email 2FA requirement entirely and obtain the resulting session, up to administrator level. The root flaw is an unauthenticated endpoint that resets a completed email 2FA enrollment, collapsing multi-factor authentication to single-factor for the attack window. A publicly available exploit has been published via WPScan, and the vendor has released a fix in version 9.8.1.

Man-in-the-middle interception of protected ICS communications affects the ASE/Kalkitech ASE2000 V2 Communication Test Set versions 2.35 through 2.37 on Windows, whose IEC 60870-5-104 TLS client (Task Mode) improperly validates server certificates. A network-positioned attacker can present a certificate containing multiple simultaneous defects that the client accepts, defeating TLS authentication and exposing/altering traffic between the test set and a downstream RTU/IED. No public exploit code or CISA KEV listing is identified at time of analysis, and no EPSS score was provided; risk is elevated by the ICS/OT context rather than by evidence of active exploitation.

MCPHub's embedded OAuth 2.0 authorization server before v1.0.32 allows an attacker who intercepts a victim's authorization code to redeem it for valid access tokens without supplying a client secret or PKCE verifier. The root cause is a logic inversion in client authentication: the pre-fix condition checked `if (clientSecret && client.clientSecret)`, meaning that omitting the secret in a token request caused the entire secret-validation block to be skipped, even for confidential clients with a registered secret. Simultaneously, PKCE enforcement was absent for public clients, leaving no proof-of-possession check between code issuance and token exchange. Vendor-released patch v1.0.32 is available; no public exploit or CISA KEV listing has been identified at time of analysis.

Authentication bypass in the Frontegg SAML SSO WordPress plugin through version 1.0.1 lets unauthenticated remote attackers log in as any user, including administrators, because the plugin establishes a session from a SAML authentication response without verifying its cryptographic signature or issuer. Attackers can also create arbitrary accounts, giving them a persistent foothold. No public exploit identified at time of analysis; EPSS is low (0.19%, 8th percentile) but this reflects lack of observed activity, not difficulty of exploitation.

Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the repository commits API, which fails to confine paths and does not enforce authentication. All 18.7 releases through 19.3.2 are affected across the fix lines (before 19.1.8, 19.2.6, and 19.3.2). This is confirmed actively exploited (CISA KEV) and publicly available exploit code exists, making it an emergency-patch priority for any internet-reachable GitLab instance.

Privilege escalation in an ICS API routing component (ICSA-26-254-01) allows a low-privileged authenticated attacker to bypass role-based authorization by manipulating a client-controlled HTTP header that governs authentication-path selection. The routing layer directs requests to one of two authentication backends based on a header the attacker fully controls; by setting that header to invoke the alternate path, the attacker assumes a fixed, elevated role and can perform actions restricted to higher-privileged users. No public exploit is identified at time of analysis; the advisory originates from ICS-CERT, indicating deployment in operational technology environments where unauthorized privileged write access carries operational consequence beyond what CVSS scores alone convey.

Prototype pollution in the yayson npm JSON:API library (<= 4.2.0) lets a remote attacker corrupt Object.prototype by submitting a document whose resource type is "__proto__". Store/LegacyStore use the attacker-supplied type, id, and relationship names as plain-object keys in internal lookup tables, so a crafted JSON:API payload writes attacker-controlled key/value pairs onto every object in the Node.js process for its lifetime. Proof-of-concept code is published in the GitHub Security Advisory; there is no evidence of active exploitation. The guaranteed impact is process-wide denial of service and logic corruption, with escalation to authorization bypass or RCE dependent on gadgets in the consuming application.

Unauthenticated arbitrary SQL execution in the mysql-mcp-server (designcomputer) MCP server occurs when it runs in SSE/HTTP transport mode (MCP_TRANSPORT=sse), where SseServerTransport is created without security_settings, disabling the MCP Python SDK's DNS-rebinding (Origin/Host) validation, omitting CORS/TrustedHost middleware, and binding to 0.0.0.0 with no authentication on any route. Any network-reachable attacker can invoke the execute_sql tool to dump or modify the entire database, and where the MySQL account holds FILE privilege, achieve arbitrary file read/write and potential RCE via webshell drop. The vendor reports 25 publicly reachable SSE instances found via internet-wide scanning; no CISA KEV listing and no standalone published exploit, so this is best characterized as no public exploit identified at time of analysis despite detailed attack scenarios in the advisory.

Unauthenticated administrator account creation affects GetSimple CMS (v3.4.0a and earlier) and its community edition GetSimpleCMS-CE (v3.3.22 and earlier), where a self-exclusion bug in the post-installation cleanup logic leaves admin/setup.php reachable on production sites. Any remote attacker can invoke the still-present setup script to register a new administrator, yielding full control of the CMS. No patched version exists at publication and no public exploit has been identified, though the flaw is trivially reproducible from the advisory description.

Missing origin validation in wpa_supplicant's driver-based PMKSA cache selection path allows a local low-privileged attacker to bypass network context and AKMP matching, forcing the supplicant to use a cached Pairwise Master Key Security Association from a mismatched network or authentication method. All wpa_supplicant versions prior to 2.12 are affected. Successful exploitation can allow the attacker to bypass Wi-Fi authentication controls, potentially enabling connection to unintended network segments or interception of traffic through credential reuse across network boundaries. No public exploit code or CISA KEV listing has been identified at time of analysis.

Full account takeover in SPIP before 4.4.18 lets unauthenticated attackers reset the password of any user - including administrators - by invoking the editer_auteur administrative action directly over HTTP. The administrative action endpoints under ecrire/action/ accept a valid HMAC-SHA256 nonce as sufficient proof of authorization but never call autoriser() to verify server-side permissions, so an anonymous user can compute a valid nonce for any action. Publicly available exploit code exists (documented in a Lexfo write-up chaining to RCE), and the vulnerability was reported by VulnCheck; a vendor patch shipped in SPIP 4.4.18.

Full user impersonation in the Laci Synchroni sync server (backend prior to 1.2.3) lets an attacker take over any account by editing the client-side `UID` in their local config.json before login. The server's OAuth2 flow never verified that the authenticated OAuth2 identity actually owned the requested UID, so `AuthorizeOauthAsync` in SecretKeyAuthenticatorService would issue session tokens for an arbitrary target user. Publicly available fix code exists (PR #28, commit 5bc3efd); no known active exploitation and no EPSS/KEV signal was provided.

Hard-coded bootloader credentials in the ANJIA AJL33PC0801 IP camera allow any attacker with physical device access to authenticate to the bootloader without knowing a legitimate password. Successful exploitation grants full control over firmware loading and system configuration, enabling persistent device compromise, implant installation, or complete operational disruption. CISA issued ICS advisory ICSA-26-251-01 for this vulnerability; no public exploit or CISA KEV listing has been identified at time of analysis.

Cross-origin WebSocket hijacking in Headroom's proxy layer (prior to v0.35.0) allows an unauthenticated attacker-controlled webpage to issue arbitrary LLM requests through the victim's Headroom instance without authentication. Because the WebSocket server forwards requests to the upstream LLM provider without validating the Origin header, any browser with network access to the proxy-standard or headless-can be weaponized as a relay. The primary concrete impact is unauthorized consumption of the stored OpenAI API key and potential exposure of LLM response content; no public exploit code or CISA KEV listing has been identified at time of analysis.

Unauthenticated privilege escalation in Progress Chef Automate lets a remote actor bypass the API gateway's identity validation and reach protected Automate functionality without credentials. The flaw stems from missing authentication on a critical path (CWE-306), carries a maximum CVSS 10.0 rating with a scope change, and is documented in a Progress Critical Security Bulletin. No public exploit has been identified at time of analysis.

Unauthenticated file read in WWBN AVideo's getRecordedFile.php endpoint exposes recorded live-stream FLV files to any network attacker without authentication or authorization. All AVideo deployments through commit c3edcc274c389816d434acadac07ee78eaf330c1 are affected. An attacker who can reach the web interface and supply a known or guessed stream key can silently download private recorded video content, with no public exploit or KEV status confirmed at time of analysis.

Privilege escalation in Cloud Foundry UAA (User Account and Authentication server) lets users who authenticate via a federated OIDC provider obtain the powerful uaa.admin scope even though operators intended to restrict that provider using the externalGroupsWhitelist configuration. The flaw manifests only when an OIDC identity provider is configured with groupMappingMode: AS_SCOPES together with a wildcard (*) externalGroupsWhitelist entry, causing the wildcard to grant all mapped external groups as scopes - including uaa.admin. No public exploit has been identified at time of analysis, and the vulnerability requires a specific non-default IdP configuration.

WeenyGenius, a computer lab management system by Howyar Technologies, exposes its endpoint communication protocol without any authentication, allowing any adjacent-network attacker to impersonate either student or teacher roles. The teacher-impersonation path is the critical vector: posing as a teacher causes student workstations to initiate management connections back to the attacker, yielding remote control over every student endpoint in the lab. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the zero-privilege, zero-interaction requirement within a reachable network makes exploitation straightforward for any insider or network-adjacent threat actor.

Authentication bypass in the Advanced Customized Prompts WordPress plugin (versions through 1.0.1) lets an unauthenticated attacker obtain a valid authenticated session for any registered account by supplying only an email address, because an unauthenticated action issues the session without ever verifying the password. Attackers can log in as any user - including administrators - or create arbitrary new accounts, yielding full site takeover. Publicly available exploit code exists (reported by WPScan), though there is no public exploit identified as actively exploited in CISA KEV.

Authentication bypass in the Teddy Bear Customize Addon WordPress plugin (through version 1.0.5) lets unauthenticated attackers log in as any registered user - including administrators - by supplying only that user's email address, because the login routine never verifies the account password. WPScan reports a publicly available exploit, and with CVSS 9.8 (AV:N/AC:L/PR:N/UI:N) this is a trivially weaponizable full account-takeover; no active-exploitation (KEV) listing exists at this time.

Remote Code Inclusion in Brainzcompany Zenius EMS 8.0 (through OAM Build 109) is achievable by unauthenticated attackers on an adjacent network who bypass authentication via an alternate path or channel (CWE-288) compounded by improper syntactic input validation. The two-weakness combination allows an attacker to cause the server to include and execute attacker-controlled remote code, yielding full compromise of confidentiality, integrity, and availability. No public exploit code or CISA KEV listing has been identified at time of analysis.

Use of hardcoded default credentials in Xiongmai IP Camera XM530 firmware HMT.CM2005-v220608.1837 and earlier stores static account credentials in unencrypted plaintext within bin/config.xml and compiled into the Sofia executable, allowing remote attackers to gain full administrative control over the camera.

Authentication bypass in the Xiongmai XM530 IP camera firmware (HMT.CM2005-v220608.1837 and earlier) lets remote unauthenticated attackers execute privileged ONVIF actions - PTZ control, RTSP/stream URL retrieval, and system reboot - by sending a crafted SOAP request supplying the admin username with any arbitrary password whenever the account's stored password is empty. The flaw sits in the WS-Security (wsse:UsernameToken) verification routine of the Sofia IPC daemon, which fails to reject a token when no password is set. Publicly available exploit code exists (GitHub research repository); no public evidence of active in-the-wild exploitation at time of analysis.

CVE-2026-19816 is a vulnerability reported by Ubuntu with no public description, CVSS score, or CWE classification available at the time of analysis. The affected product is an Ubuntu package or system component, but the specific vulnerability class, attack vector, and impact cannot be determined from the available intelligence. No exploitation conditions, technical root cause, or patch details are derivable from current data.

Improper authentication in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote authenticated (low-privileged) attacker to read sensitive information and bypass security restrictions, crossing a privilege/scope boundary within the Cloud Pak for Data platform. The scope-changed CVSS 9.6 reflects that a low-privileged foothold can reach data and controls outside the attacker's authorized boundary; there is no availability impact. IBM has released a patch, but no public exploit has been identified and no EPSS or KEV signal is present in the provided data.

Remote code execution in IBM Langflow OSS 1.0.0 through 1.11.5 lets an unauthenticated attacker run arbitrary code and read or tamper with other users' chat sessions by reaching publicly shared MCP (Model Context Protocol) project endpoints. The flaw stems from Langflow failing to enforce its public-flow security restrictions and session-isolation controls, so exposure exists once a project is shared publicly via an MCP endpoint. No public exploit is identified in the provided data, and the item is not listed in CISA KEV.

Sensitive health-data exposure in the Lenovo Health Android application (distributed exclusively in the Chinese market) stems from hardcoded credentials (CWE-798) that let an attacker access users' health-related information without legitimate authentication. Reported by Lenovo PSIRT and tracked under a single Lenovo advisory, it carries a CVSS 4.0 base of 9.3 driven by high confidentiality impact. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.

Local privilege escalation in Lenovo Rescue and Smart Assistant (LMSA) enables a local authenticated user to execute arbitrary code with elevated privileges by exploiting a capture-and-replay authentication bypass (CWE-290) in the application's privileged service layer. The vulnerability is strictly local in scope per the CVSS 4.0 vector (AV:L/PR:L), limiting the threat to attackers who already hold a standard user account on an affected Lenovo device. Lenovo has published advisory LEN-217409 with remediation guidance; no public exploit has been identified at time of analysis.

IBM WebSphere Application Server 8.5 and 9.0 contain improper authentication controls that allow an attacker who already holds a local, low-privileged foothold on the server to bypass security checks and escalate privileges. Successful exploitation yields high confidentiality and integrity impact — protected resources and configuration can be read and modified — though availability is unaffected per the CVSS vector. No public exploit code has been identified, EPSS is very low at 0.12% (3rd percentile), the issue is not in CISA KEV, and a vendor patch is available from IBM.

Authentication/authorization bypass in rclone's dynamic serve interface (versions 1.70.0 through 1.75.0) lets remote attackers reach a fixed filesystem instead of the per-request backend the operator intended. When an FTP or S3 server is spun up via the serve/start RC (remote control) API with a per-server proxyOpt.AuthProxy, the FTP and S3 constructors mistakenly consult the empty process-global proxy.Opt.AuthProxy, so the request-local auth proxy is silently ignored: FTP accepts anonymous logins with any password against the fixed VFS, and S3 with AuthKey serves the fixed RC fs rather than the proxy-selected backend. There is no public exploit identified at time of analysis, and this is not in CISA KEV. Fixed in 1.75.1.

Authentication bypass in rclone's S3 server mode (rclone serve s3) allows any unauthenticated network attacker to impersonate arbitrary S3 access keys. When rclone serve s3 is started with --auth-proxy but without --auth-key, authPairMiddleware registers whatever accessKeyID the client chooses against an empty s3Secret, and gofakes3 then validates the request's SigV4 signature against that same empty secret - so an attacker can pick any access key, sign with an empty secret, and reach whatever backend the auth-proxy script resolves for that identity. Fixed in rclone 1.75.1; no public exploit identified at time of analysis, though the vendor security advisory (GHSA-xwwr-4h3p-r22c) and fix commit are public.

Arbitrary code execution in Dell ThinOS 10 (all builds prior to 2605_10.2616) allows a remote, unauthenticated attacker to run code within the application context of the affected thin client, per Dell advisory DSA-2026-389. The root cause is a protection mechanism failure (CWE-284) that bypasses an intended security control rather than exploiting a memory-corruption bug directly. No public exploit is identified at time of analysis and the CVE is not in CISA KEV, but the network-reachable, no-authentication attack profile makes it high priority.

HTTP/1 request-target parsing in Traefik prior to 2.11.57 and 3.7.13 allows unauthenticated remote attackers to send a rootless URL target (e.g., `http:example.com/admin`) that Go's HTTP library stores in URL.Opaque rather than URL.Path, leaving URL.Path empty. Traefik's routing engine, forwardAuth middleware, and access logger all evaluate against the normalized empty path (treated as `/`), while URL.RequestURI() gives URL.Opaque precedence when forwarding — meaning the backend receives the original opaque target verbatim. The practical consequence is cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion, all requiring no authentication or special client configuration. No public exploit has been identified at time of analysis, though the patch PR includes test cases demonstrating the attack technique in full detail.

Backend connection hijacking in Traefik reverse proxy (2.11.0 through 2.11.56 and 3.0.0 through 3.7.12) lets an unauthenticated remote client impersonate another user over HTTP/3. Because the HTTP/3 entrypoint never calls service.AddTransportOnContext, the kerberosRoundTripper falls back to a shared backend transport instead of one bound to each frontend connection, so when a backend uses connection-bound NTLM or Negotiate authentication with keep-alive, an unrelated client can reuse a backend connection already authenticated for a victim, read the victim's data, and act as the victim without ever obtaining their credentials. No public exploit is identified at time of analysis, though the fix PR ships a regression test that effectively demonstrates the flaw.

Traefik's header-security defenses (aliasHeadersStrategy, underscoreHeadersStrategy, forwardedHeaders) inspect req.Header but not req.Trailer, allowing unauthenticated clients on versions 3.2.0 through 3.7.12 to smuggle security-sensitive header values through HTTP/1.1 chunked trailers or HTTP/2 trailers. When retry or buffering middleware is active in the routing chain, attacker-controlled trailer values become accessible before the request is cloned for the backend; backends that merge trailers into their header namespace then receive the spoofed values, bypassing Traefik's documented delete or reject behavior. No public exploit code has been identified and this CVE is not in CISA KEV, but the impact on identity and routing integrity at the backend is classified high by the CVSS 4.0 subsequent-system metrics.

CyberPanel before 3.0.5 allows attackers who have obtained an administrator's password to bypass two-factor authentication entirely on API endpoints by deriving valid API tokens from the password alone, without satisfying the TOTP requirement. This reduces 2FA-protected admin accounts to effective single-factor authentication at the API layer, enabling full administrative operations or session creation. The fix is available in version 3.0.5 per the GitHub security advisory; no public exploit or active exploitation has been identified at time of analysis.

Authentication bypass in Traefik v3.7.0 through v3.7.11 lets remote unauthenticated attackers reach protected Kubernetes backends when an Ingress uses the ingress-nginx compatibility provider with both an authentication annotation and the nginx.ingress.kubernetes.io/from-to-www-redirect annotation. The provider generates a host-only 'sibling' router carrying only a non-terminal RedirectRegex middleware that still routes to the protected backend, so a crafted request evades the redirect and is proxied without any annotation-derived middleware. Reported by VulnCheck with a published advisory; no public exploit is identified at time of analysis, though the technique is fully documented and trivially reproducible.

Improper access control in Capgo (capgo.app) lets any holder of an ordinary full API key forge a trusted SSO provider by writing directly to the public.sso_providers table exposed via Supabase PostgREST, setting status='active' and enforce_sso=true without passing the backend provisioning route. This sidesteps the Enterprise-plan gate, Supabase Management API provider creation, DNS TXT domain-ownership verification, and the pending_verification→verified→active workflow, so an attacker can assert SSO enforcement for arbitrary unverified domains and disrupt normal login. All versions are affected, no patch was available at advisory time, and there is no public exploit identified at time of analysis beyond the VulnCheck write-up.

Capgo's MFA enforcement is defeated by an authentication assurance level (AAL) mismatch across two distinct code paths: the Edge JWT middleware (foundJWT() in supabase/functions/_backend/utils/hono_middleware.ts) accepts Supabase JWTs without inspecting the aal claim, and the direct RBAC path (checkPermissionPg() calling public.rbac_check_permission_direct() in rbac.ts) authorizes operations by user ID alone, bypassing the assurance-level check that public.verify_mfa() correctly enforces. An attacker holding only the victim's account password can authenticate, receive an aal1 JWT, exercise privileged RBAC operations without triggering any MFA challenge, mint a persistent app_admin API key, and modify production OTA channel configurations - all of which survive logout of the original aal1 session. No patched version has been released; all versions of capgo.app are affected, and the advisory includes a validated proof-of-concept demonstrating bundle swap on a production channel.

Improper authorization in Hikvision HikCentral Access Control V2.5.0 and below allows authenticated low-privilege users to invoke API endpoints restricted to higher-privileged roles, resulting in unauthorized access to sensitive data and limited system modification. The CVSS vector (PR:L, C:H, I:L) confirms the attacker requires only a valid low-privilege account but can achieve high confidentiality impact and limited integrity compromise across the network. No public exploit code or CISA KEV listing has been identified at time of analysis, though the straightforward nature of the authorization flaw (unenforced role checks on API routes) makes it readily exploitable by any insider or attacker who obtains basic credentials.

Unauthenticated remote control of GeoVision GV-LPC2211 license-plate-capture cameras (firmware V1.13) is possible because the PTZ control service is exposed on the network with no authentication (CWE-306). Any remote client that can reach the service can query PTZ state and, more critically, issue PTZ movement or raw serial commands to the device and its attached serial peripherals. CVSS is 9.4 and no public exploit has been identified at time of analysis, but the trivial network-reachable, unauthenticated nature makes exploitation straightforward.

Unauthenticated arbitrary WordPress option deletion in the zipMoney (Zip Co) Payments Plugin for WooCommerce before 2.4.0 lets remote attackers destroy site configuration and take the site offline. One front-end request handler performs no authorization checks and does not restrict which option name the caller supplies, so any unauthenticated visitor can delete critical wp_options entries. Publicly available exploit code exists and a vendor patch (2.4.0) is available; no active exploitation has been confirmed (not in CISA KEV).

Two-factor authentication bypass in the miniOrange 2FA WordPress plugin allows an attacker who has already obtained a victim's password to defeat the second factor through unlimited OTP brute-forcing. The plugin keys its attempt-rate limit to a client-controlled identifier rather than the target account, enabling an adversary to rotate that identifier and circumvent lockout entirely; a separate validation endpoint applies no rate limit at all. A publicly available exploit (WPScan) confirms practical exploitability against plugin versions below 6.3.1 and 19.3.

Unauthenticated arbitrary site-option deletion in the miniOrange 2FA WordPress plugin (versions 5.3.24 through before 6.3.1, and 18.0 through before 19.3) lets any visitor delete arbitrary wp_options entries because option names are taken directly from request input without validating a legitimate transaction. Deleting the right options can lock every administrator out of the WordPress dashboard or fully deactivate the two-factor plugin, stripping the site of its 2FA protection. Publicly available exploit code exists (WPScan) and a vendor patch is available; the flaw is rated CVSS 10.0.

Privilege escalation in the Bulk Password Reset WordPress plugin (all versions ≤1.3.3) allows any authenticated subscriber-level user to perform a full administrative account takeover. The plugin fails to validate the requesting user's identity before permitting bulk password changes and email-address updates, meaning an attacker can redirect an administrator's email to an attacker-controlled address, then invoke the standard WordPress password-reset flow to obtain reset credentials for that admin account. No public exploit code has been identified at time of analysis, but source code references from WordPress Plugin Trac directly expose the vulnerable functions at lines 44, 594, 659, and 679 of bulk_password_reset.php.

Pre-authentication queue deletion in Apache Artemis and Apache ActiveMQ Artemis allows unauthenticated remote attackers to destroy message queues by sending a crafted Openwire RemoveSubscriptionInfo command before or after the broker's authentication stage completes. The flaw affects every Apache ActiveMQ Artemis release from 1.0.0 through 2.44.0, and the rebranded Apache Artemis releases from 2.50.0 through 2.56.0, making it an extremely wide-scope exposure for the legacy version range. No public exploit code or CISA KEV listing has been identified at time of analysis, but the pre-authentication nature and low exploitation complexity make this a credible denial-of-service and data-loss vector in any internet- or intranet-exposed Artemis deployment.

Session hijacking in Apache ActiveMQ Artemis and Apache Artemis allows unauthenticated remote attackers to steal authenticated messaging sessions by sending a crafted CORE protocol SESSION_REATTACH packet, granting full control of an existing authenticated session without any credentials. The CORE protocol's session reattachment mechanism - designed for fault-tolerant HA reconnection - performs no identity verification, enabling any network-accessible attacker to impersonate legitimate connected clients. No public exploit or CISA KEV listing is identified at time of analysis, but the vulnerability spans the entire release history of Apache ActiveMQ Artemis (1.0.0 through 2.44.0), meaning essentially all historical deployments are affected.

Cluster credential exposure in Apache ActiveMQ Artemis and Apache Artemis allows a network-adjacent unauthenticated attacker to passively capture cluster administrative credentials during the initial peer-discovery handshake. Both the legacy Apache ActiveMQ Artemis lineage (versions 1.0.0 through 2.44.0) and the newer Apache Artemis distribution (versions 2.50.0 through 2.56.0) are affected, covering effectively the entire supported history of the project. An attacker positioned on the same network segment as a clustering deployment can intercept these credentials without any prior authentication, then use them to authenticate as a cluster administrator and gain full control over the message broker cluster. No public exploit code has been identified at the time of analysis.

Pre-authentication information disclosure in Apache ActiveMQ Artemis and Apache Artemis exposes cluster topology details to any unauthenticated remote attacker. The CORE protocol's SUBSCRIBE_TOPOLOGY request can be submitted before the broker enforces authentication, leaking cluster node configuration including internal broker addresses and cluster membership data. No public exploit code has been identified and it is not listed in CISA KEV, but the zero-prerequisite network vector makes automated scanning trivially feasible at scale.

Unauthenticated remote attackers can create arbitrary durable queues on Apache Artemis and Apache ActiveMQ Artemis brokers via the native CORE protocol due to missing authentication enforcement in the protocol handler. The vulnerability spans the entire Apache ActiveMQ Artemis release history (1.0.0 through 2.44.0) and the recently rebranded Apache Artemis fork (2.50.0 through 2.56.0), making the unpatched population potentially very large. Exploitation enables persistent unauthorized broker state manipulation and denial-of-service through storage and memory exhaustion, with no credentials or user interaction required; no public exploit code has been identified at time of analysis.

Unauthenticated LAN access to the ESPHome Device Builder dashboard on Home Assistant add-on deployments allows any device on the local network to gain host-equivalent control with no credentials. The ingress site, which deliberately skips authentication because the HA supervisor is supposed to authenticate upstream, was bound to 0.0.0.0 instead of loopback and the supervisor gateway. Because the add-on uses host networking for mDNS, this exposed the no-auth site on the host's LAN interface, directly bypassing the supervisor's authentication layer. An attacker with LAN access can run arbitrary Python via external_components at compile time, execute arbitrary shell through compile/validation subprocesses, and read or write arbitrary files in the config and data directories. No public exploit has been identified at time of analysis.

Unauthenticated remote task execution in @yeger/turbo-graph ≤ 2.8.8 allows any adjacent-network attacker to invoke arbitrary Turborepo tasks with the victim developer's OS-level privileges. Two independent implementation flaws combine: the embedded Next.js server omits the hostname argument to Node.js `.listen()`, causing the process to bind on all interfaces (`0.0.0.0`/`::`), while the `/api/run` HTTP endpoint reads task names from an attacker-controlled query string and passes them directly to `spawn()` with no authentication, CSRF protection, or allowlist check. No public exploit database entry or CISA KEV listing was identified, but a fully functional PoC with containerized end-to-end reproduction is included in the GitHub Security Advisory GHSA-2r5q-h53f-9rp3, significantly lowering the bar to exploitation.

OAuth and SCIM identity confusion in Open WebUI 0.6.41-0.10.x (SQLite-backed deployments only) allows unauthenticated remote attackers to hijack arbitrary stored user accounts, including administrator accounts, by presenting an OAuth subject claim containing SQL LIKE wildcard characters. SQLAlchemy's `JSON.contains()` on SQLite compiles to a substring LIKE match rather than an exact equality check, so a crafted `sub` claim such as `%admin%` can resolve to a different stored identity and cause the server to issue the attacker a valid session token for that identity. Vendor-released patch is available in version 0.11.1; no active exploitation has been confirmed.

Authentication bypass in MaxSite CMS versions 0.78 through 109.6 lets unauthenticated remote attackers forge valid administrator session cookies because the framework ships with a hardcoded session encryption key in application/config/config.php that installers never rotate. Using the publicly known key, an attacker computes a valid HMAC-SHA1 over a crafted ci_session cookie to impersonate an admin, defeating the is_login() and mso_check_allow() authorization checks. Publicly available exploit code exists (published by VulnCheck / EviL0rd); there is no evidence of active exploitation in CISA KEV at time of analysis.

Authentication bypass in SSSD's OIDC/IdP provider allows an authenticated IdP user whose subject identifier is a strict lexical prefix of a target user's identifier to impersonate that target user on SSSD-protected Linux systems. The root cause is `eval_access_token_buf()` passing the attacker-controlled identifier's length to `strncmp()`, reducing an identity equality check to a prefix test. All Red Hat Enterprise Linux releases (6-10) and OpenShift Container Platform 4 are affected when SSSD is configured to use an OIDC-based identity provider; no public exploit has been identified at time of analysis.

Unauthenticated firmware injection in Softish EarVision Android Application 1.3.1 paired with the C6 Ear Camera 1.3.1_Code 132 allows an adjacent attacker to deliver arbitrary, unsigned firmware to the physical ear camera device. By spoofing the C6 Ear Camera's wireless identity and eliciting a single user confirmation, the attacker triggers the application to transmit firmware over an update channel that performs neither endpoint authentication nor cryptographic signature verification (CWE-306). No public exploit code has been identified and the vulnerability is absent from the CISA KEV catalog; however, the adjacent-network vector and minimal social engineering threshold make exploitation realistic in clinical or close-proximity consumer settings.

Hardcoded or algorithmically derivable Wi-Fi credentials in the Softish C6 Ear Camera (firmware 1.3.1_Code 132) and companion EarVision Android application (1.3.1) allow an adjacent-network attacker to reconstruct the device's access-point password without authentication. Once the attacker connects to the camera's private Wi-Fi network, the live video stream, device management interfaces, status pages, and the firmware-update endpoint become fully accessible. The vulnerability was disclosed via CISA ICS-CERT advisory VA-26-251-01 and carries a CVSS 4.0 score of 8.7 reflecting high impact across confidentiality, integrity, and availability within the vulnerable system.