Authentication Bypass
Monthly
Cross-namespace authorization bypass in HashiCorp consul-k8s 0.42.0 and later can let an attacker with an existing low-privilege authenticated foothold obtain elevated Consul privileges through component ACL binding rules; deployments not using those rules or running releases before 0.42.0 are outside the stated affected scope. The flaw is fixed in consul-k8s 2.1.0 and 1.8.18, and no public exploit was identified at time of analysis, but the 9.9 CVSS score and act_now priority support prompt remediation.
Missing authentication in OmniRoute 3.8.50 through 3.8.51 lets an unauthenticated remote caller POST to /api/sync/tokens and mint a sync token whenever the instance runs in open mode (requireLogin=false), then spend that token against GET /api/sync/bundle to pull decrypted provider credentials and plaintext API keys - the same material /api/settings/export-json already denies to anonymous callers. The flaw is conditional: when login is enabled (the default), token issuance already required a dashboard session or the local CLI, so only open-mode deployments are reachable, which is why the assessed CVSS:3.1 vector is AV:N/AC:H/PR:N/UI:N with confidentiality-only impact (C:H/I:N/A:N) even though the vendor's CVSS:4.0 score is 8.2. Tokens minted this way were recorded as issuedBy:"open" and kept opening the bundle after login was re-enabled; version 3.8.52 fixes issuance, routing /api/sync/tokens into the always-protected tier and refusing the legacy "open" tokens. No public exploit code was identified at time of analysis and the CVE is not in CISA KEV; priority is this_week.
An authorization bypass in HashiCorp Consul's service mesh proxy registration lets an authenticated user who holds only service:write permission apply Envoy escape-hatch (custom proxy/bootstrap) configuration that is normally reserved for holders of mesh:write, effectively escalating the privileges of an existing mesh participant. Consul Community Edition before 2.1.0 and Consul Enterprise before 2.1.0 and before 1.21.19 are affected; the CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), with the PR:L metric reflecting that a valid ACL token with service:write is required, so this is not anonymous remote compromise. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor states the issue is fixed in Consul CE 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.
Unauthenticated retrieval of cached service mesh leaf certificates and their private keys affects HashiCorp Consul and Consul Enterprise 1.17.0 through 2.0.4 through the agent's service mesh leaf certificate API, which fails to enforce ACL authorization (CWE-862). A remote attacker who can reach the affected agent API can obtain the certificate and private key for services whose leaf certificates are already cached, allowing impersonation of those mesh services without a valid ACL token or user interaction. HashiCorp has released fixes in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19; no public exploit code or CISA KEV entry was identified at time of analysis, and the issue is prioritized for remediation this week.
Unauthenticated webhook forgery in the Padok Burrito Terraform Automation Collaboration Software Kubernetes operator through 0.12.0 lets anyone who can reach burrito-server's /api/webhook endpoint create or delete TerraformPullRequest custom resources with attacker-chosen Branch, Base and ID fields, provided the tracked repository's credential omits webhookSecret or sets it to an empty value. The forged event drives a real terraform plan of the attacker-selected branch under the operator's own stored git and cloud credentials, and code analysis indicates the resulting diff can be posted onto a genuine pull request's comment thread, exposing and misattributing another branch's infrastructure changes; auto-apply is hardcoded off for these temporary layers so the flaw alone cannot force a terraform apply. The CVSS vector is unauthenticated (PR:N) and the priority call is act_now; no CISA KEV entry appears in the supplied data, and the GitHub advisory publishes a proof-of-concept test it reports as passing against envtest.
Missing authentication in boneIO Black firmware before 1.6.0 leaves the management web API bound to all network interfaces and accessible without credentials. A network-adjacent, unauthenticated attacker can fully control the device, including causing denial of service, changing configuration, and operating connected physical circuits; no public exploit was identified at time of analysis. Version 1.6.0 adds first-run administrator setup and role-restricted API routes, while devices older than 1.2.0 require re-flashing because they are based on unsupported Debian 10.
boneIO Black home automation controllers running software before version 1.6.0 expose a Node-RED instance through their Caddy reverse proxy at the /nodered/ path without any authentication, and because the Node-RED Admin API permits deploying flows that can invoke system commands, an unauthenticated attacker who can reach the device from the adjacent network can deploy a malicious flow and obtain remote code execution with full control of the home automation system. Exploitation requires local-network adjacency (CVSS AV:A) rather than internet exposure, and no credentials, tokens or user interaction are needed against the default configuration; devices updated to 1.6.0 or later are not affected. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; it was reported by CERT-PL and assigned a priority of this_week, reflecting a genuine high-priority issue affecting a small-audience embedded product.
Unauthenticated path traversal combined with missing authorization in the cloud-storage source of Google MCP Toolbox for Databases (googleapis/mcp-toolbox) 1.2.0 through 1.4.0 lets a remote caller use crafted tool invocation parameters to copy arbitrary files from the host into attacker-chosen Google Cloud Storage buckets and to overwrite arbitrary local files. Every severity signal points the same way: the CVSS 4.0 base score is 9.3 with AV:N/AC:L/AT:N/PR:N/UI:N and high vulnerable-system confidentiality, integrity and availability impact, and the vuln.today decision label is act_now, so this should be prioritized immediately. No public exploit code and no CISA KEV entry were identified at time of analysis; no EPSS score was supplied. Realistic exposure is bounded by whether the toolbox endpoint is network-reachable by untrusted callers and by the GCS permissions granted to the host service account.
Authentication bypass in Fortinet FortiSandbox and FortiSandbox PaaS allows remote attackers to execute unauthorized code or commands through crafted HTTP requests. The flaw (CWE-288, alternate path or channel bypass) carries a 9.8 CVSS score with a PR:N/UI:N vector, meaning no credentials or user interaction are needed against the exposed HTTP interface; affected releases are FortiSandbox 5.0.0-5.0.6, 4.4.0-4.4.9 and 4.2 (all versions), plus FortiSandbox PaaS 5.0.0-5.0.6, 4.4 (all) and 4.2 (all). No public exploit code or CISA KEV entry is present in the supplied data, but the vendor-reported severity and the act_now priority label make this a genuine high-priority issue; internet-exposed management interfaces carry the greatest exposure.
Unauthenticated remote attackers can rewrite server environment configuration in danmu_api deployments running a version before 1.21.7 when two conditions coincide: the install still uses the shipped default TOKEN of 87654321 and the ADMIN_TOKEN environment variable is unset. In that state the system-management endpoints /api/env/set, /api/env/add and /api/env/del inherit the token-free default-TOKEN compatibility path and accept unauthenticated POST requests, letting an attacker write ADMIN_TOKEN to seize the management interface, lock out the operator, or repoint OTHER_SERVER and PROXY_URL to internal targets for SSRF and forced redeployment. The vendor addressed this in 1.21.7 by requiring ADMIN_TOKEN on those endpoints (401 when unset) and excluding them from the default-TOKEN bypass; no public exploit code was identified at time of analysis, and instances that already use a non-default TOKEN or have set ADMIN_TOKEN are not exposed.
Unauthenticated account takeover in MacCMS v10 before 2026.1000.4054 lets any remote attacker reset the password of any registered member, because the password-recovery verification routine never binds the submitted code to the account it was issued for. An attacker requests a recovery code through user/findpass_msg delivered to their own mailbox or phone, then submits that code to user/findpass_reset together with the victim's registered email address or phone number, and the reset succeeds. No authentication, privileges, or user interaction are required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, vendor score 9.3); the only prerequisites are that the member system and its code-delivery channel are enabled and that the attacker knows the victim's registered identifier. Our assessment rates this a genuine high-priority issue rather than an inflated score, and the vendor has released a patch; no public exploit code was identified at time of analysis.
Missing authorization in Frappe CRM before 1.89.1 lets an authenticated low-privileged user read CRM Lead records they are not permitted to see by supplying a known phone number to the crm.integrations.api.get_contact_by_phone_number endpoint, which resolves matches with raw database queries instead of the permission system. Any user holding a valid session and a low-privilege role (the patch's tests use a 'Sales User' account) can enumerate phone numbers to disclose lead details otherwise blocked by standard API and UI controls; no public exploit was identified at time of analysis and the issue is not in CISA KEV. Severity is high for confidentiality (CVSS 7.1 in the 4.0 scoring, with the assessed 3.1 vector at AV:N/AC:L/PR:L/UI:N/C:H) but the impact is disclosure-only and requires a known or guessed phone number per record, which keeps this a moderate-priority, patch-this-week item rather than an emergency. The vendor shipped a fix in v1.89.1.
Improper authentication and authorization controls in the CreditNirvana Collections Platform (CollectionWorkz) login service let an unauthenticated remote attacker manipulate authentication requests and reach platform APIs without a valid session - enumerating users and establishing sessions as arbitrary accounts, including administrators, with the ability to read and modify sensitive data at that user's privilege level. The flaw is scored 9.3 under CVSS 4.0 (AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact but no availability impact), and CERT-In has issued an advisory; the vuln.today priority is act_now. No public exploit code and no CISA KEV entry were identified in the available data, and the specific affected version range is not stated.
Mendix SAML modules for Mendix 9, 10 and 11 fail to block replay of SAML assertions in IdP-initiated authentication flows, allowing an unauthenticated remote attacker to gain unauthorized application access by re-presenting a valid SAML response. Three module branches are affected: the Mendix 10 and Mendix 11 compatible modules below V4.2.4 and the Mendix 9 compatible module below V3.6.29. Per the assessed CVSS 4.0 vector (7.6, High), the attack is network-reachable and requires no credentials (PR:N), but difficulty is raised by AC:H (the attacker must first obtain a valid, unexpired SAML response) and UI:P (a legitimate user's IdP-initiated authentication must occur to produce that response); no public exploit was identified at time of analysis and no KEV entry exists.
Missing authorization in YesWiki's ActivityPub outbox sync handler (ActivityPubService::syncActorPosts) lets an operator of a malicious federated ActivityPub server use a poisoned outbox to delete, overwrite, or forge wiki entries mirrored from other actors, with the administrator acting as a confused deputy. All releases from 4.6.2 through 4.6.7 are affected - 4.6.7 closed the equivalent holes in the inbox path via the GHSA-rm6r-grfg-4v78 fix but left the sync path unguarded - and the prerelease 5.0.0-alpha1 carries the same unguarded handler; version 4.7.0 contains the fix. Exploitation is conditional rather than ambient: ActivityPub must be enabled on at least one Bazar form, the instance must already hold a mirrored entry from a third-party actor, and an administrator must trigger the GET-based sync action (or be lured into it, since the action carries no CSRF token), while the attacker needs no privileges on the target instance. A proof-of-concept is documented in the upstream advisory, but it is not verified as working exploit code, and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Snipe-IT 8.6.2 and earlier can re-admit deactivated accounts - including accounts with admin rights - through the Google SSO callback, because GoogleAuthController::handleGoogleCallback logged in whichever local user matched the incoming Google email as a username without enforcing the activated flag. The exposure is gated by deployment shape: Google SSO must be enabled, the instance must use email-as-username (or the targeted account must have an email-shaped username), the Snipe-IT account must already be deactivated, and the attacker must still hold a live, unrevoked Google Workspace identity for that address. Default installations that use the firstname.lastname username format are not affected because the username/email mismatch makes the lookup return NULL; this makes the bug primarily an offboarding-window and former-insider risk rather than anonymous external compromise, and it has been assigned an act_now priority. No public exploit code was identified at time of analysis, and the issue is fixed in Snipe-IT 8.6.3 via commit 5fea2fadc0.
Signature verification bypass in rclone stable selfupdate (versions 1.55.0 through 1.75.1) lets an attacker who controls the authenticated release-distribution responses prepend an unsigned SHA-256 checksum for a malicious archive ahead of the genuine PGP-clearsigned SHA256SUMS block, causing selfupdate to accept and extract an attacker-controlled rclone executable. Exploitation requires origin, CDN, or TLS-termination compromise or trusted-certificate interception plus a user running stable `rclone selfupdate` without `--check`; the beta channel is unaffected and ordinary unauthenticated interception is insufficient. The issue is rated High (CVSS 4.0 7.7; independent CVSS 3.1 7.5), fixed in 1.75.2, is not listed in CISA KEV in the supplied data, and has a public PoC reference that demonstrates the bypass and archive extraction but does not complete installation.
An object-level authorization bypass in phpMyFAQ before 4.1.10 allows unauthenticated visitors to rewrite or, under one optional administrator setting, permanently delete any visitor-submitted open question by sending an arbitrary openQuestionID to POST /api/faq/create. The only gate in front of the endpoint is the guest-submission feature switch, which defaults to enabled; the graphical CAPTCHA the attacker must solve is an anti-automation measure, not an authorization control, and it is the main practical limit on mass abuse. In the shipped default configuration the impact is integrity-only (CVSS 4.0 8.7, CVSS 3.1 7.5): category and answer link are overwritten and a forged 'answered' entry is written to faqquestion_history; if records.enableDeleteQuestion is turned on, the same request deletes the question outright with no soft-delete and no revision trail, matching the advisory's 9.1 Critical variant. No KEV listing or confirmed active exploitation is reported, and no standalone public exploit code has been identified at time of analysis, although the advisory itself publishes a step-by-step reproduction; this should be scheduled in the current weekly patch cycle.
Missing authorization in Parse Server before 8.6.101 and 9.0.0 before 9.10.4-alpha.4 allows unauthenticated REST API clients on MongoDB deployments to delete the internal _SCHEMA collection, stripping class field definitions, class-level permissions and protected fields so affected data becomes readable and modifiable by any client. PostgreSQL deployments are explicitly not affected and object ACLs continue to apply; no public exploit has been identified at time of analysis. The vendor and independent assessment rate this high severity (CVSS 8.8, assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) and a near-term priority for MongoDB-backed installations with reachable REST endpoints; vendor patches are available for both affected release branches.
An authentication bypass in Parse Server affects 8.x releases before 8.6.102 and 9.0.0 through 9.10.5-alpha.2 when an app is configured with a custom authentication adapter written as a subclass of the exported AuthAdapter class: Parse Server never invokes the subclass's validateSetUp, validateLogin, and validateUpdate methods and instead falls back to an inherited base-class default that accepts any authData. For any provider served by such an adapter, unauthenticated remote attackers can supply arbitrary authData to sign up, link an identity, log in as an existing user, or skip a custom adapter that implements an additional authentication factor, potentially gaining full account access and integrity over affected data. Apps using built-in adapters or custom adapters defined as plain objects are not affected, and no public exploit code was identified at time of analysis; the priority label from the reporting feed is act_now, reflecting that the impact is severe for the narrower population that matches the configuration prerequisite.
Cross-organization authorization bypass in Dokploy through 0.30.10 lets an authenticated owner or admin of one organization control another tenant's applications by supplying a foreign applicationId to procedures such as saveEnvironment, updateTraefikConfig, deploy, and stop. Successful exploitation can overwrite environment variables and build secrets, repoint application sources, and disrupt other tenants' workloads. The flaw requires a multi-tenant Dokploy deployment and org-level owner or admin credentials; no public exploit has been identified at time of analysis, and a vendor fix is available via the referenced upstream commit.
Remote unauthenticated compromise of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition is possible through the JSSE component when attacker-influenced data reaches the affected APIs. The listed affected builds include Java SE 8u511-b32, 8u511-perf-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2, and 27.0.1.0.2, plus GraalVM for JDK 17.0.21.0.2/21.0.13.0.2 and GraalVM Enterprise Edition 21.3.20.0.2. Per the assessed CVSS vector AV:N/AC:L/PR:N/UI:N, exploitation is remote, unauthenticated, and requires no user interaction on the API path, with high confidentiality and integrity impact and no availability impact; no CISA KEV entry, public exploit code, or EPSS score was supplied, and the vuln.today decision label is act_now.
Improper token-purpose validation in Postiz (gitroomhq/postiz-app) through v2.25.2 allows any authenticated user holding a low-privileged account to obtain a validly signed token containing claims of their choosing, which the application then accepts interchangeably as a session, an organization invitation carrying a chosen role, a password reset, or an enterprise provisioning token. The primary path is the browser-extension channel credential-refresh route, which signs attacker-supplied data taken from the request itself with the shared token-signing secret and stores the signed result where the requesting user can read it back; a second, narrower team-invitation creation route signs extra request-body fields in the same way. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, but the vendor rates the issue critical (CVSS 9.9, scope changed) and the priority label is act_now, with upgrading to v2.25.3 stated as the only complete fix.
Unauthenticated remote attackers can read protected information from WordPress sites running the Knit Pay UPI QR Code Payment Gateway for WooCommerce through version 1.6.3 because a plugin endpoint lacks authorization checks (CWE-862). The flaw is rated CVSS 7.5 with confidentiality-only impact (C:H/I:N/A:N) and requires WooCommerce plus the named plugin to be installed and active. No CISA KEV entry or public exploit code is present in the supplied intelligence, and exposure is limited by the plugin's niche UPI payment deployment footprint.
An allowlist bypass in Grav CMS 2.0.15 through 2.2.12 lets an authenticated account holding page-edit permission (api.pages.write, or admin.pages in the classic admin) invoke arbitrary public static PHP methods by smuggling a data-*@ directive past Grav's Class::method allowed-callable check inside a page-authored Flex form override; methods such as Folder::delete, Folder::move, Folder::copy or Utils::download can then delete directories, move or overwrite files, and read files outside the page tree. The crafted directive fires when the page's Flex form is built, for example when an administrator opens the page on the site, so the payload is planted by the lower-privileged editor and executed in an administrator's request. The vendor shipped a complete fix in 2.2.13; the earlier 2.2.2 patch (GHSA-9rq7-4cch-f22j) only closed the replace-name@ spelling and leaves installations exploitable, and no public exploit code was identified at time of analysis.
Row-level data-scope enforcement in yudao-cloud through 2026.09 can be switched off by any authenticated tenant user who sends a 'data-permission-enable: false' header on requests to /admin-api (and /app-api), letting them read or modify records belonging to other departments and users inside the same tenant. The flaw is a trust-boundary error (CWE-807): DataPermissionRpcWebFilter honours that header on every request path instead of only on internal /rpc-api calls, so no special configuration, user interaction, or elevated role is needed beyond a valid account. Rated High at CVSS 4.0 7.1 (assessed 3.1: AV:N/AC:L/PR:L/UI:N/C:H/I:L/A:N); no public exploit code was identified at time of analysis, though a third-party technical writeup of the header bypass is referenced, and the vendor has published an upstream fix commit.
Authentication bypass in the asVereinbase WordPress plugin before 1.1.8 allows unauthenticated remote attackers to log in as any user, including an administrator, because the plugin accepts an empty stored password or second-factor value as a match. Affected are WordPress sites running the plugin at versions below 1.1.8; the CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact, and no special configuration or user interaction is required. A public PoC reference exists but is not verified as working exploit code, and the EPSS score is low at 0.19% (8th percentile) even though the vuln.today decision label is act_now, so the severity and priority signals are split and should be read together.
OpenReception appointment booking software 2.1.0 and earlier lets remote attackers brute-force a returning client's six-digit booking PIN inside a targeted tenant, because the PIN throttle record is keyed on a tenant-independent email hash and its tenant_id is fixed by whichever tenant first logged a failure, so the victim tenant's challenge check never matches the row and never returns 429. A successful guess yields the client's booking access token, exposing their end-to-end-encrypted appointment tunnel and allowing appointments to be added or cancelled as that client. No vendor patch is available at time of analysis, and the published advisory includes step-by-step reproduction detail plus measurements of roughly 79 guess round-trips per second locally; the generic 20-requests-per-2-seconds IP limiter can be sidestepped by rotating the unvalidated x-forwarded-for header.
WireGuard in Zephyr (subsys/net/lib/wireguard) accepts an unauthenticated transport-data datagram and copies its source address into peer->endpoint, letting any host that can reach the listener's UDP port 51820 off-path redirect all subsequent handshake initiations, keepalives and encrypted tunnel traffic to an address of the attacker's choosing. Affected builds are Zephyr 4.4.0 through 4.4.2 with CONFIG_WIREGUARD enabled, which is marked experimental and off by default, and the defect fires only while the targeted peer has no valid handshake and no current keypair - the state at boot and after a session expires. The result is persistent tunnel denial (assessed A:H) and limited confidentiality loss (C:L) through traffic-metadata observation or selective dropping if the attacker relays redirected initiations; the Noise/AEAD cryptography prevents decryption or forgery, so keys are not compromised. The advisory's original report includes a 16-byte datagram recipe as a proof of concept; it is not verified as working exploit code, no public exploit is confirmed in use, and KEV status is not indicated - exploitation requires only UDP reachability to the listener, with no credentials or user interaction.
Privilege escalation in Tandoor Recipes before 2.7.0 lets any authenticated user obtain admin-level authorization inside a space where they only hold guest or user rights, by priming a per-user permission cache while their own self-created space is active. The flaw is in has_group_permission(), which caches group names under GROUP_CACHE_<user id> with no active-space component and re-sets the 30-second TTL on every request, so cached admin groups from space A keep answering checks after switch_user_active_space() moves the session into victim space B - and group revocations or demotions never take effect while the user stays active. Rated CVSS 4.0 7.1 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N); exploitation needs a multi-space deployment, an authenticated account, and - on multi-worker installs using the default per-process LocMemCache - the escalated request must land on the worker that primed the entry. Not listed in CISA KEV, but the vendor advisory documents a verified proof-of-concept harness against the real functions, so the technique is fully public and reproducible.
OpenID Connect login in Goobi viewer 25.01 through 26.04 validates the JWT audience outside the cryptographic verifier, so an ID token minted for a different relying party on the same identity provider can be replayed to the viewer's authentication endpoint and log the attacker in as that token's subject. Only deployments that have opted into OpenID authentication and share an IdP/issuer with at least one other relying party are exposed; array-valued aud claims fail closed and single-RP setups are described by the vendor as not practically exploitable, and the viewer's per-login nonce/state binding narrows the window further. There is no KEV entry and no public exploit identified at time of analysis, but a fixed release (26.05) and the upstream commit are both public. EPSS was not supplied in the input.
Goobi Viewer deployments that leave webapi.authorization.token unset accept an empty ?token= value on every @AuthorizationBinding-protected REST endpoint, allowing an unauthenticated caller to invoke protected API methods. The official install guide generates a UUID token, so only installations that skipped that bootstrap step - typically test, staging, CI, or container images - are exposed; on those, an attacker can delete Solr records, read operational statistics and cache data, and, where the client-applications feature is used, read client secrets and grant a client access to restricted content. The issue is fixed in version 26.05, and no public exploit was identified at the time of analysis.
Goobi viewer 24.03 through 26.04 exposes the DownloadTaskEndpoint WebSocket at /tasks/download/monitor.socket to unauthenticated users, so a remote attacker can drive the server's download machinery without credentials (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). Depending on network reachability, that yields server-side request forgery against internal hosts such as the local Solr instance or cloud instance-metadata endpoints, retrieval of local files whose extensions fall inside the application's allow-list, and deletion of the Solr index through the Core Admin UNLOAD action, which leaves the viewer unavailable until a full re-index. The vendor scored the issue 9.8, while the independent assessment keeps the unauthenticated network vector but lowers integrity impact from high to low; no public exploit identified at time of analysis. Vendor-released patch: 26.05.
Memory-note lifecycle tooling in obsidian-tc 1.0.1 through 1.31.3 can overwrite the entire body of an Obsidian vault note it does not own, and can leave the SQLite memory graph half-committed when a filesystem step is refused. An authenticated caller holding memory-write scope (write:memory) that invokes create_entity, link_entities, rename_entity, unlink_entities or delete_entity on a (type, name) pair whose computed memory/<type>/<name>.md path is already occupied by a hand-authored note or a foreign orphan will have that note's body regenerated from SQLite, with only its frontmatter preserved; delete_entity still requires its own deletion permission and destructive confirmation, which this flaw does not bypass. The maintainer found and fixed the class in 1.31.4 (PR #978, GHSA-r3g7-r4hr-m258); no public exploit identified at time of analysis, and the issue is rated this_week priority rather than an emergency because exploitation depends on already-granted memory-write permissions.
obsidian-tc 1.13.0 through 1.31.3 lets an authenticated client complete destructive, dispatch-gated Obsidian vault operations (delete, cross-folder move, frontmatter replace, link rewrite) even after the human explicitly declined or cancelled the human-in-the-loop confirmation, or after the elicitation response was omitted or malformed. The server treats a validly bound requestState echoed on resubmission as proof of approval, but that state is minted before the elicitation leg is ever asked, so it only proves the resubmission belongs to the same call; exploitation requires a Streamable HTTP deployment with auth.jwtSecret configured, a 2026-07-28-era client declaring elicitation.form support, and a tool marked destructive:true or carrying a human-in-the-loop scope floor. Only client-driven HTTP deployments are affected - stdio or jwtSecret-unset installs fall back to the CLI elicit_token path and never offer the round trip - and there is no public exploit identified at time of analysis (no CISA KEV listing), though the advisory notes the underlying construction was reproduced directly by the maintainers.
Authorization bypass in Apache Vysper's XEP-0077 In-Band Registration implementation allows any authenticated user to compromise other accounts on the XMPP server. All versions are affected, the project is retired and unsupported, and the vendor does not plan to release a fix; no public exploit was identified at time of analysis. The vendor's stated remediation is migration to an alternative XMPP server.
DJI CrystalSky ZS600C firmware 0.3.9.7 through 0.6.6.9 exposes an unauthenticated adbd shell to anyone with physical USB access because the device ships with ro.adb.secure=0 and USB ADB enabled. An attacker can obtain a uid 2000 shell as a foothold for a separate privilege-escalation step to root; ADB over TCP is not enabled by default, but when enabled out-of-band the same unauthenticated shell is reachable over the network. No public exploit was identified at time of analysis and there is no CISA KEV entry; the assessed CVSS 3.1 score is 7.0 (AV:P) because the default path requires physical access, while the reported CVSS 4.0 base score is 9.3.
Local apps on DJI CrystalSky ZS600C devices can invoke system-privileged actions-including a factory reset that wipes user data, shutdown, clock/timezone changes, and a firmware-apply hand-off-because the DJIUpdateService binder does not verify caller identity or permissions. The flaw affects firmware v0.3.9.7 through v0.6.6.9 and is reachable by an installed app with no permissions and no user interaction. No public exploit has been identified at time of analysis; the issue is access-gated to local code execution on the specific device but warrants this-week prioritization because successful abuse is destructive and disruptive.
Missing authorization in DJI CrystalSky ZS600C firmware v0.3.9.7 through v0.6.6.9 allows a local application with no Android permissions to invoke binder transaction 1018 on android.dji.server and execute arbitrary OS commands as root through the root-privileged assistant daemon. The attack is local only and requires the ability to run code on the physical device; no public exploit has been identified at time of analysis. The reported CVSS 4.0 base score is 8.6 (High), and the independent CVSS 3.1 assessment is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Missing authorization in Zimbra Collaboration Suite 10.1.16 and 10.1.20 allows an authenticated delegated administrator holding no explicit administrative grants to overwrite the global Zimlet configuration through ConfigureZimletRequest. The injected configuration can add an attacker-controlled domain to the proxy allowlist of the default class of service, so a signed-in user in that class who opens a crafted /service/proxy URL is served attacker-controlled HTML from Zimbra's own origin, letting the resulting JavaScript read mailbox data and act as the victim. The admin-side escalation is remote and low-complexity but requires a delegated-admin account with admin SOAP service access (PR:L), and the browser compromise requires the victim to open the crafted URL (UI:R); no public exploit code has been identified at time of analysis, no KEV entry is present, and the vuln.today priority label is this_week rather than emergency.
Local io_uring CONNECT BPF filter bypass in Linux kernel 7.2 and 7.3 lets a low-privileged process reach AF_INET6 destinations that an administrator-configured filter intended to deny. The bug is a length-threshold mismatch: at addr_len 24 (SIN6_LEN_RFC2133), io_connect_bpf_populate() leaves connect.port and connect.v6_addr zero while the kernel connects to the real destination, so filters that deny specific IPv6 ports or addresses are bypassed. The upstream commit describes a verified reproducer; no CISA KEV active-exploitation listing is provided, EPSS is low at 0.21% (11th percentile), and the assessed impact is limited confidentiality/integrity loss rather than remote compromise.
Any account holding the lowest 'member' role in a PraisonAI Platform workspace can permanently delete projects, agents, issues, labels, issue dependencies and issue-label attachments created by the workspace owner or by other members, because all six content DELETE endpoints verify workspace membership but never verify resource ownership or an owner/admin role. The flaw affects praisonai-platform from 0.1.4 up to the fix and scores CVSS 8.1 (AV:N/AC:L/PR:L/UI:N/C:N/I:H/A:H), since an authenticated low-privileged user can destroy integrity and availability of workspace content while confidentiality is untouched. Exploitation requires a valid member account inside the targeted workspace - either invited by the victim or obtained through a compromised member credential - so the practical exposure is an insider or account-takeover scenario rather than a mass internet threat; there is no CISA KEV entry, no EPSS signal supplied and no confirmed working exploit package, though the vendor advisory publishes a full step-by-step reproduction.
Unauthenticated remote agent invocation in PraisonAI LinearBot 4.6.56 through 4.6.58: because LINEAR_WEBHOOK_SECRET is treated as optional and defaults to an empty string, the aiohttp webhook listener bound to 0.0.0.0 skips Linear-Signature HMAC verification entirely, so any network caller who can reach the endpoint can POST a forged 'Linear-Event: AgentSession' request that is parsed, backgrounded, and dispatched into BotSessionManager.chat(), causing the bot to run the configured agent and post comments back to Linear under the bot token. Exploitation requires the operator to have started LinearBot with a Linear token but without a webhook secret, and the listener to be reachable; deployments that do set the secret reject missing and invalid signatures with 401 before dispatch. A public proof-of-vulnerability harness exists that exercises the handler offline and monkey-patches the outbound comment path; it is not verified as working exploit code against deployed instances, and there is no confirmed active exploitation (no KEV entry).
PraisonAI versions 4.5.112 through 4.6.58 expose the Recipe HTTP API without authentication when an operator starts the deprecated Typer command `praisonai recipe serve` on a non-localhost interface without explicitly selecting API-key auth, allowing unauthenticated network callers to enumerate and execute recipes and, when `--admin` is enabled, invoke `/admin/reload`. The issue is an authentication bypass at the installed Typer callsite (CWE-287, with CWE-306 and CWE-862 also applicable); the hardened legacy feature handler rejects non-localhost binding without auth, and `create_auth_middleware()` fails closed with 503/401 when auth is selected but misconfigured. The CVSS 3.1 base score is 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N), and PraisonAI 4.6.59 contains the vendor fix; no CISA KEV entry or confirmed working remote exploit code is present in the supplied intelligence, and the advisory's public local-only proof-of-value harness exercises the bypass in-process without binding a socket, so it is not verified as working remote exploit code. Given the this-week decision label, prioritize upgrading internet-reachable or Docker-deployed instances.
Slack app_mention events in the PraisonAI bot (PyPI package praisonai, versions 3.11.0 through 4.6.58) skip the allowed_users, allowed_channels and unknown_user_policy checks that the normal message handler enforces, so any Slack workspace member who can mention the bot in a channel where the app is installed can drive the configured agent even when the identical event content is dropped by the message path. The root cause is missing authorization (CWE-862, also tracked as CWE-863) in src/praisonai/praisonai/bots/slack.py, and the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L (8.3, High) - network reachable, low complexity, and authenticated, since the attacker must already hold Slack workspace membership and be able to mention the bot. A public PoC reference exists in the form of a local-only harness that mocks Slack Bolt and the Slack SDK in-process and does not connect to Slack; it is not verified as working exploit code against a live deployment, and there is no confirmed active exploitation (no CISA KEV listing). Remediation is prioritized as this week rather than an emergency.
Missing authorization in the BlueSpiceUserManager extension of BlueSpice (5.0.0 through 5.1.10 and 5.2.0 through 5.2.6) lets any authenticated user, with no special privileges, block or unblock arbitrary accounts including administrators through the /bs-usermanager/v1/block/create and /bs-usermanager/v1/block/delete REST endpoints. Successful abuse can lock every administrator out of the wiki (denial of service) or silently lift blocks that administrators imposed, altering the integrity of account state. Exploitation requires a valid registered account plus network reach to the REST API, and the extension must be installed and enabled; where self-registration is open the barrier is negligible, otherwise the realistic attacker set is insiders. No public exploit code was identified at time of analysis.
WPMobile.App (wpappninja) WordPress plugin versions through 11.86 expose an unauthenticated missing-authorization weakness that can disclose sensitive information to remote attackers. The flaw is rated CVSS 7.5 with confidentiality-only impact, and no public exploit was identified at time of analysis. Sites running the affected plugin are exposed when the vulnerable plugin functionality is reachable.
Authentication bypass in WizLearn LMS, rated CVSS 9.8, allows an unauthenticated remote attacker to circumvent both password-based login and the OAuth flow with a crafted POST request, potentially taking over user accounts and gaining administrative control of the platform. The affected release range is not established in the available data because the CPE version is a wildcard, so organizations should confirm vulnerable versions against the CSA advisory. No public exploit identified at time of analysis.
Improper authentication in ASUS router firmware lets an unauthenticated attacker on an adjacent network-such as an associated Wi-Fi client or a device on the same LAN segment-send an HTTP request, forge an access ticket, and perform administrator operations. The affected router models and firmware versions are not specified in the available data, which uses a wildcard CPE for ASUS routers, and no public exploit has been identified at time of analysis. The issue is rated 8.7 and is prioritized this week.
Unauthenticated credential takeover of non-administrator WordPress accounts is possible in ACF Extended and ACF Extended PRO before 0.9.2.8 through the front-end Forms module's update-user action. The plugin checks authorization only when the targeted account is an administrator, so a visitor can overwrite another non-admin user's credentials and obtain a session for that account when a published form maps the target user to a visitor-submitted value instead of the default current user. The flaw is remotely reachable without authentication or user interaction but is conditional on that non-default form configuration; no public exploit was identified at time of analysis and the vendor has released a patch.
Privilege escalation in Okta Access Gateway allows an already authenticated user with an active session to obtain Admin Console access by altering the authentication-source parameter during sign-on, which OAG fails to validate before issuing a SAML assertion. Okta rates the flaw 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), while our assessment adjusts the privilege requirement to PR:L because valid credentials and a live session are mandatory; the AC:H metric reflects that the parameter manipulation is not trivial to perform reliably. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, but successful abuse grants administrative control of the gateway, so it warrants prompt patching on this week's cycle rather than emergency action.
Authentication bypass in the public registration form of onPhase/frevvo Forms 11.0.14 allows an unauthenticated remote attacker to impersonate an existing tenant user, obtain TenantAdmin and Designer privileges, and execute arbitrary operating system commands. Exploitation requires the public registration endpoint to be reachable and the attacker to supply a valid tenant name and an existing user identifier; no credentials or user interaction are required. The vuln.today decision is act_now, and no public exploit identified at time of analysis.
Remote, unauthenticated attackers can change the hostname, DNS servers, and NTP time source on Kiloview E3 NDI encoder firmware before 1.30 through the ONVIF device service, even when authentication is enabled for that service (CVSS 8.7). The flaw is an authentication bypass for configuration write operations (CWE-306) with high integrity impact but no direct confidentiality or availability impact; exploitation requires network reachability to the ONVIF service. No public exploit identified at time of analysis, and the vendor provides a firmware update.
Kiloview E3 NDI encoder firmware before version 1.30 signs session JSON Web Tokens with a single HMAC-SHA256 secret that is hardcoded in the firmware image and shared across every deployed device. Because the firmware is publicly downloadable from the vendor, anyone can extract that secret and forge valid session tokens, including administrative ones, then reach privileged device functions over the network without any credentials and without user interaction. The flaw is remotely exploitable and high impact for confidentiality, integrity and availability in our assessment; no public exploit code or confirmed active exploitation was identified at time of analysis, though the underlying technique requires only offline extraction of a static string plus network reachability to the authentication endpoint. Kiloview has released fixed firmware 1.30, and the vendor advisory (ICSA-26-295-01) is available.
Privilege escalation in Microsoft VM Inspector for Azure Virtual Machines allows unauthenticated, network-reachable attackers with no user interaction to gain elevated privileges, and the vendor scores it CVSS 10.0 with a scope change (S:C) indicating impact extends beyond the initially vulnerable component. The root cause is a link-following defect (CWE-59): the component resolves a link before accessing a file, so an attacker who can influence a symbolic link or junction can redirect privileged file operations. Microsoft has published a fix through its MSRC update guide and the vuln.today priority is act_now; no public exploit code or CISA KEV entry was identified at time of analysis.
Privilege elevation in Azure Kubernetes Configuration Service is possible for unauthenticated network attackers because a critical function lacks authentication, and the CVSS 3.1 base score is 10.0. Because the service is Microsoft-managed, real-world exposure depends on network reachability to the vulnerable endpoint and on whether Microsoft has already completed server-side remediation; no customer-side non-default configuration is stated as required. Vendor patch information is available and the vuln.today priority label is act_now; no public exploit identified at time of analysis.
Improper authentication in Microsoft Entra Application Proxy (formerly AAD App Proxy) allows an unauthenticated, remote attacker to elevate privileges across a trust boundary, with the supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) scoring 10.0 - no privileges, no user interaction and low complexity, with high confidentiality and integrity impact and a scope change. Exposure is deployment-specific: the target organization must actually run Application Proxy to publish internal applications for remote access, and the proxy endpoint must be reachable by the attacker; organizations not using the service are not exposed to this flaw. Microsoft is the reporting party and a vendor patch is available per the MSRC update guide, and the vuln.today decision label is act_now; no public exploit code or confirmed active exploitation was identified in the supplied data, although the trigger conditions themselves are not described in the available sources.
Token forgery in the Authlib Python library before 1.9.1 lets a remote, unauthenticated attacker mint HS256, HS384 or HS512 tokens carrying arbitrary claims that Authlib accepts as genuinely signed, whenever the deploying application's HMAC verification key resolves to an empty string or empty bytes (for example an unset environment variable defaulted to '', a config column defaulting to '', or a key-resolver returning '' on a lookup miss). The exposure is strongly gated by that deployment precondition: applications that always supply a non-empty secret are not exploitable, and asymmetric RS/ES verification paths are unaffected, which is why the vector carries AC:H rather than a universally applicable rating. No public exploit code has been identified at time of analysis (the advisory supplies a prose reproduction description rather than weaponized code), CISA KEV does not list this issue, and the vendor has released 1.9.1 as the fix.
Authentication bypass in Authlib's deprecated-but-still-shipped authlib.jose module (1.3.1 through 1.8.0, fixed in 1.9.0) lets an unauthenticated remote attacker forge HS256 JSON Web Tokens with arbitrary subject and role claims using nothing but the issuer's public key, because the OctKey.import_key() guard tests for PEM armour only at byte zero while the PEM loaders skip leading whitespace, comment lines or a BOM. Two non-default deployment properties are required: the relying party uses the documented module-level jwt object (whose registry mixes HS* with RS*/ES*/PS*/EdDSA and whose decode exposes no algorithms parameter), and the verification key is stored as PEM or X.509 certificate text that does not begin at offset 0 with '-----BEGIN ' - a canonical PEM is still blocked, and pinning the algorithm (e.g. JsonWebToken(['RS256'])) is confirmed to reject the forgery. Rated CVSS 7.4 (AV:N/AC:H/PR:N/UI:N, C:H/I:H) and not listed in CISA KEV; the upstream advisory includes an end-to-end proof-of-concept reproduction against 1.8.0.
An authenticated administrator of an HPE networking product can reach a low-complexity, network-exposed flaw and achieve full confidentiality, integrity and availability impact on the affected component, according to an HPE security bulletin (document HPESBNW05162) scored at CVSS 3.1 base 7.2. The vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H confirms the issue is remotely reachable with no user interaction, but the high-privilege prerequisite (PR:H) means only an attacker who already holds an administrative or otherwise privileged account on the device can exploit it, so the realistic exposure is an insider, a compromised administrative credential, or a post-exploitation step, not anonymous internet attack. No public exploit code or proof-of-concept is referenced in the supplied sources, and the specific affected product, version, feature and protocol are not described in the available data.
Project isolation bypass in Incus lets an authenticated client that is confined to one project copy and read custom storage volumes belonging to any other project on the same server, including volume snapshots and configuration. The flaw affects Incus 7.0.1 (fixed in 7.0.2) and 7.2.0 through 7.4.x (fixed in 7.5.0), and is reachable only through a hand-crafted POST to /1.0/storage-pools/{pool}/volumes/custom that supplies a source volume with an attacker-chosen source.project while omitting source.type - the official Incus client always sets source.type=copy and therefore cannot trigger it. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation requires legitimate low-privilege credentials holding can_create_storage_volumes in at least one project, so impact is concentrated on multi-project servers where project isolation is the actual security boundary.
Incus servers that use multi-project tenancy expose in-flight operations across project boundaries because the GET /1.0/operations/{uuid} handler performs no authorization check, letting any authenticated client - including one holding a TLS certificate restricted to a single project - read operations that belong to other projects. The disclosed data includes the full command line, the process environment (where deployment tooling typically stores database passwords, API tokens and cloud credentials), the operation's websocket fd secrets and resource URLs, and, when an 'incus config trust add' operation happens to be pending, the trust-enrolment token itself, which the reporter demonstrated could be exchanged for an unrestricted certificate and full server admin. Exploitation is constrained: the attacker must already hold a project-restricted certificate and must obtain the 122-bit crypto/rand UUIDv4 of a specific in-flight operation out of band, since Incus discloses no enumeration path to a restricted client. The issue carries no CISA KEV entry or reported active exploitation; the upstream advisory includes a step-by-step reproduction sequence, which is the only published proof of concept.
Argument injection in Incus 7.3.0 through 7.4.x lets a user confined to a restricted project smuggle the forbidden block.create_options setting onto a custom volume, then trigger a copy or move onto a storage pool that formats new volumes, so the injected value is appended to the mkfs command line executed as root. The flaw is an incomplete fix for CVE-2026-62867, which only rejected the option on the direct custom-volume creation path while leaving update, copy and move operations unchecked; the package range is go/github.com/lxc/incus/v7/cmd/incusd >= v7.3.0, < v7.5.0. Exploitation requires an authenticated restricted-project user with permission to create or edit custom volumes, and root-level code execution only materialises on pools that format on copy such as non-thin LVM - on other drivers the forbidden option lands on the volume config without reaching mkfs. No public exploit code was identified at time of analysis, but the weakness class is straightforward and the priority signal is act_now given the root-level outcome on affected storage backends.
Cross-namespace privilege escalation in OpenBao 2.3.0 through 2.6.2 allows an authenticated token holder to attach specially crafted policy names and thereby gain capabilities from policies cached in other namespaces, including the root namespace. The ACL policy cache does not keep cached policies scoped to their namespace, so the token can act across namespace boundaries; the referenced policies must already be in the in-memory LRU cache at both token creation and token use, and a referenced foreign root policy is granted only within the token's own namespace, which limits reliability and impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and multi-tenant deployments that depend on namespace isolation are the primary concern; fixed releases are 2.6.3 and 2.7.0.
Integrity-only NoSQL injection in the MongoDB C# Driver update-statement builder allows an authenticated application user with ordinary read-write access to influence update logic, potentially modifying or deleting stored data the application did not intend to change. The flaw is tracked as CSHARP-6168 and affects releases before 3.13.0; exploitation depends on the application passing attacker-influenced values directly into the affected update builder surface, so it is not reachable against a hardened application that does not do so. No public exploit was identified in the provided intelligence at time of analysis, and the primary remediation is upgrading to MongoDB .NET/C# Driver 3.13.0.
Roskus Prospero Flow CRM versions 2.0.0 through 5.25.x ship user API routes (GET and DELETE /api/user/{id}) protected only by the auth:api middleware, which validates the JSON Web Token and performs no permission, policy or role check, so any holder of a basic-role account can read the account records of other users in the same company - including administrators and their email address, telephone number, postal address and IBAN - and, from 3.5.0 onward, delete those accounts. Exploitation requires a valid authenticated account (PR:L) and, for deletion of accounts outside the attacker's own company, membership in Company::DEFAULT_COMPANY (company ID 1), where the company comparison is skipped entirely; an account in that company can delete any account of any company, including a company's last administrator, and deletion removes the data held on the account. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vulnerability is tracked with an assessed CVSS 3.1 base of 8.6 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and is prioritized for remediation this week.
Cross-tenant data access in SmileCDR HAPI FHIR allows an attacker who holds valid credentials for one tenant in a multi-tenant deployment to read from or write to another tenant's storage partition by submitting an untrusted bundle body that replaces a trusted partition identity; storage partition entitlement is not enforced by default. Exploitation requires authenticated access to at least one tenant, and single-tenant deployments or those with partition entitlement enforcement enabled are less exposed. No public exploit identified at time of analysis, and this is a genuine priority rather than an inflated high-CVSS issue, though not a drop-everything emergency.
Canonical Juju 4.0 through 4.0.15 leaves the model unit-resources download route without an authorization check, so any principal already authenticated to the controller - a unit agent, or a human user holding only 'login' permission with no access to the target model - can request an arbitrary unit in an arbitrary model and read that application's charm resources, including container-registry credentials. The fix in Juju 4.0.16 binds the unit named in the request URL to the authenticated identity, refusing cross-unit and cross-model access. No public exploit code was identified at time of analysis, and the flaw requires a valid controller credential, though one at the lowest privilege tier and against default deployments.
Unauthenticated OAuth state values can be redeemed as Magic Link tokens in Better Auth 1.4.0-beta.18 through 1.7.6, letting an attacker who knows a victim's email address obtain a full session for that account without mailbox access or completing the provider callback. The flaw only applies to deployments that enable the Magic Link plugin with plain token storage (or hashed tokens plus globally hashed verification identifiers), enable a built-in social or Generic OAuth provider, and use database-backed OAuth state - the default when a database or secondary storage is configured. Successful abuse yields an existing user's session with all its permissions, or, when Magic Link sign-up is enabled, a new account incorrectly flagged as email verified; no public exploit code has been identified at time of analysis, but the vendor advisory and a public fix commit fully document the technique.
Authorization bypass (CWE-639) in the MarcosCamara01 Ecommerce Template lets any authenticated shopper delete or change the cart and wishlist rows that belong to other accounts on the same installation, because the Drizzle repository calls match rows on the primary key alone and the per-user PostgreSQL row level security policies never take effect for the application's connection. Affected deployments are those using the template's default single-DATABASE_URL setup, where the migration role that creates the tables is also the runtime role, so PostgreSQL does not apply RLS to the table owner; cart_items.id and wishlist.id are sequential bigserial values, making other users' row identifiers enumerable, and the update path returns the modified row including its owning user_id. A valid low-privileged account on the target is required and no user interaction is needed; no public exploit identified at time of analysis, and vendor-side code addressing both the RLS enforcement gap and the missing ownership predicates is available in the referenced commit.
Authentication bypass in Silicon Labs Connect SDK 4.3.1 and earlier, plus Flex SDK 3.7.7 and earlier, allows an attacker positioned within radio range of the device to send a protocol message carrying invalid security settings that the stack fails to verify, causing the message to be processed as though it came from a trusted source. Successful exploitation disrupts network operation (high integrity and availability impact) but cannot recover the Network Key or decrypt traffic, so confidentiality is explicitly unaffected. The trigger is unauthenticated, low complexity, and requires no user interaction, though the attacker must be within adjacent-network/radio range and cannot reach the device over the internet; no public exploit code or active exploitation is identified in the available data, and patch is available from the vendor.
An authorization bypass in Lotus (uselotus/lotus) through 0.10.2 lets a self-registered, authenticated user switch into a different tenant by POSTing that organization's UUID to /app/switch_organization/, after which the victim tenant's data and billing configuration become reachable. Access is not unrestricted: the attacker must obtain the target organization's random, non-guessable UUID out of band, which is the main practical barrier and the reason the vector carries AC:H/AT:P despite the low-privilege (PR:L) requirement. Exploitation status is not confirmed in the available sources - no CISA KEV entry and no verified working exploit code were provided, though a public technical writeup reference is linked; priority is 'this_week', i.e. a genuine but not drop-everything issue, and no fixed version is listed in the available data.
Improper authentication in the Go event-ingestion middleware of uselotus Lotus through 0.10.2 lets unauthenticated remote attackers submit usage events to POST /api/track/ on behalf of another organization, corrupting that tenant's metered usage and billing records. The flaw is integrity-only (no data disclosure or availability impact) and exploitation hinges on knowing or obtaining a valid API key prefix, since the secret half of the key is never compared against the stored hashed_key; the sources do not explain how a prefix would be leaked or enumerated. No public exploit code was identified at time of analysis and the vulnerability is not in CISA KEV, though VulnCheck reporting and a public technical writeup give the issue a this_week remediation priority; the blast radius is narrow but the defect is a genuine authentication bypass.
Unauthenticated remote users may be able to read protected data from WordPress sites running ACF Extended through 0.9.2.7 because the plugin does not enforce an authorization check in some access-controlled functionality (CWE-862). The CVSS 3.1 score is 7.5 with confidentiality-only impact and no integrity or availability effect; the exact endpoint and configuration state required are not described in the available sources. Patchstack reported the issue, no CISA KEV entry is present, no public exploit identified at time of analysis, and vuln.today places it in the this_week priority tier.
Authentication bypass by spoofing in Brainstorm Force's SureCart WordPress plugin affects versions through 4.9.5 and, per the CVSS vector, is reachable over the network without authentication or user interaction, with high confidentiality, integrity, and availability impact. The exact spoofing mechanism and any required configuration are not described in the supplied sources, and no public exploit was identified at time of analysis. The vuln.today priority is act_now.
Royal MCP, a WordPress plugin, issues preview-link tokens that are not bound to the single preview they were created for; in versions before 1.5.7 any party holding a valid token is authenticated as the token's owning user - an administrator in a default install - across the entire REST API without a nonce check, enabling full site takeover. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects that the hard part is obtaining such a token, and the available sources do not describe how a token is acquired or how long it stays valid, so practical acquisition difficulty is unverified. A public PoC reference exists (the WPScan entry) but it is not verified as working exploit code, and no CISA KEV listing or EPSS scoring is present in the supplied data.
Hard-coded cryptographic key in the NT OneAPP login flow enables remote attackers to decrypt captured authentication requests and recover plaintext user credentials and device information. The issue affects NT OneAPP from NewType Infortech (CPE version wildcard, so all versions unless the vendor states otherwise); exploitation requires the attacker to first obtain encrypted login traffic, which is why the independent assessment rates attack complexity high despite the unauthenticated network vector. No public exploit was identified at time of analysis, and no CISA KEV entry is associated with this CVE.
Authentication bypass in Obot's CLI login flow before 0.26.0 lets an unauthenticated remote attacker obtain a victim's non-expiring API key by choosing a token request ID and persuading a signed-in user to complete the crafted login link, resulting in account takeover. The flaw is a CSRF-class weakness (CWE-352) requiring user interaction, and the stolen key remains valid until manually revoked. No public exploit code was identified at time of analysis, and CVE-2026-114662 is not in CISA KEV.
Missing authorization in OpenRemote's GatewayServiceResource lets any authenticated, non-administrative user start, stop, or query edge-gateway tunnels, opening persistent bidirectional TCP circuits into an edge gateway's network or tearing down tunnels operators depend on. All OpenRemote deployments from 1.2.0 through versions before 1.31.0 are affected, but exposure is gated on the instance actually using gateway tunneling with at least one configured edge gateway, since the vulnerable POST/DELETE tunnel endpoints must be reachable and operational. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the attacker only needs a low-privileged account (CVSS PR:L) and no user interaction, which keeps the bar low wherever tunneling is deployed.
Authorization bypass in the Grav Flex Objects plugin 1.4.0 through 1.4.16 lets authenticated, non-super users holding api.access plus either admin.pages or admin.configuration.pages read page source and frontmatter, modify content, and delete pages they are explicitly denied, because the generic /api/v1/flex-objects/pages routes enforce only directory-level admin.pages checks instead of the Pages API's api.pages.read/write and page-level permission rules. Scored 7.1 with an independent assessment of high confidentiality and high integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), the flaw is a privilege-escalation problem past intended per-page restrictions rather than an anonymous compromise path - the attacker must already hold a valid restricted admin or editor account, and super-user accounts are unaffected. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this is a moderate-priority remediation item rather than a drop-everything emergency.
TLS client-configuration reuse in Traefik Proxy 2.11.0 through 2.11.57 and 3.0.0 through 3.7.13 allows an unauthenticated client to bypass a backend service's configured root CAs, SNI/server name, and certificate verification. When one backend issues an NTLM or Negotiate (Kerberos) challenge, Traefik stores the resulting round tripper in a client-connection slot that is not keyed by ServersTransport; an attacker who arms that slot can then reach a different service over the same keep-alive connection and inherit the wrong TLS client settings, undermining trust in the downstream backend rather than in Traefik itself. Exploitation is conditional - it requires connection-reuse timing, an NTLM/Kerberos-authenticating backend, and multiple services with divergent ServersTransport TLS settings behind the same proxy - and no public exploit code or active exploitation has been identified at time of analysis; vendor fixes are available in 2.11.58 and 3.7.14.
Authentication bypass in Traefik Proxy 3.7.0 through 3.7.13 allows unauthenticated remote attackers to impersonate mTLS identities by supplying forged Ssl-Client-* headers (notably Ssl-Client-Verify: SUCCESS plus a chosen certificate subject and issuer) to the plaintext HTTP router. Exploitation is gated on a non-default configuration: the Kubernetes Ingress-NGINX provider must be in use, ssl-redirect must be disabled so the HTTP router is reachable, auth-tls-pass-certificate-to-upstream must be enabled so Traefik forwards client-supplied headers, and the upstream backend must trust those headers as proof of mutual-TLS identity. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied; the advisory (GHSA-mwrr-6hp4-pxr6) covers releases before v3.7.14.
Traefik 2.11.0 through 2.11.57 and 3.0.0 through 3.7.13 can assign an unauthenticated attacker's frontend request to a backend socket that a legitimate user preauthenticated with Authorization: Negotiate (NTLM/Kerberos), letting the attacker read or write with the victim's identity. The root cause is Traefik's globally shared backend connection pool, which does not isolate sockets bound to a particular frontend identity; exploitation requires an active victim socket and favorable pool-reuse timing, so this is a mid-to-high priority issue for deployments fronting connection-bound Negotiate backends rather than a universal emergency. No public exploit code or CISA KEV entry is identified at time of analysis, and fixed releases are 2.11.58 and 3.7.14.
Client-certificate authentication bypass in Traefik v3.7.0 through v3.7.13 lets a holder of a certificate issued by one host's client CA reach a different host that requires its own separate client CA, while that host's legitimate clients are locked out. The defect only manifests when the Kubernetes Ingress NGINX provider is enabled and mTLS client authentication (auth-tls-secret) is configured on multiple hosts whose secret names collide once dots are normalized to dashes, causing Traefik to merge the two trust pools; the independent assessment rates this CVSS 3.1 7.4-class impact (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N) because exploitability depends on that naming pattern (AT:P). No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation additionally requires the attacker to already hold a valid certificate from the colliding CA.
Unauthenticated clients can inherit a victim's NTLM/Negotiate-authenticated backend session in Traefik v3.2.0 through v3.7.13 when the experimental FastProxy connection pool is enabled, because pooled keep-alive backend connections are not pinned to the frontend client that originally authenticated. An attacker who lands on a reused connection after a victim completed a handshake can read that victim's data and perform actions as them on the backend, while the Traefik instance itself is not directly compromised. Exploitation is opportunistic and configuration-dependent: it requires the non-default experimental FastProxy pool, NTLM or Negotiate authentication on the backends, and a timing window in which the attacker is handed the victim's pooled connection; no public exploit code or CISA KEV entry was identified at time of analysis.
Access-control bypass in Traefik v3.7.13's Kubernetes Ingress NGINX provider allows unauthenticated remote attackers to reach ssl-passthrough Ingress backends protected by auth-type, auth-url, or whitelist-source-range annotations when a non-TLS entry point is exposed and the attacker knows the Ingress host. The flaw is configuration-gated-affected deployments must use the Ingress NGINX provider with ssl-passthrough Ingresses and a reachable plain HTTP entry point-and the bypass is silent because nothing is logged. No public exploit code or active exploitation is identified in the provided intelligence; upgrade to v3.7.14.
Mutual TLS enforcement in Traefik Proxy can be bypassed, allowing unauthenticated remote clients to reach routers that are configured to require client certificates without presenting one. The flaw affects builds made with the Go 1.27 toolchain, where the request TLS state can be evaluated as nil and the SNI check is consequently skipped; an attacker sends an HTTP/2 request carrying the ':scheme http' pseudo-header over the TLS connection to sidestep certificate validation. Fixed in v2.11.58 and v3.7.14, the issue is exploitable only when an mTLS-protected router actually exists and the binary was compiled with the affected Go version, so default deployments that do not use client-certificate authentication are not exposed; no public exploit code was identified at time of analysis.
Delegated 'Users Admin' accounts in WWBN AVideo before version 29.4.0 can delete, overwrite, or demote full administrator accounts by posting directly to confirmDeleteUser.json.php or userAddNew.json.php with an administrator's user ID, destroying that admin's videos and account in the process. The flaw is a server-side authorization gap: the interface already hides admin-row actions from non-admins, but the endpoints themselves never re-verified that the caller outranks the target, so a crafted request bypasses the cosmetic UI restriction. Exploitation requires an authenticated account holding the Permissions::canAdminUsers() delegated role, so anonymous visitors and ordinary users are not affected; no public exploit code has been identified at time of analysis and no EPSS or CISA KEV signal is present in the available data.
Improper access control in Splunk Enterprise 9.4, 10.0, 10.2, and 10.4 allows a low-privileged authenticated user to cross a security boundary and achieve high confidentiality, integrity, and availability impact, making the release a 9.9 severity fix. The flaw was found during Cisco's internal hardening review rather than through external reporting, and the affected ranges are 9.4 before 9.4.16, 10.0 before 10.0.11, 10.2 before 10.2.8, and 10.4 before 10.4.4. No public exploit code has been identified and there is no CISA KEV entry, but vendor patch availability combined with an act_now priority label places upgraded discipline on anyone running an unpatched instance; the trigger is not described in the available sources.
Authenticated Splunk Enterprise users whose roles include the schedule_search capability can use the scheduled search workflow to run risky SPL commands that the platform would normally block, resulting in disclosure or alteration of Splunk data or disruption of Splunk availability. The issue affects Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and is fixed in those releases. The assessed vector requires low privileges (PR:L) and no user interaction, with high confidentiality, integrity, and availability impact; no public exploit identified at time of analysis.
Cross-namespace authorization bypass in HashiCorp consul-k8s 0.42.0 and later can let an attacker with an existing low-privilege authenticated foothold obtain elevated Consul privileges through component ACL binding rules; deployments not using those rules or running releases before 0.42.0 are outside the stated affected scope. The flaw is fixed in consul-k8s 2.1.0 and 1.8.18, and no public exploit was identified at time of analysis, but the 9.9 CVSS score and act_now priority support prompt remediation.
Missing authentication in OmniRoute 3.8.50 through 3.8.51 lets an unauthenticated remote caller POST to /api/sync/tokens and mint a sync token whenever the instance runs in open mode (requireLogin=false), then spend that token against GET /api/sync/bundle to pull decrypted provider credentials and plaintext API keys - the same material /api/settings/export-json already denies to anonymous callers. The flaw is conditional: when login is enabled (the default), token issuance already required a dashboard session or the local CLI, so only open-mode deployments are reachable, which is why the assessed CVSS:3.1 vector is AV:N/AC:H/PR:N/UI:N with confidentiality-only impact (C:H/I:N/A:N) even though the vendor's CVSS:4.0 score is 8.2. Tokens minted this way were recorded as issuedBy:"open" and kept opening the bundle after login was re-enabled; version 3.8.52 fixes issuance, routing /api/sync/tokens into the always-protected tier and refusing the legacy "open" tokens. No public exploit code was identified at time of analysis and the CVE is not in CISA KEV; priority is this_week.
An authorization bypass in HashiCorp Consul's service mesh proxy registration lets an authenticated user who holds only service:write permission apply Envoy escape-hatch (custom proxy/bootstrap) configuration that is normally reserved for holders of mesh:write, effectively escalating the privileges of an existing mesh participant. Consul Community Edition before 2.1.0 and Consul Enterprise before 2.1.0 and before 1.21.19 are affected; the CVSS 3.1 score is 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), with the PR:L metric reflecting that a valid ACL token with service:write is required, so this is not anonymous remote compromise. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor states the issue is fixed in Consul CE 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19.
Unauthenticated retrieval of cached service mesh leaf certificates and their private keys affects HashiCorp Consul and Consul Enterprise 1.17.0 through 2.0.4 through the agent's service mesh leaf certificate API, which fails to enforce ACL authorization (CWE-862). A remote attacker who can reach the affected agent API can obtain the certificate and private key for services whose leaf certificates are already cached, allowing impersonation of those mesh services without a valid ACL token or user interaction. HashiCorp has released fixes in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19; no public exploit code or CISA KEV entry was identified at time of analysis, and the issue is prioritized for remediation this week.
Unauthenticated webhook forgery in the Padok Burrito Terraform Automation Collaboration Software Kubernetes operator through 0.12.0 lets anyone who can reach burrito-server's /api/webhook endpoint create or delete TerraformPullRequest custom resources with attacker-chosen Branch, Base and ID fields, provided the tracked repository's credential omits webhookSecret or sets it to an empty value. The forged event drives a real terraform plan of the attacker-selected branch under the operator's own stored git and cloud credentials, and code analysis indicates the resulting diff can be posted onto a genuine pull request's comment thread, exposing and misattributing another branch's infrastructure changes; auto-apply is hardcoded off for these temporary layers so the flaw alone cannot force a terraform apply. The CVSS vector is unauthenticated (PR:N) and the priority call is act_now; no CISA KEV entry appears in the supplied data, and the GitHub advisory publishes a proof-of-concept test it reports as passing against envtest.
Missing authentication in boneIO Black firmware before 1.6.0 leaves the management web API bound to all network interfaces and accessible without credentials. A network-adjacent, unauthenticated attacker can fully control the device, including causing denial of service, changing configuration, and operating connected physical circuits; no public exploit was identified at time of analysis. Version 1.6.0 adds first-run administrator setup and role-restricted API routes, while devices older than 1.2.0 require re-flashing because they are based on unsupported Debian 10.
boneIO Black home automation controllers running software before version 1.6.0 expose a Node-RED instance through their Caddy reverse proxy at the /nodered/ path without any authentication, and because the Node-RED Admin API permits deploying flows that can invoke system commands, an unauthenticated attacker who can reach the device from the adjacent network can deploy a malicious flow and obtain remote code execution with full control of the home automation system. Exploitation requires local-network adjacency (CVSS AV:A) rather than internet exposure, and no credentials, tokens or user interaction are needed against the default configuration; devices updated to 1.6.0 or later are not affected. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; it was reported by CERT-PL and assigned a priority of this_week, reflecting a genuine high-priority issue affecting a small-audience embedded product.
Unauthenticated path traversal combined with missing authorization in the cloud-storage source of Google MCP Toolbox for Databases (googleapis/mcp-toolbox) 1.2.0 through 1.4.0 lets a remote caller use crafted tool invocation parameters to copy arbitrary files from the host into attacker-chosen Google Cloud Storage buckets and to overwrite arbitrary local files. Every severity signal points the same way: the CVSS 4.0 base score is 9.3 with AV:N/AC:L/AT:N/PR:N/UI:N and high vulnerable-system confidentiality, integrity and availability impact, and the vuln.today decision label is act_now, so this should be prioritized immediately. No public exploit code and no CISA KEV entry were identified at time of analysis; no EPSS score was supplied. Realistic exposure is bounded by whether the toolbox endpoint is network-reachable by untrusted callers and by the GCS permissions granted to the host service account.
Authentication bypass in Fortinet FortiSandbox and FortiSandbox PaaS allows remote attackers to execute unauthorized code or commands through crafted HTTP requests. The flaw (CWE-288, alternate path or channel bypass) carries a 9.8 CVSS score with a PR:N/UI:N vector, meaning no credentials or user interaction are needed against the exposed HTTP interface; affected releases are FortiSandbox 5.0.0-5.0.6, 4.4.0-4.4.9 and 4.2 (all versions), plus FortiSandbox PaaS 5.0.0-5.0.6, 4.4 (all) and 4.2 (all). No public exploit code or CISA KEV entry is present in the supplied data, but the vendor-reported severity and the act_now priority label make this a genuine high-priority issue; internet-exposed management interfaces carry the greatest exposure.
Unauthenticated remote attackers can rewrite server environment configuration in danmu_api deployments running a version before 1.21.7 when two conditions coincide: the install still uses the shipped default TOKEN of 87654321 and the ADMIN_TOKEN environment variable is unset. In that state the system-management endpoints /api/env/set, /api/env/add and /api/env/del inherit the token-free default-TOKEN compatibility path and accept unauthenticated POST requests, letting an attacker write ADMIN_TOKEN to seize the management interface, lock out the operator, or repoint OTHER_SERVER and PROXY_URL to internal targets for SSRF and forced redeployment. The vendor addressed this in 1.21.7 by requiring ADMIN_TOKEN on those endpoints (401 when unset) and excluding them from the default-TOKEN bypass; no public exploit code was identified at time of analysis, and instances that already use a non-default TOKEN or have set ADMIN_TOKEN are not exposed.
Unauthenticated account takeover in MacCMS v10 before 2026.1000.4054 lets any remote attacker reset the password of any registered member, because the password-recovery verification routine never binds the submitted code to the account it was issued for. An attacker requests a recovery code through user/findpass_msg delivered to their own mailbox or phone, then submits that code to user/findpass_reset together with the victim's registered email address or phone number, and the reset succeeds. No authentication, privileges, or user interaction are required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, vendor score 9.3); the only prerequisites are that the member system and its code-delivery channel are enabled and that the attacker knows the victim's registered identifier. Our assessment rates this a genuine high-priority issue rather than an inflated score, and the vendor has released a patch; no public exploit code was identified at time of analysis.
Missing authorization in Frappe CRM before 1.89.1 lets an authenticated low-privileged user read CRM Lead records they are not permitted to see by supplying a known phone number to the crm.integrations.api.get_contact_by_phone_number endpoint, which resolves matches with raw database queries instead of the permission system. Any user holding a valid session and a low-privilege role (the patch's tests use a 'Sales User' account) can enumerate phone numbers to disclose lead details otherwise blocked by standard API and UI controls; no public exploit was identified at time of analysis and the issue is not in CISA KEV. Severity is high for confidentiality (CVSS 7.1 in the 4.0 scoring, with the assessed 3.1 vector at AV:N/AC:L/PR:L/UI:N/C:H) but the impact is disclosure-only and requires a known or guessed phone number per record, which keeps this a moderate-priority, patch-this-week item rather than an emergency. The vendor shipped a fix in v1.89.1.
Improper authentication and authorization controls in the CreditNirvana Collections Platform (CollectionWorkz) login service let an unauthenticated remote attacker manipulate authentication requests and reach platform APIs without a valid session - enumerating users and establishing sessions as arbitrary accounts, including administrators, with the ability to read and modify sensitive data at that user's privilege level. The flaw is scored 9.3 under CVSS 4.0 (AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact but no availability impact), and CERT-In has issued an advisory; the vuln.today priority is act_now. No public exploit code and no CISA KEV entry were identified in the available data, and the specific affected version range is not stated.
Mendix SAML modules for Mendix 9, 10 and 11 fail to block replay of SAML assertions in IdP-initiated authentication flows, allowing an unauthenticated remote attacker to gain unauthorized application access by re-presenting a valid SAML response. Three module branches are affected: the Mendix 10 and Mendix 11 compatible modules below V4.2.4 and the Mendix 9 compatible module below V3.6.29. Per the assessed CVSS 4.0 vector (7.6, High), the attack is network-reachable and requires no credentials (PR:N), but difficulty is raised by AC:H (the attacker must first obtain a valid, unexpired SAML response) and UI:P (a legitimate user's IdP-initiated authentication must occur to produce that response); no public exploit was identified at time of analysis and no KEV entry exists.
Missing authorization in YesWiki's ActivityPub outbox sync handler (ActivityPubService::syncActorPosts) lets an operator of a malicious federated ActivityPub server use a poisoned outbox to delete, overwrite, or forge wiki entries mirrored from other actors, with the administrator acting as a confused deputy. All releases from 4.6.2 through 4.6.7 are affected - 4.6.7 closed the equivalent holes in the inbox path via the GHSA-rm6r-grfg-4v78 fix but left the sync path unguarded - and the prerelease 5.0.0-alpha1 carries the same unguarded handler; version 4.7.0 contains the fix. Exploitation is conditional rather than ambient: ActivityPub must be enabled on at least one Bazar form, the instance must already hold a mirrored entry from a third-party actor, and an administrator must trigger the GET-based sync action (or be lured into it, since the action carries no CSRF token), while the attacker needs no privileges on the target instance. A proof-of-concept is documented in the upstream advisory, but it is not verified as working exploit code, and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis.
Snipe-IT 8.6.2 and earlier can re-admit deactivated accounts - including accounts with admin rights - through the Google SSO callback, because GoogleAuthController::handleGoogleCallback logged in whichever local user matched the incoming Google email as a username without enforcing the activated flag. The exposure is gated by deployment shape: Google SSO must be enabled, the instance must use email-as-username (or the targeted account must have an email-shaped username), the Snipe-IT account must already be deactivated, and the attacker must still hold a live, unrevoked Google Workspace identity for that address. Default installations that use the firstname.lastname username format are not affected because the username/email mismatch makes the lookup return NULL; this makes the bug primarily an offboarding-window and former-insider risk rather than anonymous external compromise, and it has been assigned an act_now priority. No public exploit code was identified at time of analysis, and the issue is fixed in Snipe-IT 8.6.3 via commit 5fea2fadc0.
Signature verification bypass in rclone stable selfupdate (versions 1.55.0 through 1.75.1) lets an attacker who controls the authenticated release-distribution responses prepend an unsigned SHA-256 checksum for a malicious archive ahead of the genuine PGP-clearsigned SHA256SUMS block, causing selfupdate to accept and extract an attacker-controlled rclone executable. Exploitation requires origin, CDN, or TLS-termination compromise or trusted-certificate interception plus a user running stable `rclone selfupdate` without `--check`; the beta channel is unaffected and ordinary unauthenticated interception is insufficient. The issue is rated High (CVSS 4.0 7.7; independent CVSS 3.1 7.5), fixed in 1.75.2, is not listed in CISA KEV in the supplied data, and has a public PoC reference that demonstrates the bypass and archive extraction but does not complete installation.
An object-level authorization bypass in phpMyFAQ before 4.1.10 allows unauthenticated visitors to rewrite or, under one optional administrator setting, permanently delete any visitor-submitted open question by sending an arbitrary openQuestionID to POST /api/faq/create. The only gate in front of the endpoint is the guest-submission feature switch, which defaults to enabled; the graphical CAPTCHA the attacker must solve is an anti-automation measure, not an authorization control, and it is the main practical limit on mass abuse. In the shipped default configuration the impact is integrity-only (CVSS 4.0 8.7, CVSS 3.1 7.5): category and answer link are overwritten and a forged 'answered' entry is written to faqquestion_history; if records.enableDeleteQuestion is turned on, the same request deletes the question outright with no soft-delete and no revision trail, matching the advisory's 9.1 Critical variant. No KEV listing or confirmed active exploitation is reported, and no standalone public exploit code has been identified at time of analysis, although the advisory itself publishes a step-by-step reproduction; this should be scheduled in the current weekly patch cycle.
Missing authorization in Parse Server before 8.6.101 and 9.0.0 before 9.10.4-alpha.4 allows unauthenticated REST API clients on MongoDB deployments to delete the internal _SCHEMA collection, stripping class field definitions, class-level permissions and protected fields so affected data becomes readable and modifiable by any client. PostgreSQL deployments are explicitly not affected and object ACLs continue to apply; no public exploit has been identified at time of analysis. The vendor and independent assessment rate this high severity (CVSS 8.8, assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L) and a near-term priority for MongoDB-backed installations with reachable REST endpoints; vendor patches are available for both affected release branches.
An authentication bypass in Parse Server affects 8.x releases before 8.6.102 and 9.0.0 through 9.10.5-alpha.2 when an app is configured with a custom authentication adapter written as a subclass of the exported AuthAdapter class: Parse Server never invokes the subclass's validateSetUp, validateLogin, and validateUpdate methods and instead falls back to an inherited base-class default that accepts any authData. For any provider served by such an adapter, unauthenticated remote attackers can supply arbitrary authData to sign up, link an identity, log in as an existing user, or skip a custom adapter that implements an additional authentication factor, potentially gaining full account access and integrity over affected data. Apps using built-in adapters or custom adapters defined as plain objects are not affected, and no public exploit code was identified at time of analysis; the priority label from the reporting feed is act_now, reflecting that the impact is severe for the narrower population that matches the configuration prerequisite.
Cross-organization authorization bypass in Dokploy through 0.30.10 lets an authenticated owner or admin of one organization control another tenant's applications by supplying a foreign applicationId to procedures such as saveEnvironment, updateTraefikConfig, deploy, and stop. Successful exploitation can overwrite environment variables and build secrets, repoint application sources, and disrupt other tenants' workloads. The flaw requires a multi-tenant Dokploy deployment and org-level owner or admin credentials; no public exploit has been identified at time of analysis, and a vendor fix is available via the referenced upstream commit.
Remote unauthenticated compromise of Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition is possible through the JSSE component when attacker-influenced data reaches the affected APIs. The listed affected builds include Java SE 8u511-b32, 8u511-perf-b32, 11.0.33.0.2, 17.0.21.0.2, 21.0.13.0.2, 25.0.5.0.2, and 27.0.1.0.2, plus GraalVM for JDK 17.0.21.0.2/21.0.13.0.2 and GraalVM Enterprise Edition 21.3.20.0.2. Per the assessed CVSS vector AV:N/AC:L/PR:N/UI:N, exploitation is remote, unauthenticated, and requires no user interaction on the API path, with high confidentiality and integrity impact and no availability impact; no CISA KEV entry, public exploit code, or EPSS score was supplied, and the vuln.today decision label is act_now.
Improper token-purpose validation in Postiz (gitroomhq/postiz-app) through v2.25.2 allows any authenticated user holding a low-privileged account to obtain a validly signed token containing claims of their choosing, which the application then accepts interchangeably as a session, an organization invitation carrying a chosen role, a password reset, or an enterprise provisioning token. The primary path is the browser-extension channel credential-refresh route, which signs attacker-supplied data taken from the request itself with the shared token-signing secret and stores the signed result where the requesting user can read it back; a second, narrower team-invitation creation route signs extra request-body fields in the same way. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, but the vendor rates the issue critical (CVSS 9.9, scope changed) and the priority label is act_now, with upgrading to v2.25.3 stated as the only complete fix.
Unauthenticated remote attackers can read protected information from WordPress sites running the Knit Pay UPI QR Code Payment Gateway for WooCommerce through version 1.6.3 because a plugin endpoint lacks authorization checks (CWE-862). The flaw is rated CVSS 7.5 with confidentiality-only impact (C:H/I:N/A:N) and requires WooCommerce plus the named plugin to be installed and active. No CISA KEV entry or public exploit code is present in the supplied intelligence, and exposure is limited by the plugin's niche UPI payment deployment footprint.
An allowlist bypass in Grav CMS 2.0.15 through 2.2.12 lets an authenticated account holding page-edit permission (api.pages.write, or admin.pages in the classic admin) invoke arbitrary public static PHP methods by smuggling a data-*@ directive past Grav's Class::method allowed-callable check inside a page-authored Flex form override; methods such as Folder::delete, Folder::move, Folder::copy or Utils::download can then delete directories, move or overwrite files, and read files outside the page tree. The crafted directive fires when the page's Flex form is built, for example when an administrator opens the page on the site, so the payload is planted by the lower-privileged editor and executed in an administrator's request. The vendor shipped a complete fix in 2.2.13; the earlier 2.2.2 patch (GHSA-9rq7-4cch-f22j) only closed the replace-name@ spelling and leaves installations exploitable, and no public exploit code was identified at time of analysis.
Row-level data-scope enforcement in yudao-cloud through 2026.09 can be switched off by any authenticated tenant user who sends a 'data-permission-enable: false' header on requests to /admin-api (and /app-api), letting them read or modify records belonging to other departments and users inside the same tenant. The flaw is a trust-boundary error (CWE-807): DataPermissionRpcWebFilter honours that header on every request path instead of only on internal /rpc-api calls, so no special configuration, user interaction, or elevated role is needed beyond a valid account. Rated High at CVSS 4.0 7.1 (assessed 3.1: AV:N/AC:L/PR:L/UI:N/C:H/I:L/A:N); no public exploit code was identified at time of analysis, though a third-party technical writeup of the header bypass is referenced, and the vendor has published an upstream fix commit.
Authentication bypass in the asVereinbase WordPress plugin before 1.1.8 allows unauthenticated remote attackers to log in as any user, including an administrator, because the plugin accepts an empty stored password or second-factor value as a match. Affected are WordPress sites running the plugin at versions below 1.1.8; the CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N with high confidentiality, integrity and availability impact, and no special configuration or user interaction is required. A public PoC reference exists but is not verified as working exploit code, and the EPSS score is low at 0.19% (8th percentile) even though the vuln.today decision label is act_now, so the severity and priority signals are split and should be read together.
OpenReception appointment booking software 2.1.0 and earlier lets remote attackers brute-force a returning client's six-digit booking PIN inside a targeted tenant, because the PIN throttle record is keyed on a tenant-independent email hash and its tenant_id is fixed by whichever tenant first logged a failure, so the victim tenant's challenge check never matches the row and never returns 429. A successful guess yields the client's booking access token, exposing their end-to-end-encrypted appointment tunnel and allowing appointments to be added or cancelled as that client. No vendor patch is available at time of analysis, and the published advisory includes step-by-step reproduction detail plus measurements of roughly 79 guess round-trips per second locally; the generic 20-requests-per-2-seconds IP limiter can be sidestepped by rotating the unvalidated x-forwarded-for header.
WireGuard in Zephyr (subsys/net/lib/wireguard) accepts an unauthenticated transport-data datagram and copies its source address into peer->endpoint, letting any host that can reach the listener's UDP port 51820 off-path redirect all subsequent handshake initiations, keepalives and encrypted tunnel traffic to an address of the attacker's choosing. Affected builds are Zephyr 4.4.0 through 4.4.2 with CONFIG_WIREGUARD enabled, which is marked experimental and off by default, and the defect fires only while the targeted peer has no valid handshake and no current keypair - the state at boot and after a session expires. The result is persistent tunnel denial (assessed A:H) and limited confidentiality loss (C:L) through traffic-metadata observation or selective dropping if the attacker relays redirected initiations; the Noise/AEAD cryptography prevents decryption or forgery, so keys are not compromised. The advisory's original report includes a 16-byte datagram recipe as a proof of concept; it is not verified as working exploit code, no public exploit is confirmed in use, and KEV status is not indicated - exploitation requires only UDP reachability to the listener, with no credentials or user interaction.
Privilege escalation in Tandoor Recipes before 2.7.0 lets any authenticated user obtain admin-level authorization inside a space where they only hold guest or user rights, by priming a per-user permission cache while their own self-created space is active. The flaw is in has_group_permission(), which caches group names under GROUP_CACHE_<user id> with no active-space component and re-sets the 30-second TTL on every request, so cached admin groups from space A keep answering checks after switch_user_active_space() moves the session into victim space B - and group revocations or demotions never take effect while the user stays active. Rated CVSS 4.0 7.1 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N); exploitation needs a multi-space deployment, an authenticated account, and - on multi-worker installs using the default per-process LocMemCache - the escalated request must land on the worker that primed the entry. Not listed in CISA KEV, but the vendor advisory documents a verified proof-of-concept harness against the real functions, so the technique is fully public and reproducible.
OpenID Connect login in Goobi viewer 25.01 through 26.04 validates the JWT audience outside the cryptographic verifier, so an ID token minted for a different relying party on the same identity provider can be replayed to the viewer's authentication endpoint and log the attacker in as that token's subject. Only deployments that have opted into OpenID authentication and share an IdP/issuer with at least one other relying party are exposed; array-valued aud claims fail closed and single-RP setups are described by the vendor as not practically exploitable, and the viewer's per-login nonce/state binding narrows the window further. There is no KEV entry and no public exploit identified at time of analysis, but a fixed release (26.05) and the upstream commit are both public. EPSS was not supplied in the input.
Goobi Viewer deployments that leave webapi.authorization.token unset accept an empty ?token= value on every @AuthorizationBinding-protected REST endpoint, allowing an unauthenticated caller to invoke protected API methods. The official install guide generates a UUID token, so only installations that skipped that bootstrap step - typically test, staging, CI, or container images - are exposed; on those, an attacker can delete Solr records, read operational statistics and cache data, and, where the client-applications feature is used, read client secrets and grant a client access to restricted content. The issue is fixed in version 26.05, and no public exploit was identified at the time of analysis.
Goobi viewer 24.03 through 26.04 exposes the DownloadTaskEndpoint WebSocket at /tasks/download/monitor.socket to unauthenticated users, so a remote attacker can drive the server's download machinery without credentials (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). Depending on network reachability, that yields server-side request forgery against internal hosts such as the local Solr instance or cloud instance-metadata endpoints, retrieval of local files whose extensions fall inside the application's allow-list, and deletion of the Solr index through the Core Admin UNLOAD action, which leaves the viewer unavailable until a full re-index. The vendor scored the issue 9.8, while the independent assessment keeps the unauthenticated network vector but lowers integrity impact from high to low; no public exploit identified at time of analysis. Vendor-released patch: 26.05.
Memory-note lifecycle tooling in obsidian-tc 1.0.1 through 1.31.3 can overwrite the entire body of an Obsidian vault note it does not own, and can leave the SQLite memory graph half-committed when a filesystem step is refused. An authenticated caller holding memory-write scope (write:memory) that invokes create_entity, link_entities, rename_entity, unlink_entities or delete_entity on a (type, name) pair whose computed memory/<type>/<name>.md path is already occupied by a hand-authored note or a foreign orphan will have that note's body regenerated from SQLite, with only its frontmatter preserved; delete_entity still requires its own deletion permission and destructive confirmation, which this flaw does not bypass. The maintainer found and fixed the class in 1.31.4 (PR #978, GHSA-r3g7-r4hr-m258); no public exploit identified at time of analysis, and the issue is rated this_week priority rather than an emergency because exploitation depends on already-granted memory-write permissions.
obsidian-tc 1.13.0 through 1.31.3 lets an authenticated client complete destructive, dispatch-gated Obsidian vault operations (delete, cross-folder move, frontmatter replace, link rewrite) even after the human explicitly declined or cancelled the human-in-the-loop confirmation, or after the elicitation response was omitted or malformed. The server treats a validly bound requestState echoed on resubmission as proof of approval, but that state is minted before the elicitation leg is ever asked, so it only proves the resubmission belongs to the same call; exploitation requires a Streamable HTTP deployment with auth.jwtSecret configured, a 2026-07-28-era client declaring elicitation.form support, and a tool marked destructive:true or carrying a human-in-the-loop scope floor. Only client-driven HTTP deployments are affected - stdio or jwtSecret-unset installs fall back to the CLI elicit_token path and never offer the round trip - and there is no public exploit identified at time of analysis (no CISA KEV listing), though the advisory notes the underlying construction was reproduced directly by the maintainers.
Authorization bypass in Apache Vysper's XEP-0077 In-Band Registration implementation allows any authenticated user to compromise other accounts on the XMPP server. All versions are affected, the project is retired and unsupported, and the vendor does not plan to release a fix; no public exploit was identified at time of analysis. The vendor's stated remediation is migration to an alternative XMPP server.
DJI CrystalSky ZS600C firmware 0.3.9.7 through 0.6.6.9 exposes an unauthenticated adbd shell to anyone with physical USB access because the device ships with ro.adb.secure=0 and USB ADB enabled. An attacker can obtain a uid 2000 shell as a foothold for a separate privilege-escalation step to root; ADB over TCP is not enabled by default, but when enabled out-of-band the same unauthenticated shell is reachable over the network. No public exploit was identified at time of analysis and there is no CISA KEV entry; the assessed CVSS 3.1 score is 7.0 (AV:P) because the default path requires physical access, while the reported CVSS 4.0 base score is 9.3.
Local apps on DJI CrystalSky ZS600C devices can invoke system-privileged actions-including a factory reset that wipes user data, shutdown, clock/timezone changes, and a firmware-apply hand-off-because the DJIUpdateService binder does not verify caller identity or permissions. The flaw affects firmware v0.3.9.7 through v0.6.6.9 and is reachable by an installed app with no permissions and no user interaction. No public exploit has been identified at time of analysis; the issue is access-gated to local code execution on the specific device but warrants this-week prioritization because successful abuse is destructive and disruptive.
Missing authorization in DJI CrystalSky ZS600C firmware v0.3.9.7 through v0.6.6.9 allows a local application with no Android permissions to invoke binder transaction 1018 on android.dji.server and execute arbitrary OS commands as root through the root-privileged assistant daemon. The attack is local only and requires the ability to run code on the physical device; no public exploit has been identified at time of analysis. The reported CVSS 4.0 base score is 8.6 (High), and the independent CVSS 3.1 assessment is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Missing authorization in Zimbra Collaboration Suite 10.1.16 and 10.1.20 allows an authenticated delegated administrator holding no explicit administrative grants to overwrite the global Zimlet configuration through ConfigureZimletRequest. The injected configuration can add an attacker-controlled domain to the proxy allowlist of the default class of service, so a signed-in user in that class who opens a crafted /service/proxy URL is served attacker-controlled HTML from Zimbra's own origin, letting the resulting JavaScript read mailbox data and act as the victim. The admin-side escalation is remote and low-complexity but requires a delegated-admin account with admin SOAP service access (PR:L), and the browser compromise requires the victim to open the crafted URL (UI:R); no public exploit code has been identified at time of analysis, no KEV entry is present, and the vuln.today priority label is this_week rather than emergency.
Local io_uring CONNECT BPF filter bypass in Linux kernel 7.2 and 7.3 lets a low-privileged process reach AF_INET6 destinations that an administrator-configured filter intended to deny. The bug is a length-threshold mismatch: at addr_len 24 (SIN6_LEN_RFC2133), io_connect_bpf_populate() leaves connect.port and connect.v6_addr zero while the kernel connects to the real destination, so filters that deny specific IPv6 ports or addresses are bypassed. The upstream commit describes a verified reproducer; no CISA KEV active-exploitation listing is provided, EPSS is low at 0.21% (11th percentile), and the assessed impact is limited confidentiality/integrity loss rather than remote compromise.
Any account holding the lowest 'member' role in a PraisonAI Platform workspace can permanently delete projects, agents, issues, labels, issue dependencies and issue-label attachments created by the workspace owner or by other members, because all six content DELETE endpoints verify workspace membership but never verify resource ownership or an owner/admin role. The flaw affects praisonai-platform from 0.1.4 up to the fix and scores CVSS 8.1 (AV:N/AC:L/PR:L/UI:N/C:N/I:H/A:H), since an authenticated low-privileged user can destroy integrity and availability of workspace content while confidentiality is untouched. Exploitation requires a valid member account inside the targeted workspace - either invited by the victim or obtained through a compromised member credential - so the practical exposure is an insider or account-takeover scenario rather than a mass internet threat; there is no CISA KEV entry, no EPSS signal supplied and no confirmed working exploit package, though the vendor advisory publishes a full step-by-step reproduction.
Unauthenticated remote agent invocation in PraisonAI LinearBot 4.6.56 through 4.6.58: because LINEAR_WEBHOOK_SECRET is treated as optional and defaults to an empty string, the aiohttp webhook listener bound to 0.0.0.0 skips Linear-Signature HMAC verification entirely, so any network caller who can reach the endpoint can POST a forged 'Linear-Event: AgentSession' request that is parsed, backgrounded, and dispatched into BotSessionManager.chat(), causing the bot to run the configured agent and post comments back to Linear under the bot token. Exploitation requires the operator to have started LinearBot with a Linear token but without a webhook secret, and the listener to be reachable; deployments that do set the secret reject missing and invalid signatures with 401 before dispatch. A public proof-of-vulnerability harness exists that exercises the handler offline and monkey-patches the outbound comment path; it is not verified as working exploit code against deployed instances, and there is no confirmed active exploitation (no KEV entry).
PraisonAI versions 4.5.112 through 4.6.58 expose the Recipe HTTP API without authentication when an operator starts the deprecated Typer command `praisonai recipe serve` on a non-localhost interface without explicitly selecting API-key auth, allowing unauthenticated network callers to enumerate and execute recipes and, when `--admin` is enabled, invoke `/admin/reload`. The issue is an authentication bypass at the installed Typer callsite (CWE-287, with CWE-306 and CWE-862 also applicable); the hardened legacy feature handler rejects non-localhost binding without auth, and `create_auth_middleware()` fails closed with 503/401 when auth is selected but misconfigured. The CVSS 3.1 base score is 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N), and PraisonAI 4.6.59 contains the vendor fix; no CISA KEV entry or confirmed working remote exploit code is present in the supplied intelligence, and the advisory's public local-only proof-of-value harness exercises the bypass in-process without binding a socket, so it is not verified as working remote exploit code. Given the this-week decision label, prioritize upgrading internet-reachable or Docker-deployed instances.
Slack app_mention events in the PraisonAI bot (PyPI package praisonai, versions 3.11.0 through 4.6.58) skip the allowed_users, allowed_channels and unknown_user_policy checks that the normal message handler enforces, so any Slack workspace member who can mention the bot in a channel where the app is installed can drive the configured agent even when the identical event content is dropped by the message path. The root cause is missing authorization (CWE-862, also tracked as CWE-863) in src/praisonai/praisonai/bots/slack.py, and the assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L (8.3, High) - network reachable, low complexity, and authenticated, since the attacker must already hold Slack workspace membership and be able to mention the bot. A public PoC reference exists in the form of a local-only harness that mocks Slack Bolt and the Slack SDK in-process and does not connect to Slack; it is not verified as working exploit code against a live deployment, and there is no confirmed active exploitation (no CISA KEV listing). Remediation is prioritized as this week rather than an emergency.
Missing authorization in the BlueSpiceUserManager extension of BlueSpice (5.0.0 through 5.1.10 and 5.2.0 through 5.2.6) lets any authenticated user, with no special privileges, block or unblock arbitrary accounts including administrators through the /bs-usermanager/v1/block/create and /bs-usermanager/v1/block/delete REST endpoints. Successful abuse can lock every administrator out of the wiki (denial of service) or silently lift blocks that administrators imposed, altering the integrity of account state. Exploitation requires a valid registered account plus network reach to the REST API, and the extension must be installed and enabled; where self-registration is open the barrier is negligible, otherwise the realistic attacker set is insiders. No public exploit code was identified at time of analysis.
WPMobile.App (wpappninja) WordPress plugin versions through 11.86 expose an unauthenticated missing-authorization weakness that can disclose sensitive information to remote attackers. The flaw is rated CVSS 7.5 with confidentiality-only impact, and no public exploit was identified at time of analysis. Sites running the affected plugin are exposed when the vulnerable plugin functionality is reachable.
Authentication bypass in WizLearn LMS, rated CVSS 9.8, allows an unauthenticated remote attacker to circumvent both password-based login and the OAuth flow with a crafted POST request, potentially taking over user accounts and gaining administrative control of the platform. The affected release range is not established in the available data because the CPE version is a wildcard, so organizations should confirm vulnerable versions against the CSA advisory. No public exploit identified at time of analysis.
Improper authentication in ASUS router firmware lets an unauthenticated attacker on an adjacent network-such as an associated Wi-Fi client or a device on the same LAN segment-send an HTTP request, forge an access ticket, and perform administrator operations. The affected router models and firmware versions are not specified in the available data, which uses a wildcard CPE for ASUS routers, and no public exploit has been identified at time of analysis. The issue is rated 8.7 and is prioritized this week.
Unauthenticated credential takeover of non-administrator WordPress accounts is possible in ACF Extended and ACF Extended PRO before 0.9.2.8 through the front-end Forms module's update-user action. The plugin checks authorization only when the targeted account is an administrator, so a visitor can overwrite another non-admin user's credentials and obtain a session for that account when a published form maps the target user to a visitor-submitted value instead of the default current user. The flaw is remotely reachable without authentication or user interaction but is conditional on that non-default form configuration; no public exploit was identified at time of analysis and the vendor has released a patch.
Privilege escalation in Okta Access Gateway allows an already authenticated user with an active session to obtain Admin Console access by altering the authentication-source parameter during sign-on, which OAG fails to validate before issuing a SAML assertion. Okta rates the flaw 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), while our assessment adjusts the privilege requirement to PR:L because valid credentials and a live session are mandatory; the AC:H metric reflects that the parameter manipulation is not trivial to perform reliably. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, but successful abuse grants administrative control of the gateway, so it warrants prompt patching on this week's cycle rather than emergency action.
Authentication bypass in the public registration form of onPhase/frevvo Forms 11.0.14 allows an unauthenticated remote attacker to impersonate an existing tenant user, obtain TenantAdmin and Designer privileges, and execute arbitrary operating system commands. Exploitation requires the public registration endpoint to be reachable and the attacker to supply a valid tenant name and an existing user identifier; no credentials or user interaction are required. The vuln.today decision is act_now, and no public exploit identified at time of analysis.
Remote, unauthenticated attackers can change the hostname, DNS servers, and NTP time source on Kiloview E3 NDI encoder firmware before 1.30 through the ONVIF device service, even when authentication is enabled for that service (CVSS 8.7). The flaw is an authentication bypass for configuration write operations (CWE-306) with high integrity impact but no direct confidentiality or availability impact; exploitation requires network reachability to the ONVIF service. No public exploit identified at time of analysis, and the vendor provides a firmware update.
Kiloview E3 NDI encoder firmware before version 1.30 signs session JSON Web Tokens with a single HMAC-SHA256 secret that is hardcoded in the firmware image and shared across every deployed device. Because the firmware is publicly downloadable from the vendor, anyone can extract that secret and forge valid session tokens, including administrative ones, then reach privileged device functions over the network without any credentials and without user interaction. The flaw is remotely exploitable and high impact for confidentiality, integrity and availability in our assessment; no public exploit code or confirmed active exploitation was identified at time of analysis, though the underlying technique requires only offline extraction of a static string plus network reachability to the authentication endpoint. Kiloview has released fixed firmware 1.30, and the vendor advisory (ICSA-26-295-01) is available.
Privilege escalation in Microsoft VM Inspector for Azure Virtual Machines allows unauthenticated, network-reachable attackers with no user interaction to gain elevated privileges, and the vendor scores it CVSS 10.0 with a scope change (S:C) indicating impact extends beyond the initially vulnerable component. The root cause is a link-following defect (CWE-59): the component resolves a link before accessing a file, so an attacker who can influence a symbolic link or junction can redirect privileged file operations. Microsoft has published a fix through its MSRC update guide and the vuln.today priority is act_now; no public exploit code or CISA KEV entry was identified at time of analysis.
Privilege elevation in Azure Kubernetes Configuration Service is possible for unauthenticated network attackers because a critical function lacks authentication, and the CVSS 3.1 base score is 10.0. Because the service is Microsoft-managed, real-world exposure depends on network reachability to the vulnerable endpoint and on whether Microsoft has already completed server-side remediation; no customer-side non-default configuration is stated as required. Vendor patch information is available and the vuln.today priority label is act_now; no public exploit identified at time of analysis.
Improper authentication in Microsoft Entra Application Proxy (formerly AAD App Proxy) allows an unauthenticated, remote attacker to elevate privileges across a trust boundary, with the supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) scoring 10.0 - no privileges, no user interaction and low complexity, with high confidentiality and integrity impact and a scope change. Exposure is deployment-specific: the target organization must actually run Application Proxy to publish internal applications for remote access, and the proxy endpoint must be reachable by the attacker; organizations not using the service are not exposed to this flaw. Microsoft is the reporting party and a vendor patch is available per the MSRC update guide, and the vuln.today decision label is act_now; no public exploit code or confirmed active exploitation was identified in the supplied data, although the trigger conditions themselves are not described in the available sources.
Token forgery in the Authlib Python library before 1.9.1 lets a remote, unauthenticated attacker mint HS256, HS384 or HS512 tokens carrying arbitrary claims that Authlib accepts as genuinely signed, whenever the deploying application's HMAC verification key resolves to an empty string or empty bytes (for example an unset environment variable defaulted to '', a config column defaulting to '', or a key-resolver returning '' on a lookup miss). The exposure is strongly gated by that deployment precondition: applications that always supply a non-empty secret are not exploitable, and asymmetric RS/ES verification paths are unaffected, which is why the vector carries AC:H rather than a universally applicable rating. No public exploit code has been identified at time of analysis (the advisory supplies a prose reproduction description rather than weaponized code), CISA KEV does not list this issue, and the vendor has released 1.9.1 as the fix.
Authentication bypass in Authlib's deprecated-but-still-shipped authlib.jose module (1.3.1 through 1.8.0, fixed in 1.9.0) lets an unauthenticated remote attacker forge HS256 JSON Web Tokens with arbitrary subject and role claims using nothing but the issuer's public key, because the OctKey.import_key() guard tests for PEM armour only at byte zero while the PEM loaders skip leading whitespace, comment lines or a BOM. Two non-default deployment properties are required: the relying party uses the documented module-level jwt object (whose registry mixes HS* with RS*/ES*/PS*/EdDSA and whose decode exposes no algorithms parameter), and the verification key is stored as PEM or X.509 certificate text that does not begin at offset 0 with '-----BEGIN ' - a canonical PEM is still blocked, and pinning the algorithm (e.g. JsonWebToken(['RS256'])) is confirmed to reject the forgery. Rated CVSS 7.4 (AV:N/AC:H/PR:N/UI:N, C:H/I:H) and not listed in CISA KEV; the upstream advisory includes an end-to-end proof-of-concept reproduction against 1.8.0.
An authenticated administrator of an HPE networking product can reach a low-complexity, network-exposed flaw and achieve full confidentiality, integrity and availability impact on the affected component, according to an HPE security bulletin (document HPESBNW05162) scored at CVSS 3.1 base 7.2. The vector AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H confirms the issue is remotely reachable with no user interaction, but the high-privilege prerequisite (PR:H) means only an attacker who already holds an administrative or otherwise privileged account on the device can exploit it, so the realistic exposure is an insider, a compromised administrative credential, or a post-exploitation step, not anonymous internet attack. No public exploit code or proof-of-concept is referenced in the supplied sources, and the specific affected product, version, feature and protocol are not described in the available data.
Project isolation bypass in Incus lets an authenticated client that is confined to one project copy and read custom storage volumes belonging to any other project on the same server, including volume snapshots and configuration. The flaw affects Incus 7.0.1 (fixed in 7.0.2) and 7.2.0 through 7.4.x (fixed in 7.5.0), and is reachable only through a hand-crafted POST to /1.0/storage-pools/{pool}/volumes/custom that supplies a source volume with an attacker-chosen source.project while omitting source.type - the official Incus client always sets source.type=copy and therefore cannot trigger it. No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation requires legitimate low-privilege credentials holding can_create_storage_volumes in at least one project, so impact is concentrated on multi-project servers where project isolation is the actual security boundary.
Incus servers that use multi-project tenancy expose in-flight operations across project boundaries because the GET /1.0/operations/{uuid} handler performs no authorization check, letting any authenticated client - including one holding a TLS certificate restricted to a single project - read operations that belong to other projects. The disclosed data includes the full command line, the process environment (where deployment tooling typically stores database passwords, API tokens and cloud credentials), the operation's websocket fd secrets and resource URLs, and, when an 'incus config trust add' operation happens to be pending, the trust-enrolment token itself, which the reporter demonstrated could be exchanged for an unrestricted certificate and full server admin. Exploitation is constrained: the attacker must already hold a project-restricted certificate and must obtain the 122-bit crypto/rand UUIDv4 of a specific in-flight operation out of band, since Incus discloses no enumeration path to a restricted client. The issue carries no CISA KEV entry or reported active exploitation; the upstream advisory includes a step-by-step reproduction sequence, which is the only published proof of concept.
Argument injection in Incus 7.3.0 through 7.4.x lets a user confined to a restricted project smuggle the forbidden block.create_options setting onto a custom volume, then trigger a copy or move onto a storage pool that formats new volumes, so the injected value is appended to the mkfs command line executed as root. The flaw is an incomplete fix for CVE-2026-62867, which only rejected the option on the direct custom-volume creation path while leaving update, copy and move operations unchecked; the package range is go/github.com/lxc/incus/v7/cmd/incusd >= v7.3.0, < v7.5.0. Exploitation requires an authenticated restricted-project user with permission to create or edit custom volumes, and root-level code execution only materialises on pools that format on copy such as non-thin LVM - on other drivers the forbidden option lands on the volume config without reaching mkfs. No public exploit code was identified at time of analysis, but the weakness class is straightforward and the priority signal is act_now given the root-level outcome on affected storage backends.
Cross-namespace privilege escalation in OpenBao 2.3.0 through 2.6.2 allows an authenticated token holder to attach specially crafted policy names and thereby gain capabilities from policies cached in other namespaces, including the root namespace. The ACL policy cache does not keep cached policies scoped to their namespace, so the token can act across namespace boundaries; the referenced policies must already be in the in-memory LRU cache at both token creation and token use, and a referenced foreign root policy is granted only within the token's own namespace, which limits reliability and impact. No public exploit code or confirmed active exploitation has been identified at time of analysis, and multi-tenant deployments that depend on namespace isolation are the primary concern; fixed releases are 2.6.3 and 2.7.0.
Integrity-only NoSQL injection in the MongoDB C# Driver update-statement builder allows an authenticated application user with ordinary read-write access to influence update logic, potentially modifying or deleting stored data the application did not intend to change. The flaw is tracked as CSHARP-6168 and affects releases before 3.13.0; exploitation depends on the application passing attacker-influenced values directly into the affected update builder surface, so it is not reachable against a hardened application that does not do so. No public exploit was identified in the provided intelligence at time of analysis, and the primary remediation is upgrading to MongoDB .NET/C# Driver 3.13.0.
Roskus Prospero Flow CRM versions 2.0.0 through 5.25.x ship user API routes (GET and DELETE /api/user/{id}) protected only by the auth:api middleware, which validates the JSON Web Token and performs no permission, policy or role check, so any holder of a basic-role account can read the account records of other users in the same company - including administrators and their email address, telephone number, postal address and IBAN - and, from 3.5.0 onward, delete those accounts. Exploitation requires a valid authenticated account (PR:L) and, for deletion of accounts outside the attacker's own company, membership in Company::DEFAULT_COMPANY (company ID 1), where the company comparison is skipped entirely; an account in that company can delete any account of any company, including a company's last administrator, and deletion removes the data held on the account. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vulnerability is tracked with an assessed CVSS 3.1 base of 8.6 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and is prioritized for remediation this week.
Cross-tenant data access in SmileCDR HAPI FHIR allows an attacker who holds valid credentials for one tenant in a multi-tenant deployment to read from or write to another tenant's storage partition by submitting an untrusted bundle body that replaces a trusted partition identity; storage partition entitlement is not enforced by default. Exploitation requires authenticated access to at least one tenant, and single-tenant deployments or those with partition entitlement enforcement enabled are less exposed. No public exploit identified at time of analysis, and this is a genuine priority rather than an inflated high-CVSS issue, though not a drop-everything emergency.
Canonical Juju 4.0 through 4.0.15 leaves the model unit-resources download route without an authorization check, so any principal already authenticated to the controller - a unit agent, or a human user holding only 'login' permission with no access to the target model - can request an arbitrary unit in an arbitrary model and read that application's charm resources, including container-registry credentials. The fix in Juju 4.0.16 binds the unit named in the request URL to the authenticated identity, refusing cross-unit and cross-model access. No public exploit code was identified at time of analysis, and the flaw requires a valid controller credential, though one at the lowest privilege tier and against default deployments.
Unauthenticated OAuth state values can be redeemed as Magic Link tokens in Better Auth 1.4.0-beta.18 through 1.7.6, letting an attacker who knows a victim's email address obtain a full session for that account without mailbox access or completing the provider callback. The flaw only applies to deployments that enable the Magic Link plugin with plain token storage (or hashed tokens plus globally hashed verification identifiers), enable a built-in social or Generic OAuth provider, and use database-backed OAuth state - the default when a database or secondary storage is configured. Successful abuse yields an existing user's session with all its permissions, or, when Magic Link sign-up is enabled, a new account incorrectly flagged as email verified; no public exploit code has been identified at time of analysis, but the vendor advisory and a public fix commit fully document the technique.
Authorization bypass (CWE-639) in the MarcosCamara01 Ecommerce Template lets any authenticated shopper delete or change the cart and wishlist rows that belong to other accounts on the same installation, because the Drizzle repository calls match rows on the primary key alone and the per-user PostgreSQL row level security policies never take effect for the application's connection. Affected deployments are those using the template's default single-DATABASE_URL setup, where the migration role that creates the tables is also the runtime role, so PostgreSQL does not apply RLS to the table owner; cart_items.id and wishlist.id are sequential bigserial values, making other users' row identifiers enumerable, and the update path returns the modified row including its owning user_id. A valid low-privileged account on the target is required and no user interaction is needed; no public exploit identified at time of analysis, and vendor-side code addressing both the RLS enforcement gap and the missing ownership predicates is available in the referenced commit.
Authentication bypass in Silicon Labs Connect SDK 4.3.1 and earlier, plus Flex SDK 3.7.7 and earlier, allows an attacker positioned within radio range of the device to send a protocol message carrying invalid security settings that the stack fails to verify, causing the message to be processed as though it came from a trusted source. Successful exploitation disrupts network operation (high integrity and availability impact) but cannot recover the Network Key or decrypt traffic, so confidentiality is explicitly unaffected. The trigger is unauthenticated, low complexity, and requires no user interaction, though the attacker must be within adjacent-network/radio range and cannot reach the device over the internet; no public exploit code or active exploitation is identified in the available data, and patch is available from the vendor.
An authorization bypass in Lotus (uselotus/lotus) through 0.10.2 lets a self-registered, authenticated user switch into a different tenant by POSTing that organization's UUID to /app/switch_organization/, after which the victim tenant's data and billing configuration become reachable. Access is not unrestricted: the attacker must obtain the target organization's random, non-guessable UUID out of band, which is the main practical barrier and the reason the vector carries AC:H/AT:P despite the low-privilege (PR:L) requirement. Exploitation status is not confirmed in the available sources - no CISA KEV entry and no verified working exploit code were provided, though a public technical writeup reference is linked; priority is 'this_week', i.e. a genuine but not drop-everything issue, and no fixed version is listed in the available data.
Improper authentication in the Go event-ingestion middleware of uselotus Lotus through 0.10.2 lets unauthenticated remote attackers submit usage events to POST /api/track/ on behalf of another organization, corrupting that tenant's metered usage and billing records. The flaw is integrity-only (no data disclosure or availability impact) and exploitation hinges on knowing or obtaining a valid API key prefix, since the secret half of the key is never compared against the stored hashed_key; the sources do not explain how a prefix would be leaked or enumerated. No public exploit code was identified at time of analysis and the vulnerability is not in CISA KEV, though VulnCheck reporting and a public technical writeup give the issue a this_week remediation priority; the blast radius is narrow but the defect is a genuine authentication bypass.
Unauthenticated remote users may be able to read protected data from WordPress sites running ACF Extended through 0.9.2.7 because the plugin does not enforce an authorization check in some access-controlled functionality (CWE-862). The CVSS 3.1 score is 7.5 with confidentiality-only impact and no integrity or availability effect; the exact endpoint and configuration state required are not described in the available sources. Patchstack reported the issue, no CISA KEV entry is present, no public exploit identified at time of analysis, and vuln.today places it in the this_week priority tier.
Authentication bypass by spoofing in Brainstorm Force's SureCart WordPress plugin affects versions through 4.9.5 and, per the CVSS vector, is reachable over the network without authentication or user interaction, with high confidentiality, integrity, and availability impact. The exact spoofing mechanism and any required configuration are not described in the supplied sources, and no public exploit was identified at time of analysis. The vuln.today priority is act_now.
Royal MCP, a WordPress plugin, issues preview-link tokens that are not bound to the single preview they were created for; in versions before 1.5.7 any party holding a valid token is authenticated as the token's owning user - an administrator in a default install - across the entire REST API without a nonce check, enabling full site takeover. The CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects that the hard part is obtaining such a token, and the available sources do not describe how a token is acquired or how long it stays valid, so practical acquisition difficulty is unverified. A public PoC reference exists (the WPScan entry) but it is not verified as working exploit code, and no CISA KEV listing or EPSS scoring is present in the supplied data.
Hard-coded cryptographic key in the NT OneAPP login flow enables remote attackers to decrypt captured authentication requests and recover plaintext user credentials and device information. The issue affects NT OneAPP from NewType Infortech (CPE version wildcard, so all versions unless the vendor states otherwise); exploitation requires the attacker to first obtain encrypted login traffic, which is why the independent assessment rates attack complexity high despite the unauthenticated network vector. No public exploit was identified at time of analysis, and no CISA KEV entry is associated with this CVE.
Authentication bypass in Obot's CLI login flow before 0.26.0 lets an unauthenticated remote attacker obtain a victim's non-expiring API key by choosing a token request ID and persuading a signed-in user to complete the crafted login link, resulting in account takeover. The flaw is a CSRF-class weakness (CWE-352) requiring user interaction, and the stolen key remains valid until manually revoked. No public exploit code was identified at time of analysis, and CVE-2026-114662 is not in CISA KEV.
Missing authorization in OpenRemote's GatewayServiceResource lets any authenticated, non-administrative user start, stop, or query edge-gateway tunnels, opening persistent bidirectional TCP circuits into an edge gateway's network or tearing down tunnels operators depend on. All OpenRemote deployments from 1.2.0 through versions before 1.31.0 are affected, but exposure is gated on the instance actually using gateway tunneling with at least one configured edge gateway, since the vulnerable POST/DELETE tunnel endpoints must be reachable and operational. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the attacker only needs a low-privileged account (CVSS PR:L) and no user interaction, which keeps the bar low wherever tunneling is deployed.
Authorization bypass in the Grav Flex Objects plugin 1.4.0 through 1.4.16 lets authenticated, non-super users holding api.access plus either admin.pages or admin.configuration.pages read page source and frontmatter, modify content, and delete pages they are explicitly denied, because the generic /api/v1/flex-objects/pages routes enforce only directory-level admin.pages checks instead of the Pages API's api.pages.read/write and page-level permission rules. Scored 7.1 with an independent assessment of high confidentiality and high integrity impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), the flaw is a privilege-escalation problem past intended per-page restrictions rather than an anonymous compromise path - the attacker must already hold a valid restricted admin or editor account, and super-user accounts are unaffected. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this is a moderate-priority remediation item rather than a drop-everything emergency.
TLS client-configuration reuse in Traefik Proxy 2.11.0 through 2.11.57 and 3.0.0 through 3.7.13 allows an unauthenticated client to bypass a backend service's configured root CAs, SNI/server name, and certificate verification. When one backend issues an NTLM or Negotiate (Kerberos) challenge, Traefik stores the resulting round tripper in a client-connection slot that is not keyed by ServersTransport; an attacker who arms that slot can then reach a different service over the same keep-alive connection and inherit the wrong TLS client settings, undermining trust in the downstream backend rather than in Traefik itself. Exploitation is conditional - it requires connection-reuse timing, an NTLM/Kerberos-authenticating backend, and multiple services with divergent ServersTransport TLS settings behind the same proxy - and no public exploit code or active exploitation has been identified at time of analysis; vendor fixes are available in 2.11.58 and 3.7.14.
Authentication bypass in Traefik Proxy 3.7.0 through 3.7.13 allows unauthenticated remote attackers to impersonate mTLS identities by supplying forged Ssl-Client-* headers (notably Ssl-Client-Verify: SUCCESS plus a chosen certificate subject and issuer) to the plaintext HTTP router. Exploitation is gated on a non-default configuration: the Kubernetes Ingress-NGINX provider must be in use, ssl-redirect must be disabled so the HTTP router is reachable, auth-tls-pass-certificate-to-upstream must be enabled so Traefik forwards client-supplied headers, and the upstream backend must trust those headers as proof of mutual-TLS identity. No public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied; the advisory (GHSA-mwrr-6hp4-pxr6) covers releases before v3.7.14.
Traefik 2.11.0 through 2.11.57 and 3.0.0 through 3.7.13 can assign an unauthenticated attacker's frontend request to a backend socket that a legitimate user preauthenticated with Authorization: Negotiate (NTLM/Kerberos), letting the attacker read or write with the victim's identity. The root cause is Traefik's globally shared backend connection pool, which does not isolate sockets bound to a particular frontend identity; exploitation requires an active victim socket and favorable pool-reuse timing, so this is a mid-to-high priority issue for deployments fronting connection-bound Negotiate backends rather than a universal emergency. No public exploit code or CISA KEV entry is identified at time of analysis, and fixed releases are 2.11.58 and 3.7.14.
Client-certificate authentication bypass in Traefik v3.7.0 through v3.7.13 lets a holder of a certificate issued by one host's client CA reach a different host that requires its own separate client CA, while that host's legitimate clients are locked out. The defect only manifests when the Kubernetes Ingress NGINX provider is enabled and mTLS client authentication (auth-tls-secret) is configured on multiple hosts whose secret names collide once dots are normalized to dashes, causing Traefik to merge the two trust pools; the independent assessment rates this CVSS 3.1 7.4-class impact (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N) because exploitability depends on that naming pattern (AT:P). No public exploit code or confirmed active exploitation was identified at time of analysis, and exploitation additionally requires the attacker to already hold a valid certificate from the colliding CA.
Unauthenticated clients can inherit a victim's NTLM/Negotiate-authenticated backend session in Traefik v3.2.0 through v3.7.13 when the experimental FastProxy connection pool is enabled, because pooled keep-alive backend connections are not pinned to the frontend client that originally authenticated. An attacker who lands on a reused connection after a victim completed a handshake can read that victim's data and perform actions as them on the backend, while the Traefik instance itself is not directly compromised. Exploitation is opportunistic and configuration-dependent: it requires the non-default experimental FastProxy pool, NTLM or Negotiate authentication on the backends, and a timing window in which the attacker is handed the victim's pooled connection; no public exploit code or CISA KEV entry was identified at time of analysis.
Access-control bypass in Traefik v3.7.13's Kubernetes Ingress NGINX provider allows unauthenticated remote attackers to reach ssl-passthrough Ingress backends protected by auth-type, auth-url, or whitelist-source-range annotations when a non-TLS entry point is exposed and the attacker knows the Ingress host. The flaw is configuration-gated-affected deployments must use the Ingress NGINX provider with ssl-passthrough Ingresses and a reachable plain HTTP entry point-and the bypass is silent because nothing is logged. No public exploit code or active exploitation is identified in the provided intelligence; upgrade to v3.7.14.
Mutual TLS enforcement in Traefik Proxy can be bypassed, allowing unauthenticated remote clients to reach routers that are configured to require client certificates without presenting one. The flaw affects builds made with the Go 1.27 toolchain, where the request TLS state can be evaluated as nil and the SNI check is consequently skipped; an attacker sends an HTTP/2 request carrying the ':scheme http' pseudo-header over the TLS connection to sidestep certificate validation. Fixed in v2.11.58 and v3.7.14, the issue is exploitable only when an mTLS-protected router actually exists and the binary was compiled with the affected Go version, so default deployments that do not use client-certificate authentication are not exposed; no public exploit code was identified at time of analysis.
Delegated 'Users Admin' accounts in WWBN AVideo before version 29.4.0 can delete, overwrite, or demote full administrator accounts by posting directly to confirmDeleteUser.json.php or userAddNew.json.php with an administrator's user ID, destroying that admin's videos and account in the process. The flaw is a server-side authorization gap: the interface already hides admin-row actions from non-admins, but the endpoints themselves never re-verified that the caller outranks the target, so a crafted request bypasses the cosmetic UI restriction. Exploitation requires an authenticated account holding the Permissions::canAdminUsers() delegated role, so anonymous visitors and ordinary users are not affected; no public exploit code has been identified at time of analysis and no EPSS or CISA KEV signal is present in the available data.
Improper access control in Splunk Enterprise 9.4, 10.0, 10.2, and 10.4 allows a low-privileged authenticated user to cross a security boundary and achieve high confidentiality, integrity, and availability impact, making the release a 9.9 severity fix. The flaw was found during Cisco's internal hardening review rather than through external reporting, and the affected ranges are 9.4 before 9.4.16, 10.0 before 10.0.11, 10.2 before 10.2.8, and 10.4 before 10.4.4. No public exploit code has been identified and there is no CISA KEV entry, but vendor patch availability combined with an act_now priority label places upgraded discipline on anyone running an unpatched instance; the trigger is not described in the available sources.
Authenticated Splunk Enterprise users whose roles include the schedule_search capability can use the scheduled search workflow to run risky SPL commands that the platform would normally block, resulting in disclosure or alteration of Splunk data or disruption of Splunk availability. The issue affects Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, and is fixed in those releases. The assessed vector requires low privileges (PR:L) and no user interaction, with high confidentiality, integrity, and availability impact; no public exploit identified at time of analysis.