Authentication Bypass
Monthly
Account takeover in Authorizer's OAuth callback handler allows an unauthenticated attacker to pre-stage persistent backdoor access to any victim account by registering an unverified email address before the victim completes a routine OAuth login. The attack exploits a trust boundary violation in `internal/http_handlers/oauth_callback.go` (lines 125-219): the handler merges any incoming OAuth identity into the first database account matching by email, auto-verifies that account's email, and never invalidates the original password - leaving the attacker's credential fully active. No public exploit code has been independently confirmed, but the GHSA advisory contains a complete, line-referenced attack chain that makes independent reproduction trivial.
Authentication bypass in Roskus Prospero Flow CRM before 5.15.9 lets unauthenticated remote attackers log in as any employee onboarded through the standard HR flow using only that employee's email address. The employee save controller assigns a hard-coded fallback password of "changeme" (CWE-798) because the onboarding form exposes no password field, leaving newly created accounts with a universally known credential. No public exploit code or CISA KEV listing is identified at time of analysis, but the flaw is trivially reproducible from the public fix commit, and the CVSS 4.0 base score is 9.3 (Critical).
Unauthenticated firmware flashing in Netis NC63 routers (firmware V3.0.0.3327) allows any attacker on the same network segment to permanently compromise the device by uploading arbitrary firmware without credentials. Two compounding flaws enable this: the embedded Boa web server grants access to any URL path containing '.cgi' regardless of session cookie validity, and the netis.cgi CGI dispatcher reads but never enforces the authentication state before invoking the firmware update handler. Firmware images are accepted if they pass only a forgeable additive checksum and static product string checks - no cryptographic signature verification is performed. A public proof-of-concept exploit exists on GitHub (ozcanpng/CVE-2026-73673), and no vendor-released patch has been identified at time of analysis.
Cross-tenant payroll data exposure in Roskus Prospero Flow CRM before 5.15.10 enables authenticated users holding standard payroll permissions to read salary and banking details belonging to employees of entirely separate companies within the same multi-tenant instance, and to create payroll records attributed to those foreign employees. The flaw exists at the query layer: the payroll listing endpoint omits a company_id scope constraint, and payroll creation validates employee identifiers for global database existence rather than for membership in the caller's own company. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low exploitation barrier makes this an urgent priority for any multi-tenant deployment.
Authorization regression in Budibase v3.39.4 enables any authenticated BASIC user to generate S3 PutObject presigned URLs for arbitrary S3 buckets, bypassing the intended BUILDER-level permission gate on the attachment upload endpoint. The regression introduced in v3.39.4 - where the route guard was changed from `authorized(BUILDER)` to `authorized(PermissionType.TABLE, PermissionLevel.WRITE)` - gives all default BASIC users access to an endpoint that was explicitly restricted to builders. Compounding the issue, the endpoint accepts an attacker-controlled `bucket` parameter without validating it against the datasource's configured bucket, allowing writes to any S3 bucket reachable by the platform's stored IAM credentials. No public exploit tool exists at time of analysis, but the official GHSA advisory publishes complete reproduction steps and the test suite confirms the behavior, making exploitation trivial for any authenticated platform user.
Improper access control in File Browser before 2.63.20 allows authenticated users operating through proxy or hook authentication to escape their isolated directory scope and access the server root, exposing all other users' files for reading, modification, deletion, and sharing. The flaw specifically targets the createUserDir isolation mechanism, which is bypassed during auto-provisioning in proxy and hook authentication paths - leaving multi-tenant or shared File Browser deployments fully compromised at the data layer. No public exploit code has been identified at time of analysis, and CISA KEV listing is absent, but the CVSS 4.0 score of 8.7 reflects the high impact once a valid upstream credential is obtained.
Path canonicalization bypass in filebrowser before v2.63.21 permits authenticated users to circumvent administrator-configured deny rules by submitting case-variant or backslash-delimited path representations that the access rule engine fails to normalize before evaluation. The filesystem resolves these alternate representations to the same restricted objects, but the rules engine never matches them, effectively granting access to files the administrator explicitly intended to block. No public exploit code has been identified at time of analysis, though the attack concept is well-understood and straightforward to implement for any authenticated user of an affected deployment.
Privilege escalation in Grav's Flex Objects plugin (through version 1.4.6, confirmed against Grav 2.0.11) allows an authenticated low-privileged admin to achieve full site takeover by exploiting a missing authorization check in FlexApiController::update(). The generic /api/v1/flex-objects/user-accounts and /api/v1/flex-objects/user-groups API endpoints omit the field-level, target, and super-admin guards enforced by the dedicated Users and Groups controllers, so an account holding only api.access, admin.login, and users.update can overwrite a super administrator's password or self-grant admin.super group membership. No public exploit is identified at time of analysis; vendor-released patch Flex Objects 1.4.7 is available.
Privilege escalation in the getgrav/grav-plugin-api plugin before 1.0.13 allows an authenticated attacker holding only a minimal api.access-scoped key on a super account to mint a full-access, unscoped super key by exploiting missing scope-subset enforcement in createApiKey. The self-target path of requireApiKeyPermission() enforces only the baseline api.access scope, while the new key's scopes are taken verbatim from the attacker-controlled request body with no validation that they fall within the caller's granted scopes. Submitting an empty scopes array produces a key with unrestricted super privileges, directly enabling further attack chains including configuration-write-to-RCE. No public exploit code or CISA KEV listing is confirmed at time of analysis; EPSS is 0.30% (23rd percentile). Vendor-released patch version 1.0.13 is available.
Scope-cap bypass in grav-plugin-api before 1.0.13 allows a holder of a least-privilege api.config.write API key issued on a super-admin account to append arbitrary tokens to Grav's Twig sandbox allowlist (persisted to user/config/security.yaml) via the POST /reports/twig-content/allowlist endpoint. Widening the allowlist eliminates the Twig sandbox boundary, converting any subsequent content render into a server-side template injection (SSTI) sink and ultimately enabling remote code execution on the host. No public exploit has been confirmed and the CVE does not appear in CISA KEV at time of analysis, but the two-step primitive - allowlist poisoning followed by SSTI/RCE - is a well-understood attack class in CMS security research.
Server-side template injection (SSTI) leading to remote code execution in the Grav CMS API plugin (getgrav/grav-plugin-api) before version 1.0.13 is reachable by any low-privilege API key holder whose key was minted on a super-admin account. The root flaw is in PagesController::guardTwigContent(), which gates Twig processing via a bare isSuperAdmin() call that ignores the api_key_scopes array, allowing a key deliberately scoped to api.pages.write to enable process.twig on page save despite admin.pages_twig being intentionally excluded from that scope. A public proof-of-concept exists per SSVC data; exploitation is classified as automatable with total technical impact, making this a high-priority patch target for any Grav deployment where the required non-default configuration is active.
Force-disabling of two-factor authentication on Grav CMS user accounts is achievable through a missing scope enforcement check in the grav-plugin-api Composer package before version 1.0.13. Any holder of a low-privilege API key carrying api.users.write permission - or any scoped key on a super account - can POST to /api/v1/users/{user}/2fa/disable without supplying a TOTP code, stripping 2FA from any non-super target account and enabling direct account takeover. No active exploitation is currently confirmed (SSVC Exploitation: none; EPSS 0.34%), but SSVC rates this automatable with total technical impact, making prompt patching critical for any instance exposing the API with delegated keys.
Unauthorized disclosure of private content in SiYuan (siyuan-note) versions before v3.7.4 lets anonymous, unauthenticated clients subscribe to the WebSocket broadcast channel on the publish surface and receive real-time editing events for every document, including password-protected and explicitly forbidden ones. Reported by VulnCheck and documented in the vendor's GHSA advisory, the flaw is a missing authorization (CWE-862) check on broadcast sessions rather than a memory-corruption bug. No public exploit identified at time of analysis, but the trivial network-only access path and 9.2 CVSS 4.0 score make this a high-priority confidentiality issue for any exposed publish deployment.
Missing authentication on OpenChoreo's cluster-gateway (before 1.0.2 and 1.1.2) exposed caller-facing management APIs on the same externally reachable listener used for agent WebSocket traffic, letting network-reachable attackers hit /api/proxy/ and /api/exec/ without any credentials. In multi-cluster deployments this permits proxying the data-plane Kubernetes API and executing commands inside workload pods, effectively yielding cross-cluster control. No public exploit identified at time of analysis, but the GitHub Security Advisory (GHSA-qh9r-j7rp-4x2m) and CVSS 9.6 mark it as critical.
Authorization bypass in OpenChoreo's Kubernetes developer platform allows any authenticated user with a project-scoped grant to execute commands in and exfiltrate wirelogs from components belonging to entirely different projects within the same namespace. The root cause is that the `component:exec` and `wirelogs:view` API handlers in `exec.go` and `wirelogs.go` evaluate authorization using the attacker-controlled `project` query parameter rather than the authoritative `comp.Spec.Owner.ProjectName` field - a textbook CWE-639 insecure direct object reference. No public exploit or CISA KEV listing exists at time of analysis, but the CVSS 8.8 score and low-privilege network exploitation path make this a serious cross-tenant isolation failure in multi-project deployments.
Unauthenticated API access in OpenChoreo's Backstage backend exposes all `/api/*` routes to any network-reachable attacker, enabling catalog enumeration, scaffolder log reads, and catalog location creation or deletion without credentials. The root cause is two Backstage safety flags - `dangerouslyDisableDefaultAuthPolicy` and `dangerouslyAllowOutsideDevelopment` - hardcoded to `true` in both `app-config.yaml` and `app-config.production.yaml`, effectively disabling Backstage's authentication layer in all pre-fix deployments. No public exploit identified at time of analysis; vendor-released patches are available at v1.0.4, v1.1.4, and v1.2.1.
Command injection in FreePBX UCP Node server before 17.0.9 allows unauthenticated remote attackers to run arbitrary OS commands as the asterisk service user. The Socket.IO 4 middleware (io.use(checkAuth)) only guards the default namespace, so a client can reach unprotected custom namespaces and inject carriage-return/newline characters into Asterisk Manager Interface actions to execute commands. This is an authentication-bypass-plus-CRLF-injection chain; no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Authorization bypass (fail-open) in NextAuth.js (Auth.js) v5 affects applications on next-auth 5.0.0-beta.0 through 5.0.0-beta.31 that protect routes by checking only whether the auth() object exists. When Auth.js hits a server-side configuration error, the auth object is populated with a truthy error payload instead of null, so checks like !!auth or if (req.auth) evaluate true for every unauthenticated request. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the impact is a silent, total bypass of session-existence gates once a deployment becomes misconfigured. Fixed in 5.0.0-beta.32.
Account takeover in the Budibase low-code platform (prior to 3.39.30) lets an attacker impersonate any existing user by abusing OIDC SSO account-linking. Because the OIDC verify callback in oidc.ts resolved the email claim without ever reading email_verified, and sso.ts fell back to getGlobalUserByEmail as the linking key, a fresh attacker identity from a configured IdP asserting a victim's email - even as unverified - is silently merged into the victim's account, inheriting its _id and roles up to global admin/builder. No public exploit is identified at time of analysis, but the root cause is confirmed by the vendor GHSA advisory and the fixing commit; the issue carries a CVSS 4.0 base score of 9.0.
Tenant admin account takeover in Budibase self-hosted deployments before 3.40.0 is achievable by any authenticated user, including the lowest-privilege BASIC app user. The PUT /api/global/users/tenant/owner endpoint fails to enforce the cloudRestricted middleware on self-hosted instances where SELF_HOSTED or DISABLE_ACCOUNT_PORTAL is set, allowing any valid session to silently reassign the tenant owner email address to an attacker-controlled value. By then triggering the public password-reset flow against that address, the attacker achieves full administrative control over the entire Budibase tenant; no public exploit has been identified at time of analysis, but the single authenticated API call required makes the exploit chain mechanistically trivial for any user who holds even a basic account.
Hard-coded SSH credentials embedded in Tenda CH, CP, and TX3 camera firmware across versions V21.x through V27.x expose all affected devices to remote authentication bypass, granting shell-level access to any attacker who obtains the static password. A GitHub-published proof-of-concept documents the exact credential and exploitation steps, significantly collapsing the barrier imposed by the CVSS 4.0 AC:H rating. No vendor-released patch has been identified at time of analysis, and no CISA KEV listing has been issued, though the public exploit makes this a credible near-term threat for network-exposed devices.
FreePBX Framework's restore functionality allows an authenticated user with backup-restore privileges to inject the hidden AUTHTYPE=none configuration setting via a crafted backup archive, completely disabling web administration authentication on the affected PBX. Versions prior to 16.0.47 (branch 16) and 17.0.30 (branch 17) are confirmed affected; vendor patches have been released. No public exploit identified at time of analysis, though the fix commit diff publicly reveals the exact attack technique against a widely deployed telephony platform.
Unauthenticated remote code execution in AgenticSeek (commit fc242c7) lets any network-adjacent attacker run arbitrary OS commands by POSTing crafted queries to the /query API endpoint, which the autonomous agent turns into shell commands executed via BashInterpreter (subprocess.Popen with shell=True and safety=False). The endpoint listens on 0.0.0.0:7777 with wildcard CORS and no authentication, so a single crafted HTTP request yields full host-level command execution, and an incomplete command blocklist fails to contain it. Rated CVSS 4.0 9.3 (critical); no public exploit identified at time of analysis and not listed in CISA KEV, but exploitation is trivial once the port is reachable.
Account takeover in IBM Langflow OSS versions 1.0.0 through 1.9.6 is possible because the platform fails to limit repeated failed authentication attempts (CWE-307), letting remote attackers brute-force or credential-stuff their way into user accounts. IBM (the reporting vendor) rates it CVSS 9.1 with high confidentiality and integrity impact, reflecting full compromise of a targeted account. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the missing lockout control is trivial to abuse against weak or reused credentials.
Privilege escalation in IBM i versions 7.3 through 7.6 allows a local authenticated attacker to abuse improper authorization controls in the Navigator for i debugger component to access or manipulate sensitive system data, or create new profiles with elevated privileges. The vulnerability is classified under CWE-285 (Improper Authorization), indicating the debugger fails to enforce sufficient privilege checks before granting access to sensitive operations. No public exploit or CISA KEV listing exists at time of analysis, though SSVC assesses the technical impact as total should exploitation occur.
Supply chain compromise of Go module environments is possible when a malicious GOPROXY serves specifically crafted forged sumdb tile pairs, exploiting CWE-347 (improper cryptographic verification) in the cmd/go toolchain's tile-parent validation logic. Affected are cmd/go versions before 1.25.13, 1.26.6, and 1.27.0-rc.3 - any developer workstation or CI/CD pipeline using these versions and a non-default GOPROXY is at risk of silently caching attacker-controlled module content that cannot be distinguished from legitimate modules through normal transparency log evaluation. No public exploit has been identified and no CISA KEV listing exists; EPSS of 0.12% (3rd percentile) indicates low current exploitation probability, but the theoretical supply chain impact is severe.
Authentication token validation flaws in IBM i 7.3 through 7.6 expose network-reachable systems to remote unauthenticated attackers capable of extracting sensitive information and performing limited unauthorized operations. The CWE-287 root cause (Improper Authentication) combined with a PR:N/AV:N CVSS vector confirms exploitation requires no credentials and no user interaction over the network. No active exploitation has been confirmed (not in CISA KEV), EPSS sits at 0.31% (23rd percentile), and SSVC marks exploitation status as 'none' - signals that collectively moderate urgency despite the 8.2 CVSS score.
Improper authentication in IBM i (IBM's integrated midrange operating system, formerly OS/400) versions 7.3, 7.4, 7.5 and 7.6 allows a remote attacker to bypass authentication controls to execute arbitrary code or read sensitive data, provided a legitimate user is induced to interact (UI:R). IBM has published a fix (support node 7283292) and rates it 9.6 critical; there is no public exploit identified at time of analysis and it is not in CISA KEV, with a low EPSS score of 0.41% (34th percentile) indicating no observed mass exploitation yet.
Improper authentication in IBM i 7.3 through 7.6 enables remote unauthenticated attackers to bypass authentication controls over the network, yielding access to sensitive information with additional low-level integrity and availability impact per the CVSS vector. The vulnerability is classified under CWE-287 (Improper Authentication) and tagged as an authentication bypass, indicating the platform's authentication mechanism can be circumvented without credentials. No public exploit code has been identified at time of analysis, and IBM has released a patch via their support portal.
Cross-tenant authorization bypass in Trigger.dev before 4.5.6 lets a caller holding a valid API key for one project act on another project's deployment. Because CreateDeploymentBackgroundWorkerServiceV4.call() looks up the deployment by friendlyId with no environmentId/tenant predicate, an attacker can attach an attacker-controlled background worker to a victim project's deployment and force it from BUILDING to DEPLOYING. No public exploit identified at time of analysis; the flaw is an insecure-direct-object-reference (IDOR) affecting the deployments API.
Account takeover in Trigger.dev before 4.5.2 allows an unauthenticated remote attacker to hijack any existing user account that has not yet linked a Google OAuth identity, by presenting a Google profile whose email is unverified but matches the victim's registered address. The `addGoogleStrategy()` function in `apps/webapp/app/services/googleAuth.server.ts` omits the `email_verified` assertion before calling `findOrCreateGoogleUser()`, causing the server to bind the attacker's Google `authIdentifier` to the victim's account when the conditional `existingEmailUser && !existingUser` is satisfied. No public exploit has been identified at time of analysis, but the fix is available in v4.5.2 and the attack requires no Trigger.dev credentials.
Unauthorized access to privileged system objects is possible in IBM i 7.3 through 7.6 via a time-of-check to time-of-use (TOCTOU) race condition exploiting symbolic links, reachable by remote authenticated low-privilege users. The CVSS scope change (S:C) combined with full C/I/A impact signals that successful exploitation can reach objects and resources beyond the attacker's normal privilege boundary, effectively enabling privilege escalation across the OS. No public exploit code or CISA KEV listing has been identified at time of analysis, but the patch is available via the IBM advisory.
Path traversal in IBM i versions 7.3 through 7.6 enables a low-privileged remote authenticated attacker to bypass object-level access controls and gain unauthorized read, write, or disruptive access to arbitrary system objects. The CVSS 8.8 rating reflects full C/I/A impact across a network-accessible attack surface requiring only low privilege - consistent with IBM's own report as originating vendor and the EUVD advisory. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; EPSS at 0.36% (29th percentile) indicates low current exploitation activity, though a vendor patch is now confirmed available.
Authentication bypass in IBM i (OS/400) versions 7.3, 7.4, 7.5, and 7.6 allows a remote unauthenticated attacker to access server resources with the privileges of an authenticated user by exploiting improper authentication handling during NTLM session negotiation. The CVSS 3.1 base score is 9.8 (network vector, no privileges, no user interaction, total confidentiality/integrity/availability impact), though the EPSS exploitation probability is low (0.40%, 33rd percentile) and CISA's SSVC framework records exploitation status as 'none'. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in IBM WebSphere Application Server Liberty (versions 17.0.0.3 through 26.0.0.8) allows remote attackers to circumvent authentication controls when the rtcomm-1.0 or rtcommGateway-1.0 feature is enabled, exposing protected real-time communication functions. The CVSS 3.1 base score is 9.4 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:L), reflecting high confidentiality and integrity impact reachable over the network without credentials. A vendor patch is available; there is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
IBM Storage Scale GUI versions 5.2.3.0-5.2.3.8 and 6.0.0.0-6.0.1.0 ship with a hardcoded authentication token embedded in source code, granting any network-reachable attacker the ability to authenticate to the REST API and inter-node cluster communication channels without valid credentials. The static nature of the token means it is identical across every affected deployment, making a single disclosure universally exploitable against all unpatched instances. IBM has released a patch via advisory 7283308, and no public exploit or CISA KEV listing has been identified at time of analysis.
Privilege escalation in Kibana Fleet allows an authenticated low-privileged user to bypass integration-scoped authorization controls by exploiting a logic flaw in how policy update requests are validated (CWE-863). An operator holding only the Elastic Defend endpoint policy management role can craft a Fleet API update request that substitutes a different integration type into an existing endpoint policy they control, because Fleet evaluates the authorization check against the stored policy's original integration rather than the replacement integration supplied in the request. No public exploit code has been identified at time of analysis, but the vendor (Elastic) has issued advisory ESA-2026-127 with patched releases.
Cross-space authorization bypass in Kibana allows authenticated users to access trained machine learning model inference outputs, and stop or modify active model deployments, in Kibana Spaces they are not authorized to access. The vulnerability arises because API endpoints for ML model inference and deployment management accept user-controlled resource identifiers without enforcing space-level ACL boundaries, enabling privilege escalation across the Space isolation boundary. No public exploit code has been identified and Elastic has released fixed versions 8.19.20, 9.4.5, and 9.5.1 per advisory ESA-2026-126.
Incorrect authorization in Kibana Agent Builder allows authenticated users to access, modify, or delete private agents they do not own when sharing a username with another principal across different Elasticsearch authentication realms. The flaw stems from a fallback ownership check that compares usernames - which are not unique across realms - rather than stable user identifiers, enabling cross-realm identity confusion. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, but the low attack complexity and network accessibility make this a credible insider or multi-tenant threat.
Hard-coded credential exposure in the FL-100 transcranial brain stimulation device enables any attacker within Bluetooth range to bypass authentication entirely and manipulate neurostimulation parameters across every deployed unit simultaneously. The credential is universally shared across all FL-100 devices manufactured under both the Flow Neuroscience and Halo Neuroscience brands, meaning a single credential disclosure event compromises the entire installed base at once. No public exploit code has been identified at time of analysis and active exploitation is not confirmed by CISA KEV, but the zero-privilege, zero-complexity authentication bypass presents a credible patient safety risk in clinical and home-use therapeutic environments.
Missing Authorization in Kibana's Elastic Security module permits authenticated users holding detection rule authoring privileges to execute Osquery live queries and Elastic Defend response actions against enrolled managed endpoints without possessing the specific Osquery or Elastic Defend privileges that normally govern those capabilities. The CVSS 8.1 score reflects a network-accessible, low-complexity attack path with high confidentiality and integrity impact against enrolled host infrastructure. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, but patch versions 8.19.20 and 9.4.5 are available per Elastic Security Advisory ESA-2026-96.
Kibana's Machine Learning subsystem fails to enforce space-level authorization, allowing any authenticated low-privilege user in one Kibana space to read ML data from all other spaces and make unauthorized modifications across the entire deployment. The root cause is that ML operations execute with elevated internal Elasticsearch permissions while a subset of ML functionality omitted the per-request space isolation filter that enforces tenancy boundaries. No public exploit has been identified, but the attack requires only a standard user account, making it a realistic internal threat in multi-tenant or shared Kibana deployments. Fixed versions 8.19.20 and 9.4.5 are referenced in the Elastic security advisory ESA-2026-92.
Elastic Kibana's Elastic Security endpoint policy editor exposes sensitive Elastic Defend telemetry through a privilege escalation in the field value suggestion feature. Authenticated users holding Kibana Elastic Security feature privileges - but lacking Elasticsearch index-level read access to Elastic Defend event indices - can retrieve field values including process command line arguments, which routinely contain credentials, API tokens, and connection strings harvested from protected endpoints. No public exploit has been identified at time of analysis, but the low attack complexity and scope change across the Kibana-to-Elasticsearch authorization boundary make this straightforward to abuse by any user with a qualifying Kibana role.
Missing authorization on Kibana's Observability Onboarding API routes allows any authenticated low-privilege user sharing a Kibana space to enumerate, read, and overwrite the onboarding flow state of other users in that space. Affected installations include all Kibana versions prior to 8.19.19 and 9.4.5 across both self-managed and Elastic Cloud deployments. No public exploit code has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog; however, the CVSS high integrity impact (I:H) reflects an attacker's ability to corrupt another user's onboarding progress and trigger persistent server errors in the victim's Observability Onboarding view.
Authentication bypass in IBM i (the operating system for IBM Power/AS-400 midrange systems) versions 7.3, 7.4, 7.5, and 7.6 allows remote attackers to circumvent security restrictions because the system improperly validates a client-asserted identity (CWE-287). Because a caller's claimed identity is trusted without adequate verification, an attacker can impersonate another principal and gain unauthorized access to protected resources with full confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis, and the EPSS probability is low (0.34%, 27th percentile), but the CVSS 9.8 rating and network-reachable, unauthenticated vector make this a high-priority patch.
Authorization bypass in Open Identity Platform OpenDJ before 5.1.2 lets any authenticated account holding the proxied-auth privilege impersonate arbitrary non-root directory users during a SASL PLAIN bind. The PlainSASLMechanismHandler validated only the PROXIED_AUTH privilege but skipped the mayProxy ACI scope check, so the proxy ACIs meant to constrain which identities may be assumed were not enforced (CVSS 9.6). No public exploit has been identified at time of analysis, but the flaw is confirmed by the vendor GHSA advisory and fixed in 5.1.2.
Cross-enterprise IDOR in Rainbond through 6.9.7 allows any authenticated user to read or modify another enterprise's resources by substituting an arbitrary tenant name in API URL paths. The CheckToken function validates token authenticity but never cross-checks that the token's enterprise matches the enterprise embedded in the request path, enabling horizontal privilege escalation across tenant boundaries. Impacted resources include services, plugins, environment variables, and TLS certificates belonging to any enterprise on the same Rainbond instance. No public exploit code or CISA KEV listing has been identified at time of analysis.
Broken authorization in vantage6's algorithm store allows any authenticated algorithm developer to overwrite a peer's pending algorithm metadata - including the Docker image reference or tag - before that submission is approved by reviewers. Versions 5.0.2 and earlier of this pip-installable federated analytics platform are affected, with no patch available. The practical consequence is a supply-chain integrity failure: nodes and reviewers may trust and execute a container image entirely different from the one originally submitted for review, with no visible indication that a substitution occurred.
Unauthenticated remote root compromise affects CyberPanel before 3.0.0 through a hard-coded JWT signing secret in the WebTerminal FastAPI SSH service. Because the secret is baked into the code, an attacker can mint a valid token specifying ssh_user=root and connect to the WebSocket terminal on TCP 8888 with no credentials, receiving a fully interactive root shell. No public exploit identified at time of analysis, but the trivial exploitation path (known secret, single forged token) makes reliable weaponization straightforward for any actor who reads the source.
Server-side request forgery in Gitea Open Source Git Server (all versions through 1.26.4) lets attackers abuse the repository migration and mirror features to reach internal network resources. Two distinct weaknesses are involved: a DNS-rebinding bypass where a hostname resolves to a permitted address during validation and to an internal address when the actual request is made, and a missing re-validation flaw where redirect or subsequent fetch targets are not re-checked against the allow/deny policy. No public exploit was identified at time of analysis, EPSS is low (0.15%), and it is not in CISA KEV, but the vendor rates technical impact as total and the issue is fixed in 1.27.0.
Broken access control in Gitea (self-hosted Git service) versions up to and including 1.26.4 lets the team-repository linking endpoint ignore the RepoAdminChangeTeamAccess organization setting, so repository administrators can grant or alter team access to repositories even when an org owner has explicitly restricted that ability. This CWE-862 missing-authorization flaw undermines an intended org-level guardrail, exposing private repository contents (C:H) and permitting unauthorized permission changes (I:H). No public exploit has been identified at time of analysis, and the EPSS probability is low (0.15%, 5th percentile).
Unauthorized cross-tenant cluster takeover in Red Hat Multicluster Engine (MCE) for Kubernetes allows an authenticated tenant to force a managed cluster into another tenant's ManagedClusterSet by manipulating ClusterClaim labels. The clusterclaims-controller processes these label changes without enforcing tenant ownership boundaries, enabling the attacker to then inject policies and workloads into clusters they do not own. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope-changing nature (S:C) and high confidentiality impact make this a serious multi-tenancy isolation failure.
Lenovo System Update contains an authentication bypass (CWE-290) that permits a locally authenticated standard user to circumvent privilege checks and execute arbitrary code with elevated system privileges. Affected products span all tracked versions per CPE data, with Lenovo confirming the issue and releasing a patch under advisory LEN-213316. No public exploit code or CISA KEV listing has been identified at time of analysis, limiting immediate threat to environments where adversaries already have local user access.
Access control bypass in rsync daemon versions 3.1.0 through 3.4.4 lets remote unauthenticated attackers evade module-level 'hosts deny' restrictions by forcing DNS resolution to fail during hostname-based access checks, causing the daemon to skip the rule (fail-open) instead of denying. Reported by VulnCheck and fixed in rsync 3.5.0, it exposes file trees in modules that were meant to be IP/hostname-restricted; no public exploit has been identified at time of analysis and it is not listed in CISA KEV.
Authorization bypass in rsync 3.1.0 through 3.4.x allows authenticated users to circumvent module-level access controls when group-based deny rules are configured with space-containing group names. The auth users directive's comma-only parser silently discards deny rules for any @Group Name entry whose group name contains a space, granting unintended access to restricted rsync modules regardless of the administrator's intended group-based exclusions. The rsync project designated v3.5.0 a major security release to address this flaw; no CISA KEV listing or public exploit code has been identified at time of analysis.
Arbitrary file write in rsync before 3.5.0 allows attackers who control --temp-dir or --link-dest option values to escape the intended destination tree by supplying absolute paths, bypassing the rename-confinement security boundary. Any filesystem location writable by the rsync process can be targeted, enabling overwrite of system files, configuration, or planted malicious content. No public exploit identified at time of analysis, but the CVSS 4.0 score of 7.2 with high integrity and availability impact reflects serious real-world risk in server environments where option values are externally influenced.
Path confinement bypass in the rsync daemon (versions before 3.5.0) lets remote clients escape the intended per-module chroot root when a module path contains a '/./' boundary marker, granting unauthorized read or write access to files outside the module subtree. Reported by VulnCheck and carrying a CVSS 4.0 score of 9.1, the flaw is exploitable by mishandling the '/./' notation or by forging delta-basis (xname) transfers that cross the boundary. No public exploit has been identified at time of analysis, but the fix is a coordinated advisory (GHSA-wj7w-vh23-mm44) shipped in the major 3.5.0 security release.
IP-based access control bypass in the rsync daemon (rsyncproject/rsync) before version 3.5.0 lets unauthenticated remote attackers forge their source address by injecting a crafted PROXY protocol header, defeating hosts allow/deny restrictions. Reported by VulnCheck and fixed in the v3.5.0 major security release, the flaw applies to daemons that trust PROXY protocol headers yet accept direct client connections. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS 4.0 base score of 9.1 reflects high confidentiality and integrity impact once the IP allowlist is circumvented.
Bluetooth LE legacy pairing authentication in Silicon Labs RS9116W and SiWx917 wireless modules (WiseConnect SDK) can be bypassed by manipulating the Temporary Key (TK) value during Passkey Entry association, allowing an adjacent unauthenticated attacker to pair with the target device without possessing the correct passkey. Successful exploitation yields high confidentiality and integrity impact on the vulnerable system. The vulnerability is academically documented as B-E3 in a published research paper (arxiv.org/pdf/2409.02905); no public exploit tool or CISA KEV entry has been identified at time of analysis.
Bluetooth Low Energy re-pairing in Silicon Labs RS9116W and SiWx91x devices allows a nearby unauthenticated attacker to negotiate a lower security level during the re-pairing process with an already-bonded peer, effectively bypassing the previously established security guarantees. Documented as the 'V3' attack variant in the NDSS-published BLERP (BLE Re-Pairing) research paper, this flaw enables high-impact compromise of confidentiality, integrity, and availability across affected WiseConnect firmware lines. No public exploit code or CISA KEV listing is confirmed at time of analysis, though the NDSS publication constitutes academic proof-of-concept disclosure.
BLE re-pairing attacks against Silicon Labs RS9116W and SiWx917 modules allow an adjacent unauthenticated attacker to spoof a previously bonded device and force the target to re-bond with a rogue device, yielding full BLE session control. Both WiseConnect SDK 2.x (before 2.14.0) and 4.x (before 4.1.0) are confirmed affected per vendor release notes and the academic BLERP (BLE Re-Pairing Attacks and Defenses) paper published at NDSS. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog, though the NDSS paper provides a detailed methodology that could guide motivated researchers to weaponize the technique.
Cross-tenant IDOR in Roskus Prospero Flow CRM before 5.4.7 allows any authenticated user to read sensitive product records belonging to other tenant companies and reassign those products into their own account. Two compounding root causes drive the impact: ProductUpdateController lacked the MainController inheritance that enforces session-based authorization, leaving the product read endpoint unguarded, while ProductRepository::save() performed a bare Product::find($data['id']) lookup with no company_id scope constraint, enabling cross-tenant record hijacking. No public exploit or CISA KEV listing exists at time of analysis, but the exploit conditions are trivially met by any authenticated session holder.
SQL injection in Pimcore's Block.php field loader, affecting versions 2026.1.0–2026.1.4 and all releases below 12.3.9, enables an authenticated editor-level user to exfiltrate arbitrary database content including password hashes via UNION-based injection. The vulnerability chains two incomplete fixes: a missing trailing `$` anchor in ClassDefinition.php regex validation permits malicious UIDs to pass input checks, and six unquoted `getClassId()` concatenations in Block.php execute the injected SQL when any data object of the malicious class is loaded. A working proof-of-concept is publicly documented in GitHub Security Advisory GHSA-2mhj-fhvg-v428, and vendor-released patches (2026.1.5 and 12.3.9) address both weaknesses.
Unauthenticated broken access control in the Arvow AI SEO Writer WordPress plugin (versions ≤ 1.5.3) exposes unprotected endpoints that allow remote unauthenticated attackers to perform privileged write-level operations due to missing authorization checks (CWE-862). The CVSS 3.1 vector (PR:N/I:H) confirms no authentication is required and integrity impact is high, indicating attackers can modify SEO configuration, inject content, or alter plugin-managed data without any credentials. No active exploitation has been confirmed via CISA KEV, and no public proof-of-concept has been identified at time of analysis.
Broken access control in the StoreGrowth: Smart Sales Booster for WooCommerce plugin (versions <= 2.1.1) permits unauthenticated remote attackers to bypass authorization checks and perform privileged store management actions. The root cause is a missing authorization gate (CWE-862), meaning certain plugin endpoints execute sensitive operations without verifying the caller's identity or permissions. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the zero-friction exploitation conditions - no authentication, no user interaction, network-accessible - make this a straightforward target for opportunistic scanning.
Unauthenticated payment bypass in SMEPay: UPI Gateway for WooCommerce plugin (versions <= 1.0.5) allows remote attackers to complete WooCommerce orders without valid UPI payment by exploiting missing authorization controls. The plugin fails to enforce access checks on payment-related endpoints, enabling an unauthenticated network attacker to manipulate transaction state with no user interaction required. No public exploit or CISA KEV listing has been identified at time of analysis, but the network-accessible, zero-authentication attack surface makes this trivially abusable on any exposed WooCommerce storefront running the affected plugin.
Unauthenticated broken access control in the MultiVendorX WordPress plugin (versions 5.0.10 and earlier) exposes restricted marketplace data to any remote attacker without credentials. The flaw stems from missing authorization checks (CWE-862) on one or more plugin endpoints, allowing unauthenticated network requests to bypass access restrictions and retrieve sensitive information such as vendor orders, customer data, or marketplace configurations. No public exploit or CISA KEV listing has been identified at time of analysis, but the low attack complexity and zero-authentication requirement make this a straightforward target for opportunistic scanning.
Broken access control in Bitcoin Lightning Payment Gateway for WooCommerce (via CLINK) versions 1.0.7 and below exposes one or more plugin endpoints - almost certainly WordPress AJAX handlers or REST API routes - without the required capability checks, allowing unauthenticated remote attackers to perform privileged actions with high integrity impact. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) confirms no credentials are needed and exploitation requires no user interaction, making this trivially scriptable against any internet-facing WordPress store running the affected plugin. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis, though the attack conditions are permissive enough to make opportunistic exploitation straightforward.
WPMobile.App plugin for WordPress, versions 11.77 and earlier, allows unauthenticated remote attackers to bypass authorization controls and access protected resources. The CVSS 7.5 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) reflects full network exploitability with high confidentiality impact and no integrity or availability consequence, consistent with an unauthorized read-access scenario. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.
Unauthenticated broken access control in the Hydra Booking WordPress plugin by Themefic (versions ≤ 1.2.2) permits any remote, unauthenticated party to bypass authorization checks and interact with restricted plugin functionality. The CWE-862 root cause - missing authorization - means protected endpoints can be triggered by anonymous HTTP requests, enabling unauthorized reading, modification, or disruption of booking data. No public exploit code and no active exploitation have been confirmed at the time of analysis.
Broken access control in the Travelfic Toolkit WordPress plugin (versions <= 1.5.1) permits subscriber-level authenticated users to execute privileged operations without proper authorization enforcement, yielding high integrity and availability impact on the affected installation. The flaw is classified as CWE-862 (Missing Authorization), meaning the plugin fails entirely to verify whether a requesting user holds the necessary capabilities before processing sensitive actions. No public exploit code and no active exploitation have been identified at time of analysis.
WP Event Solution WordPress plugin versions up to and including 4.1.19 allows authenticated users with customer-level privileges to delete arbitrary content due to missing authorization controls (CWE-862). The vulnerability is network-exploitable with low privilege requirements and no user interaction, yielding high availability impact through unrestricted content deletion. No public exploit has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Authentication bypass in the miniOrange Headless Single Sign On WordPress plugin (versions 1.6 and earlier) allows unauthenticated remote attackers to forge or manipulate JWTs and assume the identity of any user, including administrators. The CWE-347 root cause (improper verification of a cryptographic signature) combined with a network attack vector yields a critical 9.8 CVSS. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in the miniOrange 'OAuth Single Sign On - SSO (OAuth Client)' WordPress plugin (versions 7.0.0 and earlier) lets an unauthenticated remote attacker defeat the OAuth login flow and authenticate as an arbitrary user, including administrators. The CVSS 3.1 base score is 9.8 with a network, no-privilege, no-interaction vector, and the issue is rooted in improper verification of the identity asserted during single sign-on (CWE-290). At the time of analysis there is no public exploit identified and the CVE is not listed in CISA KEV, but the combination of unauthenticated access and full account takeover makes it a high-priority patching target.
Broken Access Control in the Solace Extra WordPress plugin (≤1.6.0) allows authenticated subscribers to bypass authorization checks and perform privileged plugin actions. The CVSS vector (PR:L, A:H) indicates that a low-privileged subscriber account is sufficient to trigger high-availability-impact operations, with minor integrity impact. No public exploit or active exploitation has been identified at time of analysis.
Broken access control in the Taxi Booking Manager for WooCommerce WordPress plugin (versions <= 2.0.3) allows unauthenticated remote attackers to perform privileged actions without authorization, resulting in high integrity impact. The vulnerability stems from missing authorization checks (CWE-862) on one or more plugin endpoints, enabling manipulation of booking data or plugin functionality without any credentials. No public exploit code or active exploitation has been identified at time of analysis, but the low attack complexity and absence of authentication requirements make this straightforward to exploit once the affected endpoint is identified.
Remote code execution in PostgreSQL logical decoding (versions before 18.5, 17.11, 16.15, 15.19, and 14.24) allows any database user holding REPLICATION privilege - a role explicitly below superuser - to load arbitrary shared libraries via dlopen by specifying a malicious logical decoding plugin name, executing arbitrary code as the OS account running the server. This is a missing authorization flaw (CWE-862): the REPLICATION privilege was not intended to grant the ability to load native code. No public exploit code or CISA KEV listing has been identified at time of analysis, though the high-impact CVSS 7.2 vector and RCE outcome make this a high-priority patching target for any deployment that grants REPLICATION to non-superusers.
Allowlist/blocklist enforcement in JupyterLab's PyPIExtensionManager.install() was silently bypassed due to a missing 'await' on the is_install_allowed coroutine, allowing authenticated low-privilege users to install otherwise-blocked PyPI packages in narrowly configured deployments. Affected are JupyterLab >=4.6.0 <=4.6.1 and <=4.5.9; the stock HTTP API and Extension Manager UI are explicitly not affected because they perform their own independently awaited check. No active exploitation has been identified - CISA KEV is absent, EPSS sits at 0.18% (8th percentile), and SSVC rates exploitation as none with non-automatable impact.
NoSQL injection in Budibase Server's MongoDB query execution endpoint (POST /api/v2/queries/:queryId) allows authenticated users with query write permission to bypass document-level filters and read, modify, or delete arbitrary MongoDB documents. The flaw stems from Handlebars interpolation being performed with escaping explicitly disabled (noEscaping: true), meaning JSON metacharacters in user-supplied parameters survive into the parsed query object that flows directly to MongoDB driver calls. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, a patch commit and PR are publicly available on GitHub.
NoSQL injection in Budibase's MongoDB datasource integration (versions before 3.40.0) allows any authenticated BASIC user to bypass per-user query-level access controls by injecting MongoDB operators into query parameters. The root cause is Handlebars enrichment configured with `noEscaping: true` followed by `JSON.parse`, which promotes attacker-supplied `$`-prefixed operators directly into MongoDB query documents without filtering - enabling full collection dumps, server-side JavaScript execution via `$where`, and unauthorized update or delete operations. No public exploit has been identified at time of analysis, though upstream fix commits are available and the vulnerability targets a configuration pattern recommended in Budibase's own documentation.
Cross-realm authorization bypass in OpenRemote allows any authenticated realm administrator to permanently delete notifications belonging to other tenants, including the master realm. Any account holding the write:admin role in a single realm can issue DELETE requests targeting notification resource identifiers owned by foreign realms, because the deletion endpoint performs no cross-realm ownership check. No public exploit has been identified at time of analysis and this CVE is not in the CISA KEV catalog, but the low attack complexity and straightforward HTTP-based attack surface make this a realistic insider threat in multi-tenant deployments.
SandboxPolicy bypass in Network-AI (versions before 5.15.1) enables authenticated attackers to execute arbitrary blocked commands by exploiting a parsing discrepancy between the policy engine and the command executor. The SandboxPolicy evaluates raw command strings with quotes intact, passing them through blocklist and approval-gate checks, while the executor subsequently strips those quotes during tokenization and runs the actual dangerous argv. No public exploit has been identified at time of analysis, but the bypass mechanism is mechanistically straightforward, requiring only knowledge of the quote-handling discrepancy to exploit via the network with low-privilege credentials.
Arbitrary file deletion in filebrowser before 2.63.19 allows authenticated users holding only Create permission to delete files outside their authorized scope by abusing a race condition in the TUS resumable upload cache eviction path. An attacker swaps an ancestor directory for a symlink during the cache TTL window, redirecting an unguarded os.Remove() call to an out-of-scope target and completely bypassing ScopedFs scope guards and Perm.Delete permission checks - no Delete permission is required. No public exploit code or CISA KEV listing is identified at time of analysis; the AC:H and AT:P metrics in the CVSS 4.0 vector reflect the timing-dependent nature of the attack.
Recursive operation authorization bypass in File Browser before v2.63.22 permits any authenticated user to copy, rename, or delete files they are explicitly denied access to, by initiating the operation on a permitted parent directory. The application's access-rule engine fails to evaluate descendant paths during bulk recursive traversal, defeating the entire isolation model for multi-user deployments. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 8.6 reflects high confidentiality and integrity impact with low attack complexity.
Missing authorization in SiYuan's /api/av/getAttributeViewSearchTarget endpoint allows an anonymous reader to retrieve database (attribute view) row content that publish-access filtering should hide. The affected route was added by commit 9b8e8956f and exists only in the development branch - it is absent from v3.7.3 and master and was fixed in v3.7.4, so no released stable version is affected. There is no public exploit identified at time of analysis and it is not in CISA KEV; despite the 9.2 CVSS the real-world exposure is limited to self-built development instances.
Authentication bypass in ManageEngine Password Manager Pro (all versions before 13232) and PAM360 (all versions before 8551) allows low-privileged network attackers to forge SAML assertions and gain unauthorized elevated access, including administrative sessions, within these enterprise credential vaults. The flaw stems from improper cryptographic signature verification of SAML responses (CWE-347), enabling token manipulation that the service provider cannot detect. Vendor patch is available; no public exploit code has been confirmed at time of analysis, but the crown-jewel nature of PAM platforms - storing all privileged enterprise credentials - makes this a high-priority remediation regardless of current exploitation status.
Authentication bypass via hard-coded credentials in the Portal Generator add-on for Priority ERP (developed by Soft Solutions) allows remote, unauthenticated attackers to access the portal and read sensitive information belonging to other users or the underlying ERP. Reported by the Israel National Cyber Directorate (INCD) and rated CVSS 9.3, the flaw combines embedded static credentials (CWE-798), sensitive-information exposure (CWE-200), and improper access control (CWE-284). No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authentication bypass in the Portal Generator Addon (developed by Soft Solutions) for Priority ERP allows remote, unauthenticated attackers to invoke a critical function that should be gated behind authentication, exposing sensitive ERP data. Rated CVSS 9.3 with a scope change, the flaw stems from a missing authentication check (CWE-306) on a network-reachable function. It was reported by Israel's National Cyber Directorate (INCD); no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated authentication bypass in the Portal Generator Addon to Priority ERP (developed by Soft Solutions) allows remote attackers with no credentials to access confidential ERP data across a scope boundary. Carrying a CVSS 3.1 score of 8.6 with Scope Changed and High Confidentiality impact, the flaw exposes the underlying Priority ERP backend through the portal layer - meaning business-critical records such as financial data, customer information, or operational records may be readable without any authentication. No public exploit code and no CISA KEV listing exist at time of analysis, but the attack profile (AV:N/AC:L/PR:N/UI:N) means exploitation requires minimal sophistication from any network position.
Unauthenticated remote access control bypass in the Portal Generator Addon for Priority ERP (developed by Soft Solutions) enables network-accessible exploitation with no authentication or user interaction required. The flaw, classified as CWE-284 Improper Access Control and tagged explicitly as an Authentication Bypass, allows attackers to circumvent access restrictions, resulting in high-impact confidentiality exposure and limited data integrity impact against affected ERP portal deployments. Reported by the Israel National Cyber Directorate (INCD), no public exploit code or active exploitation via CISA KEV has been identified at time of analysis.
Account takeover in Authorizer's OAuth callback handler allows an unauthenticated attacker to pre-stage persistent backdoor access to any victim account by registering an unverified email address before the victim completes a routine OAuth login. The attack exploits a trust boundary violation in `internal/http_handlers/oauth_callback.go` (lines 125-219): the handler merges any incoming OAuth identity into the first database account matching by email, auto-verifies that account's email, and never invalidates the original password - leaving the attacker's credential fully active. No public exploit code has been independently confirmed, but the GHSA advisory contains a complete, line-referenced attack chain that makes independent reproduction trivial.
Authentication bypass in Roskus Prospero Flow CRM before 5.15.9 lets unauthenticated remote attackers log in as any employee onboarded through the standard HR flow using only that employee's email address. The employee save controller assigns a hard-coded fallback password of "changeme" (CWE-798) because the onboarding form exposes no password field, leaving newly created accounts with a universally known credential. No public exploit code or CISA KEV listing is identified at time of analysis, but the flaw is trivially reproducible from the public fix commit, and the CVSS 4.0 base score is 9.3 (Critical).
Unauthenticated firmware flashing in Netis NC63 routers (firmware V3.0.0.3327) allows any attacker on the same network segment to permanently compromise the device by uploading arbitrary firmware without credentials. Two compounding flaws enable this: the embedded Boa web server grants access to any URL path containing '.cgi' regardless of session cookie validity, and the netis.cgi CGI dispatcher reads but never enforces the authentication state before invoking the firmware update handler. Firmware images are accepted if they pass only a forgeable additive checksum and static product string checks - no cryptographic signature verification is performed. A public proof-of-concept exploit exists on GitHub (ozcanpng/CVE-2026-73673), and no vendor-released patch has been identified at time of analysis.
Cross-tenant payroll data exposure in Roskus Prospero Flow CRM before 5.15.10 enables authenticated users holding standard payroll permissions to read salary and banking details belonging to employees of entirely separate companies within the same multi-tenant instance, and to create payroll records attributed to those foreign employees. The flaw exists at the query layer: the payroll listing endpoint omits a company_id scope constraint, and payroll creation validates employee identifiers for global database existence rather than for membership in the caller's own company. No public exploit code or CISA KEV listing has been identified at time of analysis, but the low exploitation barrier makes this an urgent priority for any multi-tenant deployment.
Authorization regression in Budibase v3.39.4 enables any authenticated BASIC user to generate S3 PutObject presigned URLs for arbitrary S3 buckets, bypassing the intended BUILDER-level permission gate on the attachment upload endpoint. The regression introduced in v3.39.4 - where the route guard was changed from `authorized(BUILDER)` to `authorized(PermissionType.TABLE, PermissionLevel.WRITE)` - gives all default BASIC users access to an endpoint that was explicitly restricted to builders. Compounding the issue, the endpoint accepts an attacker-controlled `bucket` parameter without validating it against the datasource's configured bucket, allowing writes to any S3 bucket reachable by the platform's stored IAM credentials. No public exploit tool exists at time of analysis, but the official GHSA advisory publishes complete reproduction steps and the test suite confirms the behavior, making exploitation trivial for any authenticated platform user.
Improper access control in File Browser before 2.63.20 allows authenticated users operating through proxy or hook authentication to escape their isolated directory scope and access the server root, exposing all other users' files for reading, modification, deletion, and sharing. The flaw specifically targets the createUserDir isolation mechanism, which is bypassed during auto-provisioning in proxy and hook authentication paths - leaving multi-tenant or shared File Browser deployments fully compromised at the data layer. No public exploit code has been identified at time of analysis, and CISA KEV listing is absent, but the CVSS 4.0 score of 8.7 reflects the high impact once a valid upstream credential is obtained.
Path canonicalization bypass in filebrowser before v2.63.21 permits authenticated users to circumvent administrator-configured deny rules by submitting case-variant or backslash-delimited path representations that the access rule engine fails to normalize before evaluation. The filesystem resolves these alternate representations to the same restricted objects, but the rules engine never matches them, effectively granting access to files the administrator explicitly intended to block. No public exploit code has been identified at time of analysis, though the attack concept is well-understood and straightforward to implement for any authenticated user of an affected deployment.
Privilege escalation in Grav's Flex Objects plugin (through version 1.4.6, confirmed against Grav 2.0.11) allows an authenticated low-privileged admin to achieve full site takeover by exploiting a missing authorization check in FlexApiController::update(). The generic /api/v1/flex-objects/user-accounts and /api/v1/flex-objects/user-groups API endpoints omit the field-level, target, and super-admin guards enforced by the dedicated Users and Groups controllers, so an account holding only api.access, admin.login, and users.update can overwrite a super administrator's password or self-grant admin.super group membership. No public exploit is identified at time of analysis; vendor-released patch Flex Objects 1.4.7 is available.
Privilege escalation in the getgrav/grav-plugin-api plugin before 1.0.13 allows an authenticated attacker holding only a minimal api.access-scoped key on a super account to mint a full-access, unscoped super key by exploiting missing scope-subset enforcement in createApiKey. The self-target path of requireApiKeyPermission() enforces only the baseline api.access scope, while the new key's scopes are taken verbatim from the attacker-controlled request body with no validation that they fall within the caller's granted scopes. Submitting an empty scopes array produces a key with unrestricted super privileges, directly enabling further attack chains including configuration-write-to-RCE. No public exploit code or CISA KEV listing is confirmed at time of analysis; EPSS is 0.30% (23rd percentile). Vendor-released patch version 1.0.13 is available.
Scope-cap bypass in grav-plugin-api before 1.0.13 allows a holder of a least-privilege api.config.write API key issued on a super-admin account to append arbitrary tokens to Grav's Twig sandbox allowlist (persisted to user/config/security.yaml) via the POST /reports/twig-content/allowlist endpoint. Widening the allowlist eliminates the Twig sandbox boundary, converting any subsequent content render into a server-side template injection (SSTI) sink and ultimately enabling remote code execution on the host. No public exploit has been confirmed and the CVE does not appear in CISA KEV at time of analysis, but the two-step primitive - allowlist poisoning followed by SSTI/RCE - is a well-understood attack class in CMS security research.
Server-side template injection (SSTI) leading to remote code execution in the Grav CMS API plugin (getgrav/grav-plugin-api) before version 1.0.13 is reachable by any low-privilege API key holder whose key was minted on a super-admin account. The root flaw is in PagesController::guardTwigContent(), which gates Twig processing via a bare isSuperAdmin() call that ignores the api_key_scopes array, allowing a key deliberately scoped to api.pages.write to enable process.twig on page save despite admin.pages_twig being intentionally excluded from that scope. A public proof-of-concept exists per SSVC data; exploitation is classified as automatable with total technical impact, making this a high-priority patch target for any Grav deployment where the required non-default configuration is active.
Force-disabling of two-factor authentication on Grav CMS user accounts is achievable through a missing scope enforcement check in the grav-plugin-api Composer package before version 1.0.13. Any holder of a low-privilege API key carrying api.users.write permission - or any scoped key on a super account - can POST to /api/v1/users/{user}/2fa/disable without supplying a TOTP code, stripping 2FA from any non-super target account and enabling direct account takeover. No active exploitation is currently confirmed (SSVC Exploitation: none; EPSS 0.34%), but SSVC rates this automatable with total technical impact, making prompt patching critical for any instance exposing the API with delegated keys.
Unauthorized disclosure of private content in SiYuan (siyuan-note) versions before v3.7.4 lets anonymous, unauthenticated clients subscribe to the WebSocket broadcast channel on the publish surface and receive real-time editing events for every document, including password-protected and explicitly forbidden ones. Reported by VulnCheck and documented in the vendor's GHSA advisory, the flaw is a missing authorization (CWE-862) check on broadcast sessions rather than a memory-corruption bug. No public exploit identified at time of analysis, but the trivial network-only access path and 9.2 CVSS 4.0 score make this a high-priority confidentiality issue for any exposed publish deployment.
Missing authentication on OpenChoreo's cluster-gateway (before 1.0.2 and 1.1.2) exposed caller-facing management APIs on the same externally reachable listener used for agent WebSocket traffic, letting network-reachable attackers hit /api/proxy/ and /api/exec/ without any credentials. In multi-cluster deployments this permits proxying the data-plane Kubernetes API and executing commands inside workload pods, effectively yielding cross-cluster control. No public exploit identified at time of analysis, but the GitHub Security Advisory (GHSA-qh9r-j7rp-4x2m) and CVSS 9.6 mark it as critical.
Authorization bypass in OpenChoreo's Kubernetes developer platform allows any authenticated user with a project-scoped grant to execute commands in and exfiltrate wirelogs from components belonging to entirely different projects within the same namespace. The root cause is that the `component:exec` and `wirelogs:view` API handlers in `exec.go` and `wirelogs.go` evaluate authorization using the attacker-controlled `project` query parameter rather than the authoritative `comp.Spec.Owner.ProjectName` field - a textbook CWE-639 insecure direct object reference. No public exploit or CISA KEV listing exists at time of analysis, but the CVSS 8.8 score and low-privilege network exploitation path make this a serious cross-tenant isolation failure in multi-project deployments.
Unauthenticated API access in OpenChoreo's Backstage backend exposes all `/api/*` routes to any network-reachable attacker, enabling catalog enumeration, scaffolder log reads, and catalog location creation or deletion without credentials. The root cause is two Backstage safety flags - `dangerouslyDisableDefaultAuthPolicy` and `dangerouslyAllowOutsideDevelopment` - hardcoded to `true` in both `app-config.yaml` and `app-config.production.yaml`, effectively disabling Backstage's authentication layer in all pre-fix deployments. No public exploit identified at time of analysis; vendor-released patches are available at v1.0.4, v1.1.4, and v1.2.1.
Command injection in FreePBX UCP Node server before 17.0.9 allows unauthenticated remote attackers to run arbitrary OS commands as the asterisk service user. The Socket.IO 4 middleware (io.use(checkAuth)) only guards the default namespace, so a client can reach unprotected custom namespaces and inject carriage-return/newline characters into Asterisk Manager Interface actions to execute commands. This is an authentication-bypass-plus-CRLF-injection chain; no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Authorization bypass (fail-open) in NextAuth.js (Auth.js) v5 affects applications on next-auth 5.0.0-beta.0 through 5.0.0-beta.31 that protect routes by checking only whether the auth() object exists. When Auth.js hits a server-side configuration error, the auth object is populated with a truthy error payload instead of null, so checks like !!auth or if (req.auth) evaluate true for every unauthenticated request. There is no public exploit identified at time of analysis and it is not in CISA KEV, but the impact is a silent, total bypass of session-existence gates once a deployment becomes misconfigured. Fixed in 5.0.0-beta.32.
Account takeover in the Budibase low-code platform (prior to 3.39.30) lets an attacker impersonate any existing user by abusing OIDC SSO account-linking. Because the OIDC verify callback in oidc.ts resolved the email claim without ever reading email_verified, and sso.ts fell back to getGlobalUserByEmail as the linking key, a fresh attacker identity from a configured IdP asserting a victim's email - even as unverified - is silently merged into the victim's account, inheriting its _id and roles up to global admin/builder. No public exploit is identified at time of analysis, but the root cause is confirmed by the vendor GHSA advisory and the fixing commit; the issue carries a CVSS 4.0 base score of 9.0.
Tenant admin account takeover in Budibase self-hosted deployments before 3.40.0 is achievable by any authenticated user, including the lowest-privilege BASIC app user. The PUT /api/global/users/tenant/owner endpoint fails to enforce the cloudRestricted middleware on self-hosted instances where SELF_HOSTED or DISABLE_ACCOUNT_PORTAL is set, allowing any valid session to silently reassign the tenant owner email address to an attacker-controlled value. By then triggering the public password-reset flow against that address, the attacker achieves full administrative control over the entire Budibase tenant; no public exploit has been identified at time of analysis, but the single authenticated API call required makes the exploit chain mechanistically trivial for any user who holds even a basic account.
Hard-coded SSH credentials embedded in Tenda CH, CP, and TX3 camera firmware across versions V21.x through V27.x expose all affected devices to remote authentication bypass, granting shell-level access to any attacker who obtains the static password. A GitHub-published proof-of-concept documents the exact credential and exploitation steps, significantly collapsing the barrier imposed by the CVSS 4.0 AC:H rating. No vendor-released patch has been identified at time of analysis, and no CISA KEV listing has been issued, though the public exploit makes this a credible near-term threat for network-exposed devices.
FreePBX Framework's restore functionality allows an authenticated user with backup-restore privileges to inject the hidden AUTHTYPE=none configuration setting via a crafted backup archive, completely disabling web administration authentication on the affected PBX. Versions prior to 16.0.47 (branch 16) and 17.0.30 (branch 17) are confirmed affected; vendor patches have been released. No public exploit identified at time of analysis, though the fix commit diff publicly reveals the exact attack technique against a widely deployed telephony platform.
Unauthenticated remote code execution in AgenticSeek (commit fc242c7) lets any network-adjacent attacker run arbitrary OS commands by POSTing crafted queries to the /query API endpoint, which the autonomous agent turns into shell commands executed via BashInterpreter (subprocess.Popen with shell=True and safety=False). The endpoint listens on 0.0.0.0:7777 with wildcard CORS and no authentication, so a single crafted HTTP request yields full host-level command execution, and an incomplete command blocklist fails to contain it. Rated CVSS 4.0 9.3 (critical); no public exploit identified at time of analysis and not listed in CISA KEV, but exploitation is trivial once the port is reachable.
Account takeover in IBM Langflow OSS versions 1.0.0 through 1.9.6 is possible because the platform fails to limit repeated failed authentication attempts (CWE-307), letting remote attackers brute-force or credential-stuff their way into user accounts. IBM (the reporting vendor) rates it CVSS 9.1 with high confidentiality and integrity impact, reflecting full compromise of a targeted account. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the missing lockout control is trivial to abuse against weak or reused credentials.
Privilege escalation in IBM i versions 7.3 through 7.6 allows a local authenticated attacker to abuse improper authorization controls in the Navigator for i debugger component to access or manipulate sensitive system data, or create new profiles with elevated privileges. The vulnerability is classified under CWE-285 (Improper Authorization), indicating the debugger fails to enforce sufficient privilege checks before granting access to sensitive operations. No public exploit or CISA KEV listing exists at time of analysis, though SSVC assesses the technical impact as total should exploitation occur.
Supply chain compromise of Go module environments is possible when a malicious GOPROXY serves specifically crafted forged sumdb tile pairs, exploiting CWE-347 (improper cryptographic verification) in the cmd/go toolchain's tile-parent validation logic. Affected are cmd/go versions before 1.25.13, 1.26.6, and 1.27.0-rc.3 - any developer workstation or CI/CD pipeline using these versions and a non-default GOPROXY is at risk of silently caching attacker-controlled module content that cannot be distinguished from legitimate modules through normal transparency log evaluation. No public exploit has been identified and no CISA KEV listing exists; EPSS of 0.12% (3rd percentile) indicates low current exploitation probability, but the theoretical supply chain impact is severe.
Authentication token validation flaws in IBM i 7.3 through 7.6 expose network-reachable systems to remote unauthenticated attackers capable of extracting sensitive information and performing limited unauthorized operations. The CWE-287 root cause (Improper Authentication) combined with a PR:N/AV:N CVSS vector confirms exploitation requires no credentials and no user interaction over the network. No active exploitation has been confirmed (not in CISA KEV), EPSS sits at 0.31% (23rd percentile), and SSVC marks exploitation status as 'none' - signals that collectively moderate urgency despite the 8.2 CVSS score.
Improper authentication in IBM i (IBM's integrated midrange operating system, formerly OS/400) versions 7.3, 7.4, 7.5 and 7.6 allows a remote attacker to bypass authentication controls to execute arbitrary code or read sensitive data, provided a legitimate user is induced to interact (UI:R). IBM has published a fix (support node 7283292) and rates it 9.6 critical; there is no public exploit identified at time of analysis and it is not in CISA KEV, with a low EPSS score of 0.41% (34th percentile) indicating no observed mass exploitation yet.
Improper authentication in IBM i 7.3 through 7.6 enables remote unauthenticated attackers to bypass authentication controls over the network, yielding access to sensitive information with additional low-level integrity and availability impact per the CVSS vector. The vulnerability is classified under CWE-287 (Improper Authentication) and tagged as an authentication bypass, indicating the platform's authentication mechanism can be circumvented without credentials. No public exploit code has been identified at time of analysis, and IBM has released a patch via their support portal.
Cross-tenant authorization bypass in Trigger.dev before 4.5.6 lets a caller holding a valid API key for one project act on another project's deployment. Because CreateDeploymentBackgroundWorkerServiceV4.call() looks up the deployment by friendlyId with no environmentId/tenant predicate, an attacker can attach an attacker-controlled background worker to a victim project's deployment and force it from BUILDING to DEPLOYING. No public exploit identified at time of analysis; the flaw is an insecure-direct-object-reference (IDOR) affecting the deployments API.
Account takeover in Trigger.dev before 4.5.2 allows an unauthenticated remote attacker to hijack any existing user account that has not yet linked a Google OAuth identity, by presenting a Google profile whose email is unverified but matches the victim's registered address. The `addGoogleStrategy()` function in `apps/webapp/app/services/googleAuth.server.ts` omits the `email_verified` assertion before calling `findOrCreateGoogleUser()`, causing the server to bind the attacker's Google `authIdentifier` to the victim's account when the conditional `existingEmailUser && !existingUser` is satisfied. No public exploit has been identified at time of analysis, but the fix is available in v4.5.2 and the attack requires no Trigger.dev credentials.
Unauthorized access to privileged system objects is possible in IBM i 7.3 through 7.6 via a time-of-check to time-of-use (TOCTOU) race condition exploiting symbolic links, reachable by remote authenticated low-privilege users. The CVSS scope change (S:C) combined with full C/I/A impact signals that successful exploitation can reach objects and resources beyond the attacker's normal privilege boundary, effectively enabling privilege escalation across the OS. No public exploit code or CISA KEV listing has been identified at time of analysis, but the patch is available via the IBM advisory.
Path traversal in IBM i versions 7.3 through 7.6 enables a low-privileged remote authenticated attacker to bypass object-level access controls and gain unauthorized read, write, or disruptive access to arbitrary system objects. The CVSS 8.8 rating reflects full C/I/A impact across a network-accessible attack surface requiring only low privilege - consistent with IBM's own report as originating vendor and the EUVD advisory. No public exploit code has been identified and this vulnerability is not listed in CISA KEV; EPSS at 0.36% (29th percentile) indicates low current exploitation activity, though a vendor patch is now confirmed available.
Authentication bypass in IBM i (OS/400) versions 7.3, 7.4, 7.5, and 7.6 allows a remote unauthenticated attacker to access server resources with the privileges of an authenticated user by exploiting improper authentication handling during NTLM session negotiation. The CVSS 3.1 base score is 9.8 (network vector, no privileges, no user interaction, total confidentiality/integrity/availability impact), though the EPSS exploitation probability is low (0.40%, 33rd percentile) and CISA's SSVC framework records exploitation status as 'none'. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in IBM WebSphere Application Server Liberty (versions 17.0.0.3 through 26.0.0.8) allows remote attackers to circumvent authentication controls when the rtcomm-1.0 or rtcommGateway-1.0 feature is enabled, exposing protected real-time communication functions. The CVSS 3.1 base score is 9.4 (AV:N/AC:L/PR:N/UI:N/C:H/I:H/A:L), reflecting high confidentiality and integrity impact reachable over the network without credentials. A vendor patch is available; there is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV.
IBM Storage Scale GUI versions 5.2.3.0-5.2.3.8 and 6.0.0.0-6.0.1.0 ship with a hardcoded authentication token embedded in source code, granting any network-reachable attacker the ability to authenticate to the REST API and inter-node cluster communication channels without valid credentials. The static nature of the token means it is identical across every affected deployment, making a single disclosure universally exploitable against all unpatched instances. IBM has released a patch via advisory 7283308, and no public exploit or CISA KEV listing has been identified at time of analysis.
Privilege escalation in Kibana Fleet allows an authenticated low-privileged user to bypass integration-scoped authorization controls by exploiting a logic flaw in how policy update requests are validated (CWE-863). An operator holding only the Elastic Defend endpoint policy management role can craft a Fleet API update request that substitutes a different integration type into an existing endpoint policy they control, because Fleet evaluates the authorization check against the stored policy's original integration rather than the replacement integration supplied in the request. No public exploit code has been identified at time of analysis, but the vendor (Elastic) has issued advisory ESA-2026-127 with patched releases.
Cross-space authorization bypass in Kibana allows authenticated users to access trained machine learning model inference outputs, and stop or modify active model deployments, in Kibana Spaces they are not authorized to access. The vulnerability arises because API endpoints for ML model inference and deployment management accept user-controlled resource identifiers without enforcing space-level ACL boundaries, enabling privilege escalation across the Space isolation boundary. No public exploit code has been identified and Elastic has released fixed versions 8.19.20, 9.4.5, and 9.5.1 per advisory ESA-2026-126.
Incorrect authorization in Kibana Agent Builder allows authenticated users to access, modify, or delete private agents they do not own when sharing a username with another principal across different Elasticsearch authentication realms. The flaw stems from a fallback ownership check that compares usernames - which are not unique across realms - rather than stable user identifiers, enabling cross-realm identity confusion. No public exploit or active exploitation (CISA KEV) has been identified at time of analysis, but the low attack complexity and network accessibility make this a credible insider or multi-tenant threat.
Hard-coded credential exposure in the FL-100 transcranial brain stimulation device enables any attacker within Bluetooth range to bypass authentication entirely and manipulate neurostimulation parameters across every deployed unit simultaneously. The credential is universally shared across all FL-100 devices manufactured under both the Flow Neuroscience and Halo Neuroscience brands, meaning a single credential disclosure event compromises the entire installed base at once. No public exploit code has been identified at time of analysis and active exploitation is not confirmed by CISA KEV, but the zero-privilege, zero-complexity authentication bypass presents a credible patient safety risk in clinical and home-use therapeutic environments.
Missing Authorization in Kibana's Elastic Security module permits authenticated users holding detection rule authoring privileges to execute Osquery live queries and Elastic Defend response actions against enrolled managed endpoints without possessing the specific Osquery or Elastic Defend privileges that normally govern those capabilities. The CVSS 8.1 score reflects a network-accessible, low-complexity attack path with high confidentiality and integrity impact against enrolled host infrastructure. No active exploitation has been confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis, but patch versions 8.19.20 and 9.4.5 are available per Elastic Security Advisory ESA-2026-96.
Kibana's Machine Learning subsystem fails to enforce space-level authorization, allowing any authenticated low-privilege user in one Kibana space to read ML data from all other spaces and make unauthorized modifications across the entire deployment. The root cause is that ML operations execute with elevated internal Elasticsearch permissions while a subset of ML functionality omitted the per-request space isolation filter that enforces tenancy boundaries. No public exploit has been identified, but the attack requires only a standard user account, making it a realistic internal threat in multi-tenant or shared Kibana deployments. Fixed versions 8.19.20 and 9.4.5 are referenced in the Elastic security advisory ESA-2026-92.
Elastic Kibana's Elastic Security endpoint policy editor exposes sensitive Elastic Defend telemetry through a privilege escalation in the field value suggestion feature. Authenticated users holding Kibana Elastic Security feature privileges - but lacking Elasticsearch index-level read access to Elastic Defend event indices - can retrieve field values including process command line arguments, which routinely contain credentials, API tokens, and connection strings harvested from protected endpoints. No public exploit has been identified at time of analysis, but the low attack complexity and scope change across the Kibana-to-Elasticsearch authorization boundary make this straightforward to abuse by any user with a qualifying Kibana role.
Missing authorization on Kibana's Observability Onboarding API routes allows any authenticated low-privilege user sharing a Kibana space to enumerate, read, and overwrite the onboarding flow state of other users in that space. Affected installations include all Kibana versions prior to 8.19.19 and 9.4.5 across both self-managed and Elastic Cloud deployments. No public exploit code has been identified at time of analysis and this vulnerability is not listed in the CISA KEV catalog; however, the CVSS high integrity impact (I:H) reflects an attacker's ability to corrupt another user's onboarding progress and trigger persistent server errors in the victim's Observability Onboarding view.
Authentication bypass in IBM i (the operating system for IBM Power/AS-400 midrange systems) versions 7.3, 7.4, 7.5, and 7.6 allows remote attackers to circumvent security restrictions because the system improperly validates a client-asserted identity (CWE-287). Because a caller's claimed identity is trusted without adequate verification, an attacker can impersonate another principal and gain unauthorized access to protected resources with full confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis, and the EPSS probability is low (0.34%, 27th percentile), but the CVSS 9.8 rating and network-reachable, unauthenticated vector make this a high-priority patch.
Authorization bypass in Open Identity Platform OpenDJ before 5.1.2 lets any authenticated account holding the proxied-auth privilege impersonate arbitrary non-root directory users during a SASL PLAIN bind. The PlainSASLMechanismHandler validated only the PROXIED_AUTH privilege but skipped the mayProxy ACI scope check, so the proxy ACIs meant to constrain which identities may be assumed were not enforced (CVSS 9.6). No public exploit has been identified at time of analysis, but the flaw is confirmed by the vendor GHSA advisory and fixed in 5.1.2.
Cross-enterprise IDOR in Rainbond through 6.9.7 allows any authenticated user to read or modify another enterprise's resources by substituting an arbitrary tenant name in API URL paths. The CheckToken function validates token authenticity but never cross-checks that the token's enterprise matches the enterprise embedded in the request path, enabling horizontal privilege escalation across tenant boundaries. Impacted resources include services, plugins, environment variables, and TLS certificates belonging to any enterprise on the same Rainbond instance. No public exploit code or CISA KEV listing has been identified at time of analysis.
Broken authorization in vantage6's algorithm store allows any authenticated algorithm developer to overwrite a peer's pending algorithm metadata - including the Docker image reference or tag - before that submission is approved by reviewers. Versions 5.0.2 and earlier of this pip-installable federated analytics platform are affected, with no patch available. The practical consequence is a supply-chain integrity failure: nodes and reviewers may trust and execute a container image entirely different from the one originally submitted for review, with no visible indication that a substitution occurred.
Unauthenticated remote root compromise affects CyberPanel before 3.0.0 through a hard-coded JWT signing secret in the WebTerminal FastAPI SSH service. Because the secret is baked into the code, an attacker can mint a valid token specifying ssh_user=root and connect to the WebSocket terminal on TCP 8888 with no credentials, receiving a fully interactive root shell. No public exploit identified at time of analysis, but the trivial exploitation path (known secret, single forged token) makes reliable weaponization straightforward for any actor who reads the source.
Server-side request forgery in Gitea Open Source Git Server (all versions through 1.26.4) lets attackers abuse the repository migration and mirror features to reach internal network resources. Two distinct weaknesses are involved: a DNS-rebinding bypass where a hostname resolves to a permitted address during validation and to an internal address when the actual request is made, and a missing re-validation flaw where redirect or subsequent fetch targets are not re-checked against the allow/deny policy. No public exploit was identified at time of analysis, EPSS is low (0.15%), and it is not in CISA KEV, but the vendor rates technical impact as total and the issue is fixed in 1.27.0.
Broken access control in Gitea (self-hosted Git service) versions up to and including 1.26.4 lets the team-repository linking endpoint ignore the RepoAdminChangeTeamAccess organization setting, so repository administrators can grant or alter team access to repositories even when an org owner has explicitly restricted that ability. This CWE-862 missing-authorization flaw undermines an intended org-level guardrail, exposing private repository contents (C:H) and permitting unauthorized permission changes (I:H). No public exploit has been identified at time of analysis, and the EPSS probability is low (0.15%, 5th percentile).
Unauthorized cross-tenant cluster takeover in Red Hat Multicluster Engine (MCE) for Kubernetes allows an authenticated tenant to force a managed cluster into another tenant's ManagedClusterSet by manipulating ClusterClaim labels. The clusterclaims-controller processes these label changes without enforcing tenant ownership boundaries, enabling the attacker to then inject policies and workloads into clusters they do not own. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope-changing nature (S:C) and high confidentiality impact make this a serious multi-tenancy isolation failure.
Lenovo System Update contains an authentication bypass (CWE-290) that permits a locally authenticated standard user to circumvent privilege checks and execute arbitrary code with elevated system privileges. Affected products span all tracked versions per CPE data, with Lenovo confirming the issue and releasing a patch under advisory LEN-213316. No public exploit code or CISA KEV listing has been identified at time of analysis, limiting immediate threat to environments where adversaries already have local user access.
Access control bypass in rsync daemon versions 3.1.0 through 3.4.4 lets remote unauthenticated attackers evade module-level 'hosts deny' restrictions by forcing DNS resolution to fail during hostname-based access checks, causing the daemon to skip the rule (fail-open) instead of denying. Reported by VulnCheck and fixed in rsync 3.5.0, it exposes file trees in modules that were meant to be IP/hostname-restricted; no public exploit has been identified at time of analysis and it is not listed in CISA KEV.
Authorization bypass in rsync 3.1.0 through 3.4.x allows authenticated users to circumvent module-level access controls when group-based deny rules are configured with space-containing group names. The auth users directive's comma-only parser silently discards deny rules for any @Group Name entry whose group name contains a space, granting unintended access to restricted rsync modules regardless of the administrator's intended group-based exclusions. The rsync project designated v3.5.0 a major security release to address this flaw; no CISA KEV listing or public exploit code has been identified at time of analysis.
Arbitrary file write in rsync before 3.5.0 allows attackers who control --temp-dir or --link-dest option values to escape the intended destination tree by supplying absolute paths, bypassing the rename-confinement security boundary. Any filesystem location writable by the rsync process can be targeted, enabling overwrite of system files, configuration, or planted malicious content. No public exploit identified at time of analysis, but the CVSS 4.0 score of 7.2 with high integrity and availability impact reflects serious real-world risk in server environments where option values are externally influenced.
Path confinement bypass in the rsync daemon (versions before 3.5.0) lets remote clients escape the intended per-module chroot root when a module path contains a '/./' boundary marker, granting unauthorized read or write access to files outside the module subtree. Reported by VulnCheck and carrying a CVSS 4.0 score of 9.1, the flaw is exploitable by mishandling the '/./' notation or by forging delta-basis (xname) transfers that cross the boundary. No public exploit has been identified at time of analysis, but the fix is a coordinated advisory (GHSA-wj7w-vh23-mm44) shipped in the major 3.5.0 security release.
IP-based access control bypass in the rsync daemon (rsyncproject/rsync) before version 3.5.0 lets unauthenticated remote attackers forge their source address by injecting a crafted PROXY protocol header, defeating hosts allow/deny restrictions. Reported by VulnCheck and fixed in the v3.5.0 major security release, the flaw applies to daemons that trust PROXY protocol headers yet accept direct client connections. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the CVSS 4.0 base score of 9.1 reflects high confidentiality and integrity impact once the IP allowlist is circumvented.
Bluetooth LE legacy pairing authentication in Silicon Labs RS9116W and SiWx917 wireless modules (WiseConnect SDK) can be bypassed by manipulating the Temporary Key (TK) value during Passkey Entry association, allowing an adjacent unauthenticated attacker to pair with the target device without possessing the correct passkey. Successful exploitation yields high confidentiality and integrity impact on the vulnerable system. The vulnerability is academically documented as B-E3 in a published research paper (arxiv.org/pdf/2409.02905); no public exploit tool or CISA KEV entry has been identified at time of analysis.
Bluetooth Low Energy re-pairing in Silicon Labs RS9116W and SiWx91x devices allows a nearby unauthenticated attacker to negotiate a lower security level during the re-pairing process with an already-bonded peer, effectively bypassing the previously established security guarantees. Documented as the 'V3' attack variant in the NDSS-published BLERP (BLE Re-Pairing) research paper, this flaw enables high-impact compromise of confidentiality, integrity, and availability across affected WiseConnect firmware lines. No public exploit code or CISA KEV listing is confirmed at time of analysis, though the NDSS publication constitutes academic proof-of-concept disclosure.
BLE re-pairing attacks against Silicon Labs RS9116W and SiWx917 modules allow an adjacent unauthenticated attacker to spoof a previously bonded device and force the target to re-bond with a rogue device, yielding full BLE session control. Both WiseConnect SDK 2.x (before 2.14.0) and 4.x (before 4.1.0) are confirmed affected per vendor release notes and the academic BLERP (BLE Re-Pairing Attacks and Defenses) paper published at NDSS. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog, though the NDSS paper provides a detailed methodology that could guide motivated researchers to weaponize the technique.
Cross-tenant IDOR in Roskus Prospero Flow CRM before 5.4.7 allows any authenticated user to read sensitive product records belonging to other tenant companies and reassign those products into their own account. Two compounding root causes drive the impact: ProductUpdateController lacked the MainController inheritance that enforces session-based authorization, leaving the product read endpoint unguarded, while ProductRepository::save() performed a bare Product::find($data['id']) lookup with no company_id scope constraint, enabling cross-tenant record hijacking. No public exploit or CISA KEV listing exists at time of analysis, but the exploit conditions are trivially met by any authenticated session holder.
SQL injection in Pimcore's Block.php field loader, affecting versions 2026.1.0–2026.1.4 and all releases below 12.3.9, enables an authenticated editor-level user to exfiltrate arbitrary database content including password hashes via UNION-based injection. The vulnerability chains two incomplete fixes: a missing trailing `$` anchor in ClassDefinition.php regex validation permits malicious UIDs to pass input checks, and six unquoted `getClassId()` concatenations in Block.php execute the injected SQL when any data object of the malicious class is loaded. A working proof-of-concept is publicly documented in GitHub Security Advisory GHSA-2mhj-fhvg-v428, and vendor-released patches (2026.1.5 and 12.3.9) address both weaknesses.
Unauthenticated broken access control in the Arvow AI SEO Writer WordPress plugin (versions ≤ 1.5.3) exposes unprotected endpoints that allow remote unauthenticated attackers to perform privileged write-level operations due to missing authorization checks (CWE-862). The CVSS 3.1 vector (PR:N/I:H) confirms no authentication is required and integrity impact is high, indicating attackers can modify SEO configuration, inject content, or alter plugin-managed data without any credentials. No active exploitation has been confirmed via CISA KEV, and no public proof-of-concept has been identified at time of analysis.
Broken access control in the StoreGrowth: Smart Sales Booster for WooCommerce plugin (versions <= 2.1.1) permits unauthenticated remote attackers to bypass authorization checks and perform privileged store management actions. The root cause is a missing authorization gate (CWE-862), meaning certain plugin endpoints execute sensitive operations without verifying the caller's identity or permissions. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the zero-friction exploitation conditions - no authentication, no user interaction, network-accessible - make this a straightforward target for opportunistic scanning.
Unauthenticated payment bypass in SMEPay: UPI Gateway for WooCommerce plugin (versions <= 1.0.5) allows remote attackers to complete WooCommerce orders without valid UPI payment by exploiting missing authorization controls. The plugin fails to enforce access checks on payment-related endpoints, enabling an unauthenticated network attacker to manipulate transaction state with no user interaction required. No public exploit or CISA KEV listing has been identified at time of analysis, but the network-accessible, zero-authentication attack surface makes this trivially abusable on any exposed WooCommerce storefront running the affected plugin.
Unauthenticated broken access control in the MultiVendorX WordPress plugin (versions 5.0.10 and earlier) exposes restricted marketplace data to any remote attacker without credentials. The flaw stems from missing authorization checks (CWE-862) on one or more plugin endpoints, allowing unauthenticated network requests to bypass access restrictions and retrieve sensitive information such as vendor orders, customer data, or marketplace configurations. No public exploit or CISA KEV listing has been identified at time of analysis, but the low attack complexity and zero-authentication requirement make this a straightforward target for opportunistic scanning.
Broken access control in Bitcoin Lightning Payment Gateway for WooCommerce (via CLINK) versions 1.0.7 and below exposes one or more plugin endpoints - almost certainly WordPress AJAX handlers or REST API routes - without the required capability checks, allowing unauthenticated remote attackers to perform privileged actions with high integrity impact. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N) confirms no credentials are needed and exploitation requires no user interaction, making this trivially scriptable against any internet-facing WordPress store running the affected plugin. No public exploit code has been identified and the vulnerability is not listed in CISA KEV at time of analysis, though the attack conditions are permissive enough to make opportunistic exploitation straightforward.
WPMobile.App plugin for WordPress, versions 11.77 and earlier, allows unauthenticated remote attackers to bypass authorization controls and access protected resources. The CVSS 7.5 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) reflects full network exploitability with high confidentiality impact and no integrity or availability consequence, consistent with an unauthorized read-access scenario. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.
Unauthenticated broken access control in the Hydra Booking WordPress plugin by Themefic (versions ≤ 1.2.2) permits any remote, unauthenticated party to bypass authorization checks and interact with restricted plugin functionality. The CWE-862 root cause - missing authorization - means protected endpoints can be triggered by anonymous HTTP requests, enabling unauthorized reading, modification, or disruption of booking data. No public exploit code and no active exploitation have been confirmed at the time of analysis.
Broken access control in the Travelfic Toolkit WordPress plugin (versions <= 1.5.1) permits subscriber-level authenticated users to execute privileged operations without proper authorization enforcement, yielding high integrity and availability impact on the affected installation. The flaw is classified as CWE-862 (Missing Authorization), meaning the plugin fails entirely to verify whether a requesting user holds the necessary capabilities before processing sensitive actions. No public exploit code and no active exploitation have been identified at time of analysis.
WP Event Solution WordPress plugin versions up to and including 4.1.19 allows authenticated users with customer-level privileges to delete arbitrary content due to missing authorization controls (CWE-862). The vulnerability is network-exploitable with low privilege requirements and no user interaction, yielding high availability impact through unrestricted content deletion. No public exploit has been identified at time of analysis, and this CVE is not listed in CISA KEV.
Authentication bypass in the miniOrange Headless Single Sign On WordPress plugin (versions 1.6 and earlier) allows unauthenticated remote attackers to forge or manipulate JWTs and assume the identity of any user, including administrators. The CWE-347 root cause (improper verification of a cryptographic signature) combined with a network attack vector yields a critical 9.8 CVSS. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Authentication bypass in the miniOrange 'OAuth Single Sign On - SSO (OAuth Client)' WordPress plugin (versions 7.0.0 and earlier) lets an unauthenticated remote attacker defeat the OAuth login flow and authenticate as an arbitrary user, including administrators. The CVSS 3.1 base score is 9.8 with a network, no-privilege, no-interaction vector, and the issue is rooted in improper verification of the identity asserted during single sign-on (CWE-290). At the time of analysis there is no public exploit identified and the CVE is not listed in CISA KEV, but the combination of unauthenticated access and full account takeover makes it a high-priority patching target.
Broken Access Control in the Solace Extra WordPress plugin (≤1.6.0) allows authenticated subscribers to bypass authorization checks and perform privileged plugin actions. The CVSS vector (PR:L, A:H) indicates that a low-privileged subscriber account is sufficient to trigger high-availability-impact operations, with minor integrity impact. No public exploit or active exploitation has been identified at time of analysis.
Broken access control in the Taxi Booking Manager for WooCommerce WordPress plugin (versions <= 2.0.3) allows unauthenticated remote attackers to perform privileged actions without authorization, resulting in high integrity impact. The vulnerability stems from missing authorization checks (CWE-862) on one or more plugin endpoints, enabling manipulation of booking data or plugin functionality without any credentials. No public exploit code or active exploitation has been identified at time of analysis, but the low attack complexity and absence of authentication requirements make this straightforward to exploit once the affected endpoint is identified.
Remote code execution in PostgreSQL logical decoding (versions before 18.5, 17.11, 16.15, 15.19, and 14.24) allows any database user holding REPLICATION privilege - a role explicitly below superuser - to load arbitrary shared libraries via dlopen by specifying a malicious logical decoding plugin name, executing arbitrary code as the OS account running the server. This is a missing authorization flaw (CWE-862): the REPLICATION privilege was not intended to grant the ability to load native code. No public exploit code or CISA KEV listing has been identified at time of analysis, though the high-impact CVSS 7.2 vector and RCE outcome make this a high-priority patching target for any deployment that grants REPLICATION to non-superusers.
Allowlist/blocklist enforcement in JupyterLab's PyPIExtensionManager.install() was silently bypassed due to a missing 'await' on the is_install_allowed coroutine, allowing authenticated low-privilege users to install otherwise-blocked PyPI packages in narrowly configured deployments. Affected are JupyterLab >=4.6.0 <=4.6.1 and <=4.5.9; the stock HTTP API and Extension Manager UI are explicitly not affected because they perform their own independently awaited check. No active exploitation has been identified - CISA KEV is absent, EPSS sits at 0.18% (8th percentile), and SSVC rates exploitation as none with non-automatable impact.
NoSQL injection in Budibase Server's MongoDB query execution endpoint (POST /api/v2/queries/:queryId) allows authenticated users with query write permission to bypass document-level filters and read, modify, or delete arbitrary MongoDB documents. The flaw stems from Handlebars interpolation being performed with escaping explicitly disabled (noEscaping: true), meaning JSON metacharacters in user-supplied parameters survive into the parsed query object that flows directly to MongoDB driver calls. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, a patch commit and PR are publicly available on GitHub.
NoSQL injection in Budibase's MongoDB datasource integration (versions before 3.40.0) allows any authenticated BASIC user to bypass per-user query-level access controls by injecting MongoDB operators into query parameters. The root cause is Handlebars enrichment configured with `noEscaping: true` followed by `JSON.parse`, which promotes attacker-supplied `$`-prefixed operators directly into MongoDB query documents without filtering - enabling full collection dumps, server-side JavaScript execution via `$where`, and unauthorized update or delete operations. No public exploit has been identified at time of analysis, though upstream fix commits are available and the vulnerability targets a configuration pattern recommended in Budibase's own documentation.
Cross-realm authorization bypass in OpenRemote allows any authenticated realm administrator to permanently delete notifications belonging to other tenants, including the master realm. Any account holding the write:admin role in a single realm can issue DELETE requests targeting notification resource identifiers owned by foreign realms, because the deletion endpoint performs no cross-realm ownership check. No public exploit has been identified at time of analysis and this CVE is not in the CISA KEV catalog, but the low attack complexity and straightforward HTTP-based attack surface make this a realistic insider threat in multi-tenant deployments.
SandboxPolicy bypass in Network-AI (versions before 5.15.1) enables authenticated attackers to execute arbitrary blocked commands by exploiting a parsing discrepancy between the policy engine and the command executor. The SandboxPolicy evaluates raw command strings with quotes intact, passing them through blocklist and approval-gate checks, while the executor subsequently strips those quotes during tokenization and runs the actual dangerous argv. No public exploit has been identified at time of analysis, but the bypass mechanism is mechanistically straightforward, requiring only knowledge of the quote-handling discrepancy to exploit via the network with low-privilege credentials.
Arbitrary file deletion in filebrowser before 2.63.19 allows authenticated users holding only Create permission to delete files outside their authorized scope by abusing a race condition in the TUS resumable upload cache eviction path. An attacker swaps an ancestor directory for a symlink during the cache TTL window, redirecting an unguarded os.Remove() call to an out-of-scope target and completely bypassing ScopedFs scope guards and Perm.Delete permission checks - no Delete permission is required. No public exploit code or CISA KEV listing is identified at time of analysis; the AC:H and AT:P metrics in the CVSS 4.0 vector reflect the timing-dependent nature of the attack.
Recursive operation authorization bypass in File Browser before v2.63.22 permits any authenticated user to copy, rename, or delete files they are explicitly denied access to, by initiating the operation on a permitted parent directory. The application's access-rule engine fails to evaluate descendant paths during bulk recursive traversal, defeating the entire isolation model for multi-user deployments. No public exploit code has been identified at time of analysis, but the CVSS 4.0 score of 8.6 reflects high confidentiality and integrity impact with low attack complexity.
Missing authorization in SiYuan's /api/av/getAttributeViewSearchTarget endpoint allows an anonymous reader to retrieve database (attribute view) row content that publish-access filtering should hide. The affected route was added by commit 9b8e8956f and exists only in the development branch - it is absent from v3.7.3 and master and was fixed in v3.7.4, so no released stable version is affected. There is no public exploit identified at time of analysis and it is not in CISA KEV; despite the 9.2 CVSS the real-world exposure is limited to self-built development instances.
Authentication bypass in ManageEngine Password Manager Pro (all versions before 13232) and PAM360 (all versions before 8551) allows low-privileged network attackers to forge SAML assertions and gain unauthorized elevated access, including administrative sessions, within these enterprise credential vaults. The flaw stems from improper cryptographic signature verification of SAML responses (CWE-347), enabling token manipulation that the service provider cannot detect. Vendor patch is available; no public exploit code has been confirmed at time of analysis, but the crown-jewel nature of PAM platforms - storing all privileged enterprise credentials - makes this a high-priority remediation regardless of current exploitation status.
Authentication bypass via hard-coded credentials in the Portal Generator add-on for Priority ERP (developed by Soft Solutions) allows remote, unauthenticated attackers to access the portal and read sensitive information belonging to other users or the underlying ERP. Reported by the Israel National Cyber Directorate (INCD) and rated CVSS 9.3, the flaw combines embedded static credentials (CWE-798), sensitive-information exposure (CWE-200), and improper access control (CWE-284). No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Authentication bypass in the Portal Generator Addon (developed by Soft Solutions) for Priority ERP allows remote, unauthenticated attackers to invoke a critical function that should be gated behind authentication, exposing sensitive ERP data. Rated CVSS 9.3 with a scope change, the flaw stems from a missing authentication check (CWE-306) on a network-reachable function. It was reported by Israel's National Cyber Directorate (INCD); no public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
Unauthenticated authentication bypass in the Portal Generator Addon to Priority ERP (developed by Soft Solutions) allows remote attackers with no credentials to access confidential ERP data across a scope boundary. Carrying a CVSS 3.1 score of 8.6 with Scope Changed and High Confidentiality impact, the flaw exposes the underlying Priority ERP backend through the portal layer - meaning business-critical records such as financial data, customer information, or operational records may be readable without any authentication. No public exploit code and no CISA KEV listing exist at time of analysis, but the attack profile (AV:N/AC:L/PR:N/UI:N) means exploitation requires minimal sophistication from any network position.
Unauthenticated remote access control bypass in the Portal Generator Addon for Priority ERP (developed by Soft Solutions) enables network-accessible exploitation with no authentication or user interaction required. The flaw, classified as CWE-284 Improper Access Control and tagged explicitly as an Authentication Bypass, allows attackers to circumvent access restrictions, resulting in high-impact confidentiality exposure and limited data integrity impact against affected ERP portal deployments. Reported by the Israel National Cyber Directorate (INCD), no public exploit code or active exploitation via CISA KEV has been identified at time of analysis.