Authentication Bypass

Spoofing in Microsoft Visual Studio stems from improper certificate validation and can let an unauthenticated remote attacker impersonate a remote endpoint, with high confidentiality and integrity impact and no availability impact per the CVSS vector. The issue affects Visual Studio 2017 version 15.9, 2019 version 16.11, 2022 version 17.14, and 2026 version 18.11; exploitation is high-complexity and realistically requires an intercepting position on the network path. No public exploit was identified at time of analysis, and the available vendor update is the indicated remediation.

Unauthenticated super-administrator access in Jpom 2.10.0 through 2.11.12 is possible through query-condition injection in the JPOM-USER-TOKEN header, where a value such as 'is not null' is treated by Hutool's Condition parser as an operator and bypasses LoginInterceptor authentication. The resulting super-administrator role can then use Jpom's script features to execute commands. The issue is rated act_now with CVSS 9.3; no CISA KEV entry or confirmed public exploit code is provided in the supplied data, and the trigger is remote and unauthenticated against default configurations.

Authenticated contributors who hold write access to a Konflux-CI-managed repository can execute arbitrary shell commands inside the CI/CD workflow by injecting payloads into environment export scripts, whose unvalidated output is subsequently evaluated dynamically by manifest synchronization scripts. Successful exploitation gives the attacker control of pipeline execution and exposes authentication tokens, deployment credentials, and onward access to production systems, with a scope change beyond the pipeline component itself. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the CVSS vector requires a privileged, authenticated actor (PR:H) plus a pipeline-triggering interaction (UI:R), so real-world exposure tracks how many semi-trusted principals can push to Konflux-managed repositories.

Authentication bypass in Wp Social Login and Register Social Counter 3.2.2 and earlier allows an unauthenticated remote attacker to obtain a fully authenticated WordPress session as an existing user, including an administrator, when the site has the bundled Facebook or Twitter social-login provider configured and active. The plugin's social-login REST callback trusts the OAuth provider's email string and calls wp_set_auth_cookie() without a password check, while the intended email-verification guard is ineffective for the bundled Hybridauth Facebook and Twitter adapters. No public exploit is identified at time of analysis, and the provided intelligence does not confirm active exploitation, but the assessed prerequisites and high impact make this a this-week priority.

Authentication bypass in Uncanny LearnDash Toolkit 3.8.2 and earlier lets a network attacker who already knows a target account's credentials log in even when that account is pending approval, unverified, or administrator-suspended. The plugin's account gate checks the raw `email` value with `get_user_by()`, while the later `wp_signon()` call runs WordPress core's `sanitize_user()`, so appended junk causes the gate to be skipped while the real account still authenticates; the required nonce is freely obtainable from the unauthenticated `ult-refresh-nonce` endpoint. Risk signals are mixed: the supplied vector is 9.8 with PR:N and the decision label is act_now, but exploitation still requires valid credentials for an account in a gated state; no public exploit identified at time of analysis.

Unauthenticated attackers can trash every published popup on WordPress sites running the Popup Builder plugin through version 4.4.5 by sending a single GET request with the sg_popup_preview_id parameter. The plugin fails to verify authorization for the trash action (CWE-862), and a second flaw in SGPopup::find() causes the request to match all published popups so the deletion runs against each of them, affecting integrity and availability of popup content with no confidentiality impact. CVSS 3.1 is 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H); no public exploit identified at time of analysis, and the vuln.today decision label is act_now.

Unauthenticated file disclosure in the Drupal 7 File Force Download module (versions 7.1.0 through 7.1.2) allows a remote visitor to append download=1 to a file URL and retrieve files stored in the temporary:// scheme or in a stream wrapper supplied by another module without the access checks that should apply. Files in the public:// and private:// schemes are explicitly not affected, and the supplied data contains no indication of active exploitation; no public exploit identified at time of analysis.

Account impersonation in pow-auth Assent's Sign in with Apple strategy (versions 0.1.25 through 0.3.1) allows an unauthenticated remote attacker to override verified ID token claims with a client-controlled callback parameter. An attacker who completes a genuine Sign in with Apple login using their own Apple ID can edit the `user` form parameter so that `sub`, `email`, and other claims are replaced; applications that use those values for account lookup, linking, verification, or access control then act on the attacker's identity. No public exploit code was identified at time of analysis, and a vendor patch is available in version 0.3.2.

Cross-tenant account takeover in ROOST Coop before 1.0.2 stems from the SAML verify callback resolving the authenticated user by email only, without binding that lookup to the organization named in the /saml/login/:orgId/callback path. An attacker who administers any organization on the instance and controls its SAML IdP signing key can post an assertion for a victim's email to a different organization's callback when the target organization has registered the same signing certificate, and receive a session as that victim. The attack is authenticated (PR:H in the vendor vector, since registering a SAML IdP requires organization administrator rights) and is only exploitable in the unusual shared-certificate configuration; there is no KEV listing and no public exploit identified at time of analysis, and the decision signal places remediation in the this-week window.

Unauthenticated GraphQL queries against Coop deployments earlier than 1.0.0 expose organization records and reviewer identity data, including org IDs, names, email addresses, website URLs, on-call alert addresses, and reviewers' IDs, names, roles, permissions, and creation dates. The flaw is missing authentication on the Query.allOrgs field reachable at /api/v1/graphql, rated CVSS 8.7 (CWE-306); any publicly accessible instance is affected, while authenticated private network placement prevents outside querying. The vendor advisory includes a public proof-of-concept GraphQL query, and the issue is fixed in Coop 1.0.0 via PR #699 / commit b29242f.

Broken object-level authorization in IXP Manager before 7.3.0 allows any authenticated user to view and edit another user's API-key record through the ApiKeyController edit/update path, which selects records by identifier without verifying that the caller's user_id matches. The flaw requires a valid account and a deployment with more than one user, and it is fixed in v7.3.0; this is a credible but not emergency-grade priority, with no public exploit code or active exploitation identified at time of analysis. The vendor states that upgrading to v7.3.0 should be applied as soon as possible.

Unauthenticated first-run administrator takeover in TAKO AI Agent for Okta (pip package okta-ai-agent) v3.0.0-beta: the POST /api/auth/setup endpoint in src/api/routers/auth.py performs no authentication, requires no one-time bootstrap token, and applies no network restriction, so any remote attacker who reaches a freshly deployed instance before the legitimate owner completes setup can create the sole admin account and receive a valid fctr_session JWT cookie. Because the default docker-compose.yml publishes port 8001 on all interfaces and the Dockerfile binds uvicorn to 0.0.0.0, a default deployment reachable from untrusted hosts is exploitable with a single HTTP request and no Okta tenant access; the attacker then controls Okta-synced user data, stored API tokens, chat history, and integration credentials. A public advisory includes full reproduction artifacts and working step-by-step exploit instructions (publicly available exploit code exists), and the release fixing the issue is v3.0.1-beta, which introduces an ephemeral in-memory setup token and binds the published port to 127.0.0.1 by default. Exploitation is limited to the first-run window: once setup is completed the endpoint returns HTTP 400, and deployments bound to localhost or an internal interface reduce exposure.

XML signature wrapping in LightSAML (4.x before 4.7.1 and 5.x before 5.0.1) lets an attacker who already holds one genuinely IdP-signed SAML assertion redirect signature validation to a buried copy of that genuine assertion while LightSAML consumes attacker-authored claims from a forged direct-child assertion, yielding authentication bypass and privilege escalation up to full impersonation of arbitrary NameID, Conditions and role attributes. The flaw requires only a low-privilege position (PR:L) - a captured earlier login response or the attacker's own legitimate assertion - and works even when the Service Provider enforces requireSignature=true, since the copied genuine ds:Signature still validates. Fixed in 4.7.1 and 5.0.1; the vendor advisory and a working PoC script are public, and no confirmed active exploitation (CISA KEV) or EPSS signal was provided at time of analysis.

Permanent deletion of product variants in Shopper's admin panel is possible for any authenticated staff member who holds edit_products but not delete_product_variants in versions before 2.10.0, because the Variants Livewire component's single and bulk Filament delete actions perform no server-side authorization check (CWE-285/CWE-862). The parent product edit page gates only on edit_products, so a user can load /shopper/products/{id}/edit, obtain the signed component state, and invoke callTableAction('delete', ...) or callTableBulkAction('delete', ...) against the Livewire endpoint; impact is greatest on ProductType::Variant products, where the sellable catalogue and the storefront product pages, cart and checkout can break. Shopper 2.10.0 adds ->authorize('delete_product_variants') to both actions; a public proof-of-concept test is referenced in the advisory but is not verified as working exploit code, and no CISA KEV entry or confirmed active exploitation is reported.

ZTNET through 0.7.18 allows any authenticated low-privilege user to deactivate another account, including an administrator, by submitting a victim's userId together with a deviceId that has no matching UserDevice row to POST /api/auth/user/invalidateUser; the handler then sets isActive=false and the victim's login is refused with account-expired. The root cause is a missing authorization check (CWE-862) in a Next.js API route, so impact is confined to account availability and administrative disruption, with no confidentiality exposure or code execution. A public proof-of-concept procedure confirmed against v0.7.18 is published in the vendor advisory, and the issue is fixed in 0.8.0; no CISA KEV entry is associated with this CVE.

Missing authorization in RAGFlow 0.25.2 through 0.27.2 allows any authenticated user who knows another user's private agent UUID to execute that 'Only me' workflow and read its output by posting to /api/v1/agents/chat/completions with "openai-compatible": true, a branch that returns before the UserCanvasService.accessible() check is reached. The attacker needs a valid account or API key (PR:L) plus the non-sequential agent UUID, and no victim-side configuration change is required because agents default to 'Only me'. Demonstrated impact is unauthorized private-workflow execution and output disclosure; retrieval of private data or side effects from configured tools depends on the victim workflow and was not demonstrated, and a public proof-of-concept walkthrough of the bypass exists, with no confirmed active exploitation reported. Version 0.27.3 contains the fix and this is prioritized for remediation this week.

Account impersonation in pgAdmin 4 server mode before 9.19 lets a user who successfully authenticates against a configured LDAP directory or Kerberos realm be logged into a different pgAdmin account that happens to share their username - including the built-in internal administrator created at first setup - inheriting that account's role, registered servers and saved database passwords. A second variant occurs when internal authentication is listed before LDAP or Kerberos in AUTHENTICATION_SOURCES: Flask-Security's internal form validation resolves the typed email to an account and retains it even though the password did not match, so a Kerberos or LDAP user can type another directory user's principal or email and be logged in as that user. Exploitation requires valid credentials for the directory or realm pgAdmin is configured to use (authenticated, PR:L) plus a username collision across sources; desktop mode and versions 9.19 and later are not affected, and no public exploit code was identified at time of analysis.

pgAdmin 4 server mode can be forced into unlimited password guessing against internal accounts, including the administrator's, because the three-attempt lockout is not applied consistently across every login path. The bypass is reachable by unauthenticated remote attackers (CVSS v4.0 score 9.2, PR:N) but still depends on guessing a valid password for an existing internal account; the independent assessment rates it CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H and assigns an act_now priority. No public exploit identified at time of analysis.

Improper authorization in the Filecoin Pin `upload-action` GitHub Action (versions ≤1.0.1, covering the entire 0.x line and 1.0.x) lets an external fork contributor get arbitrary artifacts produced by their pull request pinned to Filecoin using the repository owner's configured wallet, causing unauthorized storage expenditure, dataset pollution and drainage of wallet funds - without ever learning the wallet private key. The bypass only bites repositories that follow the documented two-workflow pattern, where an untrusted PR workflow builds an artifact and a privileged `workflow_run` workflow downloads and uploads it; the fork check in `upload-action/src/build.js` only inspects `event.pull_request`, which is absent on `workflow_run` events, so `isForkPR` evaluates to false and the upload is allowed to proceed. There is no CISA KEV entry and no confirmed working exploit; a public PoC reference (a sample event/simulation script) exists but is not verified as working exploit code, and no EPSS score was supplied. The vendor fixed the issue in 1.1.0 and explicitly will not backport to 0.x.

Authentication bypass in Delinea Secret Server before 12.3.1 lets a user skip the primary login step and authenticate by completing only the second-factor login step when two-factor authentication is configured. The vendor rates it 8.7 High; exploitation requires the attacker to be able to satisfy the second factor and is assessed as high complexity, so it is not a trivial unauthenticated bypass. No public exploit code or active-exploitation confirmation was identified in the available sources at time of analysis.

Delinea Secret Server versions earlier than 12.3.1 can return cloudadmin permissions to a user who submits an unsigned JWT under conditions not enumerated in the available sources, creating an authorization-bypass and privilege-escalation risk in a privileged access management product. The issue is network-reachable but rated high complexity and requires an existing privileged/authenticated context (CVSS PR:H), and it is remediated in 12.3.1. No public exploit code or CISA KEV active-exploitation confirmation was identified in the supplied data.

MyTube deployments running in multi-user mode (loginEnabled=true) expose all locally stored and cloud-proxied media - videos, thumbnails, small thumbnails, avatars, subtitles and cloud signed URLs - to unauthenticated clients because the static and cloud route handlers are mounted before the authentication middleware. An attacker with network reach to the instance can fetch `/videos/*`, `/images/*`, `/subtitles/*`, `/avatars/*`, `/api/cloud/thumbnail-cache/*` and `/cloud/videos|images/:filename` without any session cookie, token or user interaction, and can combine this with the separate hidden-video path leak to download media the operator intended to hide. The default single-user configuration (loginEnabled=false) has no authentication boundary and is not affected; the flaw is fixed in version 1.10.3, a public PoC reference (curl-based request examples) is documented in the advisory, and there is no indication of confirmed active exploitation (no CISA KEV listing).

MyTube through 1.10.2, when deployed in multi-user mode with loginEnabled=true and a visitor password configured, lets an authenticated visitor retrieve hidden (visibility=0) video records and then download the associated media and subtitles because the backend video queries and static media routes do not enforce the visitor's intended public-only role restriction. The GitHub security advisory includes a public proof-of-concept request sequence; it is not independently verified as working exploit code, and no CISA KEV entry or confirmed active exploitation was reported. Deployments using the default loginEnabled=false single-user mode are unaffected.

Unauthenticated broken access control in WP REST Cache 2026.3.1 and earlier lets remote attackers read data from affected WordPress sites without logging in, because a plugin-exposed REST function lacks an authorization check (CWE-862). The assessed impact is confidentiality-only (CVSS 7.5, PR:N/UI:N), and exploitation requires the plugin to be installed at an affected version; the exact endpoint and any configuration prerequisite are not described in the available sources. No public exploit was identified at time of analysis, and the priority is this_week rather than emergency.

Broken access control in the Husky Products Filter for WooCommerce plugin (realmag777) at version 1.4.6 and earlier allows remote, unauthenticated attackers to reach functionality that performs no authorization check, resulting in high-impact exposure of confidential data while integrity and availability remain unaffected. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) shows that no credentials or user interaction are required, and the CWE-862 classification confirms the root cause is a missing authorization check rather than a memory-safety or injection defect; the available sources do not identify the specific endpoint, action or feature that lacks the check. There is no CISA KEV listing and no public exploit identified at time of analysis, and the vuln.today priority decision is 'this_week'; no EPSS score was supplied with the intelligence.

Pending deposits in Cardano Hydra heads can be stolen by any third party who can observe the chain and submit a standard Cardano transaction. Versions prior to 2.1.0 ship a deposit validator (hydra-plutus/validators/deposit.ak, deployed via hydra-node <= 2.0.0) whose Claim branch only compares the deposit datum's head_id to the attacker-supplied redeemer currencySymbol and checks the transaction is before the deposit deadline; it never requires the Head state-token UTxO to be spent and never constrains outputs, so a standalone Claim transaction confirming before the deadline redirects the deposited assets to an arbitrary address. The attack is unauthenticated and needs no victim interaction, only a deposit in flight through POST /commit and not yet past its deadline (default three times depositPeriod, typically tens of minutes to hours); the vendor advisory publishes a full exploit walkthrough and devnet reproduction, and the flaw is fixed in 2.1.0. No CISA KEV listing is present in the supplied data.

Unauthenticated attackers can delete other users' saved drafts and seize their draft identifiers by abusing the 'previous_draft_id' parameter in the Forminator Forms WordPress plugin through version 1.57.3.1, letting them overwrite a victim's draft with attacker-controlled submission content. The nonce that nominally guards the request provides no barrier because any visitor can obtain it by loading a public form page; the real limiting factor is that the attacker must already know the victim's draft_id, which the advisory says may be harvested from a shared 'continue later' resume link, so this is not blind or arbitrary exploitation against every installation. No CISA KEV entry or confirmed public exploit code is available at time of analysis, though the issue is prioritized this_week and affects integrity only, with no confidentiality or availability impact under the assessed vector.

Unauthenticated attackers can read every WooCommerce customer's billing data through the Email Templates Customizer and Designer plugin (all versions up to and including 1.5.14) because its preview handler never checks whether the requester is authorized. Two unauthenticated requests suffice: one harvests a reusable nonce from the 302 Location header of an unguarded admin_init handler, and the second passes that nonce with an arbitrary order ID to the preview_order endpoint, returning billing name, address, phone and email; sites with many stored orders expose proportionally more PII. The issue is rated CVSS 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N, CWE-862) and is a priority for this week; no public exploit code or CISA KEV entry was reported in the available data.

Cluster identity spoofing in SUSE Rancher Fleet's registration flow allows an actor who already holds a valid registration token for a Fleet workspace to bind a crafted registration request to a different managed cluster in that same workspace, simply by claiming that cluster's client identifier. The actor gains credentials scoped to the victim cluster's Fleet management namespace, exposing Secrets and ConfigMaps synced there, permitting limited modification of bundle deployment and cluster status data, and disrupting Fleet's management of the cluster because the legitimate agent's registration and credentials are replaced. Exploitation requires a workspace registration token plus knowledge of a stable, non-secret client identifier, so it is a conditional identity/privilege issue concentrated in shared single-workspace deployments rather than a broadly unauthenticated remote compromise; no public exploit code has been identified at time of analysis, and deployment content itself cannot be altered through this flaw.

Arbitrary command execution on hosts running the @zuke/core MCP server in registry mode is possible because command-form registry descriptors were exempted from the ZUKE_REGISTRY_LAUNCH_HOSTS authorization applied to remote module descriptors. Affected are @zuke/core versions prior to 1.51.0 where an operator runs 'zuke mcp --registry --allow-run' against a registry writable by another party (a hosted HTTP registry sharing one token, or a shared .zuke/builds directory) and a run-capable caller invokes the affected tool; the registry writer then chooses the program and arguments executed with the operator's environment and workspace access. The vendor addressed it in 1.51.0, and no public exploit code has been identified at time of analysis. The local default registry populated only through 'zuke register' is not affected because that command writes module-form descriptors.

PipesHub 0.3.0 through 0.9.1 allows an authenticated user holding only the crawl:write OAuth scope to permanently destroy a connector instance and purge its graph records and embeddings by sending a crafted :connector path segment to the crawling manager schedule route. A value such as web.delete is concatenated into the published event type (web.delete.resync), which the Python connector service splits on the dot and dispatches to its delete handler, bypassing both the connector:delete scope check and the connector-lock guard enforced by the sanctioned DELETE /api/v1/connectors/:id endpoint. The privilege escalation is bounded to connectors the caller can already pass validateConnectorAccess for (their own personal connector, or an org admin's team connector); the vendor fixed the flaw in 0.10.0 by deriving the event action from the stored connector instance, and the advisory includes a verified, executed proof-of-concept walkthrough. The vulnerability is not listed in CISA KEV, and no EPSS score was supplied.

Cross-tenant file disclosure in abp-next-admin 10.4.0 through 10.7.0 lets any authenticated tenant user read blobs belonging to another tenant by supplying the victim's tenantId in the BlobManagement download-by-name request, which causes DownloadByNameAsync to switch tenant context and return the other tenant's stored files. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) matches the description: low-complexity, network-reachable, requires a valid logged-in account, and impacts confidentiality only. Exploitation is limited to deployments running in multi-tenant mode with more than one tenant storing blobs, and the attacker must know or guess both the victim tenantId and the blob name; a public PoC reference exists (a walkthrough write-up), and the vendor has addressed the issue in available patches.

Authenticated users with author or editor roles in SonicJS through 3.0.0 can create, modify, publish, or soft-delete documents they do not own because the content write routes check only coarse role labels and fail to enforce per-document ACLs or administrator deny overrides. The flaw requires a valid bearer JWT or API key and is bounded to content integrity and availability rather than data disclosure. A vendor fix is referenced by PR #1147, and no public exploit identified at time of analysis is reported in the supplied data, with no CISA KEV entry listed.

Unauthenticated attackers can install detection-suppression rules in SOCFortress CoPilot deployments before 0.1.77 because the Velociraptor Sigma exclusion endpoints never actually validate the bearer token they receive: an arbitrary, expired or forged value is decoded into a sentinel string ('Invalid token' / 'Expired signature') that is stored as the rule's creator instead of rejecting the request. A rule created with a null customer_code applies to every tenant, so matching Sigma alerts are silently dropped by process_sigma_alert before an incident is ever created, and any authenticated user down to the lowest-privilege customer_user role can additionally list, read, update, toggle and delete every exclusion because those routes carry no scope or tenant check. Version 0.1.77 fixes both paths. No confirmed active exploitation (not in CISA KEV) is reported, but the vendor advisory publishes a detailed two-step proof-of-concept reference for the unauthenticated create path that has not been independently validated here as working exploit code.

Unauthenticated active-response invocation and alert injection affect SOCFortress CoPilot deployments prior to 0.1.76 that leave GRAYLOG_API_HEADER_VALUE or VELOCIRAPTOR_API_HEADER_VALUE unset or unchanged, because both webhook header validators fall back to the same public constant shipped in `.env.example`. A remote attacker who supplies that known header value bypasses the JWT authentication that gates every other API, reaching POST /api/graylog/invoke to forward attacker-chosen COMMAND, ACTION, VALUE and AGENT_ID to the configured Wazuh manager (without the command-enum validation enforced on the authenticated invocation route), and reaching the threshold and velo-sigma alert routes to forge alerts for arbitrary customer_code values and drive attacker-controlled OpenSearch queries. The vendor's own advisory reports a confirmed live proof of concept against the published copilot-backend image; no CISA KEV entry is recorded and no EPSS score was supplied, but the priority decision label is act_now given the default-deployment exposure. Active-response delivery additionally requires a configured reachable Wazuh manager, and deployments that independently changed both header secrets are not subject to this bypass.

ManageEngine SharePoint Manager Plus build 4506 and earlier fails to enforce authorization on its MFA configuration functions, so any authenticated low-privileged user can read or change MFA settings, enable or disable MFA application-wide, enumerate MFA-enrolled users, and delete MFA enrollments. This can weaken authentication protections or lock legitimate users out of the application; the vendor fixed the issue in build 4507. It is a moderate-priority issue (vuln.today Decision label: this_week) rather than an emergency, and no public exploit was identified at time of analysis.

Authenticated horizontal privilege escalation in Vvveb CMS before 1.0.8.7 allows any administrator - including one deliberately denied the 'view_other_admin' and 'edit_other_admin' capabilities - to read and overwrite another administrator's REST API tokens by changing the admin_id GET parameter on admin/auth-token. The stolen token can then be replayed against the REST API with a Bearer header to act as the victim administrator, so the impact escalates to full account takeover of a higher-privileged admin. Exploitation requires a valid authenticated administrator session (CVSS PR:H, no user interaction), the vendor states the issue is fixed in 1.0.8.7, and a public PoC reference with reproduction steps exists in the GitHub security advisory; it is not verified as working exploit code, and there is no KEV listing indicating active exploitation.

Vvveb CMS before 1.0.8.7 exposes its password-reset flow to unauthenticated account takeover: an attacker supplies a valid username and a PHP array-style token parameter (for example token[]=), and the handler accepts the reset without a legitimate token. The GitHub advisory documents reproduction steps leading to arbitrary password changes, including administrative accounts, and the vuln.today decision is act_now with a 9.8 CVSS vector (AV:N/AC:L/PR:N/UI:N). A public proof-of-concept is documented in the advisory; no CISA KEV listing is present in the supplied data.

Songloft 2.9.0 through 2.13.5 ships an embedded Go backend that falls back to the fixed credential pair admin/admin whenever the administrator username and password are omitted from configuration, letting anyone who can reach the service on the local network log in as administrator through /api/v1/auth/login. From that session an attacker can rewrite library and configuration settings and install JavaScript plugins that execute inside the bundled QuickJS runtime, giving code execution in the server context; the mobile/embedded startup path binds 0.0.0.0, which is what makes the service LAN-reachable in the first place. The issue is unauthenticated from the network perspective (CVSS:4.0 AV:A/AC:L/PR:N/UI:N, 8.7; assessed as CVSS:3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is bounded by two things: the attacker must be on an adjacent network, and operators who set a strong admin password are not affected. A public technical writeup describing the admin-takeover attack exists and is referenced by the CVE record, though it is not verified as working exploit code; vendor-released patch 2.13.6 is available and the priority label is this_week. No public exploit code is confirmed and the CVE is not listed as actively exploited (CISA KEV).

Authentication bypass in MuseBot releases before 2.0.0 lets remote unauthenticated attackers forge an administrative session by signing a MuseBot-session cookie with the hard-coded default session_key 'muse_bot_session_key', which ships as the built-in default of the -session_key flag. Any deployment whose admin HTTP interface is network-reachable and which never overrode that default is fully compromised: the forged cookie carries an attacker-chosen user_id and yields administrative access to password hashes, chat records and bot configuration, and allows bots to be stopped. The vendor has released 2.0.0, which auto-generates and persists a random key and actively rejects the legacy default; no CISA KEV entry or public exploit code is confirmed at time of analysis, though a public technical writeup of the bypass exists, so exposure of admin endpoints should be treated as urgent.

Privilege escalation in DataCap (devlive-community) through 2025.1.1 lets any authenticated user, including one who simply self-registered, take full control of the instance by sending a PUT request to /api/v1/user/allocationRole to assign the administrator role to their own account; the same gap extends to administrative role and menu management endpoints. Exploitation needs only a low-privileged account and network reach to the REST API, with no user interaction and no privileged credentials. A public technical writeup and source-level references describing the flaw exist, and no CISA KEV entry appears in the supplied data; the vulnerability is rated 8.7 (CVSS 4.0) and flagged for this-week prioritization.

Improper authorization in Orchard CMS 1.10.3 through 1.11 allows authenticated users holding the Author or Contributor role to display, clone and delete other users' media items by referencing their content ids, and to delete arbitrary media folders through FolderController.Delete(), because the media folder permission check never validates ownership. Exploitation requires a valid low-privilege account (CVSS 4.0 score 7.1 with PR:L), so anonymous or unauthenticated visitors cannot trigger it; risk is confined to multi-user sites that provision Author/Contributor accounts for semi-trusted people. A public technical write-up describing the issue exists but is not verified as working exploit code, and no CISA KEV entry or vendor-released fixed version appears in the available data.

Missing authorization in the doc::ajaxGetDoc() handler in ZenTao PMS through 22.6 lets any authenticated user - including a low-privilege account - read the body and draft content of private and access-restricted documents by enumerating sequential document IDs, because the handler returns content without calling checkPrivDoc(). The vendor issue tracker entry (GitHub issue #215) and a public technical writeup describe the flaw, and no fixed version is identified in the available data; exploitation is limited to confidentiality impact and requires only a valid login (PR:L, UI:N). No public exploit code has been confirmed and there is no CISA KEV entry, though a public PoC reference exists in the form of a third-party technical writeup that has not been verified as working exploit code.

Authentication bypass by spoofing in Dell OpenManage Enterprise versions prior to 4.8.0 lets an unauthenticated attacker who has adjacent network access hijack existing user sessions, scoring CVSS 3.1 base 7.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N). The attack is low in complexity and needs no credentials or user interaction, but it is bounded to attackers positioned on the same local or management network segment as the OpenManage Enterprise console rather than the open internet. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor's stated complete fix is upgrading to version 4.8.0 or later.

mTLS client authentication can be silently bypassed in Traefik 3.7.0-ea.1 through 3.7.14 when the Kubernetes Ingress NGINX provider is used and a second Ingress on the same host declares a path without matching auth-tls-secret settings. With core.strictTLSOptions disabled, Traefik falls back to default TLS options that do not request a client certificate, allowing unauthenticated remote attackers to reach backends intended to require mTLS. No public exploit identified at time of analysis; exploitation requires the non-default multi-Ingress same-host configuration collision described by the vendor.

Improper access control in ESET Endpoint Encryption up to 5.4.23.0 and ESET Full Disk Encryption up to 2.4.4.0 on Windows allows a local standard user to open a device interface exposed by a privileged ESET kernel driver and submit specially crafted requests, resulting in high confidentiality, integrity and availability impact on the affected endpoint. The flaw is local only and requires an already-established low-privileged account (CVSS:4.0 PR:L, independently assessed as CVSS:3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.5), so exposure is confined to managed Windows endpoints running these encryption products below the fixed builds. No public exploit code or active exploitation is identified in the available data, and the vendor has published a fixed-build advisory (ESET ca9033).

Authentication bypass in the Polish Social Insurance Institution (ZUS) Płatnik desktop client lets an attacker who can run or manipulate a client instance connected to the backend server skip the login verification step and authenticate as an arbitrary user without credentials. The flaw is rooted in client-side authentication (CWE-603), and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L - unauthenticated from a privileges standpoint, but gated by local access to a deployed, backend-connected client, which is the main exposure limiter; CERT-PL reports it as EUVD-2026-113776 and the vendor states it is fixed in metric 242 of version 10.02.002. No public exploit code or active exploitation has been identified at time of analysis, and the vuln.today decision label places remediation in this week's patch cycle rather than an emergency response.

FTPS data connections on vsftpd through 3.0.5 can be hijacked by a second client that resumes its own TLS session ticket against the victim's passive-mode data port, allowing theft of downloaded files or injection of content into uploads. The attacker must not be authenticated and must originate from the same source IP as the victim (shared NAT, VPN/proxy egress, or multi-tenant host) and win a timing race for the PASV connection, which is why the assessed CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N with confidentiality and integrity impact but no availability impact. No confirmed working exploit code or CISA KEV entry is present in the available data, although the researcher's technical writeup is referenced, and vuln.today assigns an act_now decision label for any environment running FTPS on vsftpd ≤3.0.5.

WebAuthn-based two-factor authentication can be bypassed in phpMyAdmin through 5.2.3, letting an attacker who already holds a victim's valid MySQL username and password complete login to the database interface without ever satisfying the second factor. The defect is in CustomServer::parseAndValidateAssertionResponse(), which checks the challenge, origin and rpIdHash of a submitted webauthn_request_response but never verifies the assertion signature against the stored public key, so a forged response with matching metadata is accepted. Only accounts that have opted into WebAuthn/FIDO2 as their phpMyAdmin second factor are affected, and the attacker must be authenticated with first-factor credentials (PR:L) and able to reach the phpMyAdmin interface; no public exploit code is confirmed at time of analysis, though a public research writeup of the flaw exists and priority is rated this_week.

OpenLiteSpeed through 1.9.4 allows unauthenticated remote attackers to bypass virtual-host client-certificate (mTLS) enforcement on HTTP/3/QUIC listeners when one instance hosts both an mTLS-protected virtual host and a non-mTLS virtual host. QuicStream inherits a verifyContext() implementation that always returns true, so a crafted QUIC request can present the non-mTLS host's SNI alongside a protected Host header and reach content that should require a client certificate. The CVSS 4.0 score is 8.2 with confidentiality-only impact, the priority label is this_week, no CISA KEV entry is provided, and a public research write-up is referenced but working exploit code is not confirmed.

Jellyfin through 12.4 allows any authenticated non-administrator to bypass library and parental-control restrictions through SuggestionsController.GetSuggestions when the userId parameter is omitted. An attacker can repeatedly call GET /Items/Suggestions without userId to enumerate restricted item IDs and server filesystem paths, then stream the restricted media; the CVSS 4.0 vector confirms network access, low privileges (PR:L), no user interaction, and high confidentiality impact with no integrity or availability impact. A public research write-up is referenced, but working exploit code is not verified in the provided data; no CISA KEV entry is provided, and the vuln.today decision label is this_week.

Unauthenticated webhook forgery in Juspay Hyperswitch before 1.128.0 allows an attacker who knows a merchant_id and the matching Worldpay orderCode to POST unsigned XML into the worldpayxml webhook endpoint and drive payment state transitions - most damagingly a lastEvent value of SETTLED that marks an unpaid order as charged, with refund, dispute and payout events reachable by the same path. Only deployments that have the Worldpayxml connector enabled are exposed, and the connector's verify_webhook_source returned true unconditionally, so no signature check or mTLS stood between the request and the state machine. No CISA KEV entry has been recorded for this issue and there is no confirmation of active exploitation; a public research writeup describing the unsigned-webhook technique exists but is not verified as working exploit code, and the vendor has released fixes in v1.128.0 and 2026.10.01.0.

Unauthenticated attackers who hold a merchant's publishable key and a valid payout identifier can confirm payouts in Juspay Hyperswitch through 1.128.0 and in builds before 2026.10.19.0, because the confirmation handler does not compare the supplied client_secret with the payout's stored secret. A successful call can overwrite amount, currency, connector and routing fields and trigger unauthorized merchant payouts. The vendor has released a fix, the issue is prioritized for remediation this week rather than as an emergency, and a public research write-up is referenced but working exploit code is not confirmed in the supplied data.

Lago's acceptInvite GraphQL mutation (all versions through 1.55.0) issues a valid session JWT for a pre-existing account without verifying that account's password, so an attacker who already holds an organization-administrator role can invite a victim's email address, accept the invite with a password of their choosing, and receive a token that grants access to the victim's organizations, billing data, API keys and payment integrations. Exploitation is authenticated (CVSS 4.0 PR:L) and limited to organizations using the EMAIL_PASSWORD authentication method; SSO-backed organizations are not reachable through this path because the identity provider already validates the email claim, and no victim interaction is required. No public exploit code is confirmed at time of analysis, although a public research writeup describing the attack chain exists, and the vendor has published an upstream fix commit.

Delta UFC500 chargers expose web server POST and PUT actions without authentication, allowing an attacker on the adjacent network to reboot the device and, if the configid can be brute-forced, set the service password and alter arbitrary settings. The flaw is a CWE-306 missing-authentication issue rated CVSS 8.7, with high confidentiality and integrity impact and lower availability impact; the independent assessment notes that network segmentation or isolating the charger management interface materially reduces realistic exposure. No public exploit identified at time of analysis, and the vuln.today decision label is this_week.

Broken access control in the Cloud Foundry Cloud Controller API leaves the /internal/v3/staging/:guid/droplet_completed and /internal/v3/staging/:guid/build_completed callback endpoints reachable on the public API listener, because the shipped Nginx routing configuration carries deny rules for /internal/v4/ and /internal/v5/ but omits the equivalent rule for /internal/v3/. An attacker who holds a valid build or droplet GUID - and a SpaceAuditor can enumerate those GUIDs without any write permission - can post a forged staging callback, transition a droplet to STAGED, and persist arbitrary process and sidecar metadata with no associated package or actor, escalating past the intended role boundary. No public exploit code was identified at time of analysis, and the vendor has published fixed versions; triage guidance places remediation in this week's work rather than an emergency response.

Unauthenticated OS command execution is possible on Teltonika Networks RUTOS devices (RUT, RUTX, RUTM, RUTC, ATRM, TAP, CAP, OXA, DAP, TRB, OTD, EBG) running versions 7.22 through 7.24.2 and TSWOS devices (SWM, TSW) running versions 1.9 through 1.10: an attacker who can reach the device's service interface from an adjacent network segment can call internal LUA functions directly, bypassing the validation that normal API requests enforce, and thereby execute operating-system commands with high impact on confidentiality, integrity and availability of both the device and connected systems. No authentication or user interaction is required once that network position is achieved, and the adjacency requirement is the principal limiting factor. No public exploit code has been identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); the vuln.today decision label is act_now, driven by the unauthenticated code-execution outcome combined with the wide affected device family.

Unauthenticated attackers can register an OAuth client with an attacker-controlled redirect URI against the AI Engine WordPress plugin's MCP OAuth 2.1 Dynamic Client Registration endpoint in all versions through 3.8.6, then obtain an administrator-bound MCP access token once an administrator approves the client on the OAuth consent screen - approval that can be obtained via clickjacking because the consent page lacks X-Frame-Options and CSP frame-ancestors. The flaw is CWE-862 missing authorization, caused by the register endpoint being exposed with a permission_callback of __return_true, and it is fixed in 3.8.7. Exploitation requires the opt-in MCP labs module to be active and administrator interaction (UI:R); no public exploit code and no CISA KEV entry are identified in the available data, and this is a high-severity, approval-gated issue rather than a drop-everything emergency.

Authentication bypass in the WordPress Security Plugin, Firewall & Malware Scanner with Auto Removal (versions before 2.191) allows anyone holding a user's current authenticator-app code to log in as that user, including an administrator, without supplying the account password. Exploitation is conditional: the site must run an affected version and the target account must use authenticator-app (TOTP) two-factor authentication, and the attacker must obtain a valid, time-limited code. No public exploit identified at time of analysis; SSVC lists exploitation as none, EPSS is 0.13% (3rd percentile), and the vendor has released version 2.191 as the fix.

Arbitrary code execution as LocalSystem is possible through the privilege manager agent in Delinea Privilege Manager builds 10.1.0 through 12.0.5796 and 13.0.0 through 13.0.1058, rooted in missing authentication for a critical function (CWE-306). The severity picture is genuinely contested: the vendor CVSS 4.0 vector scores 8.7 but requires high privileges (PR:H), active user interaction (UI:A), elevated attack complexity (AC:H) and specific attack requirements (AT:P), while our assessed CVSS 3.1 vector treats the same flaw as unauthenticated (PR:N) network-reachable with high confidentiality, integrity and availability impact. Because the exact trigger is not described in the available sources, defenders cannot yet confirm whether default deployments are exposed; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV, though the vuln.today decision label places remediation in this week's work.

Unauthenticated content disclosure in Bricks Theme 2.4 and earlier for WordPress lets anonymous attackers read draft and unpublished page content through the load_popup_content REST endpoint. Any remote attacker can obtain a public nonce via the bricks_regenerate_query_nonce action and then increment the popupId parameter on /wp-json/bricks/v1/load_popup_content to enumerate confidential drafts across the site, because the endpoint applies no post-status or capability check. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) confines impact to confidentiality - there is no write access, authentication bypass into administrative functions, or code execution; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the decision label places remediation in the current week rather than as an emergency.

Sandbox escape in the ServiceNow AI Platform lets an authenticated user holding the admin role bypass Rhino JavaScript sandbox restrictions and execute arbitrary code on the underlying host operating system, with potential for further unintended access. The flaw is rated 9.4 under CVSS 4.0 and maps to CWE-284 (improper access control), and because the privilege prerequisite (PR:H) is an admin session, the practical threat model is a privileged insider or an attacker who has already compromised an admin account rather than an unauthenticated remote adversary; no user interaction is required. ServiceNow states it has already updated hosted instances and shipped the fix to partners and self-hosted customers, and that it is not aware of malicious exploitation, so residual exposure sits with self-hosted and partner-managed deployments that have not yet applied the update; no public exploit code has been identified at time of analysis, and the vendor advisory does not publish a specific triggering path.

PKCS#12 MAC forgery and constant-key password-based decryption in node-forge 1.4.0 and earlier let anyone who does not know a PFX password tamper with a PKCS#12 file - swapping in attacker-chosen certificates or an unencrypted private key - and have forge.pkcs12.pkcs12FromAsn1() report the MAC as verified under whatever password the application supplies. The root cause is that a MacData iteration count of zero or less is accepted from the input, collapsing the RFC 7292 Appendix B.2 key derivation to a public constant (0x03 repeated); the same KDF is used by the pbeWithSHAAnd3-KeyTripleDES-CBC and pbewithSHAAnd40BitRC2-CBC schemes, so shrouded key bags, encrypted SafeContents and PKCS#8 ENCRYPTED PRIVATE KEY input handled via forge.pki.decryptPrivateKeyInfo() likewise decrypt with any password. The vendor advisory ships a working proof-of-concept and the fix commit adds it to tests/pocs/; no CISA KEV listing exists and exploitation is limited to applications that import PKCS#12 or encrypted PKCS#8 material from untrusted parties and rely on MAC verification or successful decryption as proof of password knowledge. With CVSS 3.1 scored 7.5 (AV:N/AC:L/PR:N/UI:N, integrity-only impact) this is a genuine integrity bypass but not an emergency for deployments that only load their own trusted keystores; it should be remediated this week given the public PoC.

Symlink following during same-client allocation data migration in HashiCorp Nomad and Nomad Enterprise allows a workload controlled by a tenant to redirect the ownership and permission changes Nomad applies to allocation data onto host directories, corrupting host file permissions and enabling privilege escalation. Only clusters that schedule untrusted or multi-tenant workloads on shared clients are meaningfully exposed, because the vector is local (AV:L) and requires an attacker to already control a running allocation (PR:L); remote unauthenticated exploitation is not possible. HashiCorp fixed the flaw in Nomad 2.1.0 and Nomad Enterprise 2.1.0, 1.11.12 and 1.10.18, and no public exploit code was identified at time of analysis.

Cross-shop context confusion in the Shopify shopify_app Ruby gem (versions 22.1.0 through 23.0.2) allows an authenticated attacker holding a valid Shopify session or ID token for one store to supply a different `shop` query parameter and have application code treat that requested shop as the current shop. The flaw is only exploitable where the host application uses token-exchange authentication and relies on `current_shopify_domain` or `params[:shop]` for authorization, tenant lookup, stored access-token selection, or shop-scoped data access, so impact is conditional on each app's own scoping logic; apps that derive shop identity from `current_shopify_session.shop` or the verified JWT `dest` claim are not affected. The vendor-released fix is version 23.0.3, and no public exploit code or confirmed active exploitation was identified at time of analysis, though the flaw is rated this_week priority by vuln.today and carries a vendor CVSS 4.0 score of 7.6.

Incorrect authorization in the issuer resolution logic of AWS Private CA Connector for Kubernetes (aws-privateca-issuer) before v1.10.1 allows an authenticated remote user to obtain certificates - including subordinate CA certificates - signed by a cluster-scoped AWS Private CA issuer that their approval policy does not authorize. Affected are clusters running the connector releases up to and including 1.10.0 (Helm chart <= 1.10.0) or the AWS Private CA Connector for Kubernetes EKS add-on before v1.10.1-eksbuild.1; per the CVSS 4.0 vector (PR:L, no user interaction) the attacker must already hold authenticated cluster credentials with namespace-scoped certificate-approval rights, and a cluster-scoped issuer must exist to be targeted. Vendor patches are available in v1.10.1 / v1.10.1-eksbuild.1, no public exploit code has been identified at time of analysis, and the flaw is rated for remediation this week by current prioritization signals.

Missing authorization in ZITADEL's hosted Login V2 UI allows one-click account takeover: an attacker who starts an OAuth 2.0 Device Authorization for any application with the Device Code grant type can send a signed-in victim a single link carrying the attacker's user code, and the victim's browser approves the attacker's device without consent or entering a code, delivering the victim's access, ID and (if requested) refresh tokens to the attacker's device. ZITADEL instances running 4.0.0 through 4.19.4 and 3.0.0 through 3.4.15 are affected, and unauthenticated remote attackers can also reach the same gap through the OIDC service API endpoint POST /v2/oidc/device_authorization/{device_authorization_id}, which skips the 'Only authorized users can authenticate' and project-grant restrictions that normal sign-in enforces. The victim must open the link while holding an active Login V2 session in that browser (passive user interaction), the attacker cannot read the victim's password or second factors, and instances with no Device Code application, or users who only use hosted Login V1, are not affected; no public exploit code was identified at time of analysis, and the vendor rates this a genuine high-priority issue rather than a high-score/low-risk case.

Account takeover in ZITADEL's hosted Login V2 UI allows unauthenticated remote attackers to seize active users who have not yet registered any authentication method. The verificationCheck cookie is only a SHA-256 hash of the user ID and the browser fingerprint cookie with no server-side secret, so anyone who knows a user ID or login name can forge it and set a password, register a passkey, or link an attacker-controlled identity provider, then sign in as that user. ZITADEL 4.0.0 through 4.19.4 (including RC versions) are affected and 4.19.5 fixes the flaw; no public exploit code has been identified at time of analysis, yet priority guidance is to act now because the impact is unauthenticated takeover of accounts that gate downstream applications.

Improper access control in the Web Admin console of Progress WS_FTP Server on Windows, in versions prior to 2024.0.7 on the 2024 branch and prior to 2025.0.4 on the 2025 branch, lets remote, unauthenticated callers reach administrative functionality, carrying a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/C:H/I:H/A:H). The high attack complexity signals that a specific precondition must hold before exploitation succeeds, although the trigger itself is not described in the available sources. No public exploit has been identified at time of analysis, and vendor-released fixes are available for both branches.

Progress WS_FTP Server on Windows exposes sensitive information, including administrative credentials, to unauthenticated remote attackers because of improper authentication in releases before 2024.0.6 and before 2025.0.3. The maximum CVSS score of 10.0 and the vuln.today act_now label reflect a network-reachable, no-prerequisites authentication bypass with changed scope and high confidentiality, integrity, and availability impact; patched releases are not vulnerable. No public exploit was identified at time of analysis, and the available sources do not confirm active exploitation.

Security feature bypass in Microsoft Edge (Chromium-based) lets unauthenticated remote attackers evade an incomplete input denylist and bypass a security feature when a victim opens attacker-controlled content. Microsoft rates the flaw CVSS 8.8 with network attack, low complexity, no privileges, and required user interaction; the precise security feature and evading input are not described in available sources. No public exploit was identified at the time of analysis, and a vendor patch is available per the MSRC update guide.

IBM Langflow OSS 1.0.0 through 1.12.8 allows unauthenticated remote attackers to bypass security restrictions through improper authentication, with a CVSS 9.8 vector indicating high confidentiality, integrity, and availability impact and no privileges or user interaction required. The vendor has published a patch and the vuln.today priority is act_now, though no public exploit was identified at the time of analysis. Network exposure is the main practical limiter, since instances behind VPNs, authentication proxies, or localhost-only access are less reachable.

Remote authenticated SQL command execution affects IBM Langflow OSS 1.0.0 through 1.12.3: an attacker holding a valid account can abuse improper access control to run arbitrary SQL, with high confidentiality and integrity impact. Authentication requirements (CVSS PR:L) narrow exposure to instances with multiple, shared, or untrusted users, and the vendor has published a patch; no public exploit was identified at time of analysis, and CISA SSVC reports no known exploitation.

IBM Langflow OSS 1.0.0 through 1.12.4 contains a missing authorization check (CWE-862) that allows a remote authenticated low-privileged user to execute arbitrary code, with high confidentiality, integrity, and availability impact. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H makes valid low-privileged access the key prerequisite rather than unauthenticated reachability. No public exploit was identified at time of analysis, SSVC records exploitation as none, and a patch is available from IBM; this is a credible, high-priority vulnerability but not an emergency.

Authenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.12.4 lets any holder of a low-privileged account configure a built-in code-execution component with attacker-supplied inputs, bypassing the administrator-only restriction and achieving arbitrary code execution with high confidentiality and integrity impact. Exploitation requires a valid low-privileged account and network access to the Langflow OSS instance, with no user interaction required; no public exploit identified at time of analysis. This is a genuine priority rather than a high-CVSS/low-risk artifact, given the low-privilege prerequisite and the availability of a vendor patch.

Sensitive information disclosure in IBM Langflow OSS 1.0.0 through 1.12.4 stems from improper authentication (CWE-287), allowing a remote attacker to reach protected functionality or data without proving identity and read information they should not have access to. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) confirms the flaw is network-reachable and requires no authentication or user interaction, with high confidentiality impact and no integrity or availability effect. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has published a fix; exposure is limited to instances running an affected 1.0.0-1.12.4 release that are reachable by an attacker.

Privilege escalation in OpenStack keystonemiddleware before 13.0.2 lets an authenticated holder of an access-restricted application credential escape that credential's intended scope by adding a custom X-Service-Token header to an API request, producing high confidentiality and integrity impact (CVSS 3.1 base 8.3; CWE-863 Incorrect Authorization). Any OpenStack deployment whose API services validate tokens through a vulnerable keystonemiddleware release is exposed, and exploitation requires a pre-existing restricted application credential (PR:L in the vector), so it is not anonymous. No public exploit code and no CISA KEV entry were identified at time of analysis, and the vendor fix ships in keystonemiddleware 13.0.2.

Elastic Cloud Enterprise (ECE) hosts that have not applied the 4.2.1 security update are exposed to a symlink-following flaw (CWE-59/CAPEC-132) that can give a high-privileged local user read and write access to data belonging to other deployments co-located on the same host. Exploitation requires local, high-privilege access within a deployment (CVSS AV:L/PR:H) plus a multi-tenant host running two or more deployments, and high attack complexity (AC:H) reflects conditions the attacker does not fully control; single-deployment hosts and remote unprivileged attackers are not exposed. No public exploit code or PoC is identified in the available data, and the priority signal is this_week rather than emergency, consistent with the substantial prerequisites.

Elastic Cloud Enterprise (ECE) instances that host multiple deployments on a single multi-tenant host are exposed to cross-deployment data disclosure and loss, because a symlink planted from within one deployment can be followed by ECE across the deployment boundary. Per the supplied CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H, base 8.2), exploitation is local and requires an attacker who already holds high privileges inside a co-located deployment; the resulting impact lands on other tenants' data, which is what drives the scope change and triple-high confidentiality, integrity and availability ratings. No public exploit code or active exploitation is identified in the available intelligence, and the only confirmed remediation is upgrading to ECE 3.8.6 or 4.2.1 as stated in the vendor security advisory (ESA-2026-216); per the vuln.today priority this is a this_week item, with severity concentrated in shared-host, multi-deployment environments rather than in single-tenant or isolated installations.

Elastic Cloud Enterprise (ECE) 3.x before 3.8.6 and 4.x before 4.2.1 can allow a local, highly privileged attacker to exploit improper symbolic-link resolution and bypass authentication to alter another deployment's configuration on the same host. The flaw is rated CVSS 7.2 with local access, high privileges, high attack complexity and changed scope; it is not reported as actively exploited and no public exploit was identified at time of analysis. Risk is genuine but constrained to environments where an attacker already has local high-privilege access and multiple deployments share the host.

Missing authorization in the HANDMADE - Dropshipping for Etsy and WooCommerce plugin through 1.0.10 lets a low-privileged authenticated user perform actions that should be restricted, with the assessed CVSS 7.1 impact concentrated on availability (A:H) and limited integrity effects (I:L) rather than data disclosure. The plugin must be installed and active on a WordPress/WooCommerce site, the attacker needs network access and a valid low-privilege account, and no user interaction is required; the exact vulnerable feature or endpoint is not described in the available sources. No public exploit identified at time of analysis, and this is a moderate-priority issue rather than a top-tier emergency.

Missing authorization in the GEO my WordPress plugin through version 4.5.5.5 allows remote unauthenticated attackers to reach data they should not be able to access, producing a high confidentiality impact with no integrity or availability effect. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (base 7.5), consistent with CWE-862 Missing Authorization and the Patchstack classification as broken access control. No public exploit code and no CISA KEV entry are identified in the available data, and the specific vulnerable endpoint or parameter is not described in the supplied sources.

Missing authorization in the ThimPress LearnPress WordPress plugin, affecting versions through 4.4.11, allows unauthenticated remote attackers to reach functionality that should be access-controlled and disclose data they are not entitled to read. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) indicates no authentication, no user interaction and no non-default configuration are needed, so any internet-reachable WordPress site running an affected LearnPress release is exposed; the impact is confidentiality-only, with no integrity or availability effect. No public exploit code or confirmed active exploitation was identified at time of analysis, and the issue is tracked by Patchstack under a broken-access-control advisory; the specific endpoint or parameter whose authorization check is missing is not described in the available sources.

Broadcast Live Video, a WordPress plugin from VideoWhisper.com, fails to enforce authorization checks in versions through 7.3.9, letting a logged-in low-privilege user reach actions that should require higher permissions. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H, 7.1), the result is no confidentiality exposure but low integrity and high availability impact, with no user interaction required. Exploitation requires a valid account on the target site, so installations with open or self-service registration carry the widest attacker pool; no public exploit code has been identified at time of analysis and the flaw is not in CISA KEV, though Patchstack's priority guidance places remediation in the current week.

Foxit's hosted HTML-to-PDF conversion service used a shared token for submitted documents, so an unauthenticated remote attacker who obtained or reused that token could access conversions submitted by other users (CWE-639). The exposure is limited to documents processed through Foxit's online converter before the vendor's 2026-10-29 remediation, with confidentiality-only impact; no public exploit code was identified at time of analysis.

Third-party authorization credentials were embedded directly in client-side JavaScript served by the Foxit website (foxit.com), letting any visitor read them without authentication or user interaction and potentially reuse them against the third-party service they authorize. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N, base 8.6 High) fits that exposure exactly, including the scope change that reflects impact landing on a separate third-party system rather than on foxit.com itself. EUVD records the affected range as foxit.com before 2026-10-29, and no public exploit code was identified at time of analysis; realistic risk depends on the privileges of the specific third-party service the leaked credentials grant, which has not been disclosed.

Unauthenticated SQL injection in the password-recovery functionality of the Radius Xenia M2M Platform web management interface can let a remote attacker read sensitive data, enumerate the database schema, or alter records. The issue is rated 9.3 (CVSS 4.0) and is prioritized act_now by vuln.today; no public exploit identified at time of analysis, and no CISA KEV listing is provided. Exposure is the key constraint: only instances whose management interface is reachable from the attacker's network position are at risk.

Two-factor authentication bypass in the WordPress "Two Factor Authentication" plugin before 1.17.0 and in All-In-One Security (AIOS) before 5.5.0 lets an attacker who already holds a victim's password complete the victim's second-factor check using a code from the attacker's own 2FA-enabled account, resulting in a session as the victim. The flaw is rated 7.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) and requires two preconditions: knowledge of the victim's password and a separate, valid 2FA-enabled account on the same WordPress site. It is not listed in CISA KEV, SSVC records no known exploitation and marks it not automatable, and only a public PoC reference exists that is not verified as working exploit code.

Authentication bypass in the Wild Apricot Login plugin for WordPress (all versions through 1.0.18) allows a remote attacker with low privileges (CVSS PR:L) to obtain a valid network-global WordPress authentication cookie for an existing subsite administrator without knowing that administrator's password. The described path requires a path-based WordPress Multisite network, the plugin active on at least one subsite, a WildApricot organization that permits public zero-fee membership signup, and an attacker-controlled WildApricot contact whose email exactly matches the victim administrator's email with no existing contact-ID mapping. Exploitation is conditional and high-complexity per the assessed CVSS vector; no public exploit identified at time of analysis and no CISA KEV entry is present in the provided data, and the priority label is this_week.

Authentication bypass in the SSL Wireless SMS Notification plugin for WordPress (all versions through 3.8.1) lets unauthenticated remote attackers take over any account that has a phone number linked via the plugin's sslcare_login_phone user meta, by calling the public final_login_ajax_action handler with a matching phone and attacker-chosen cap_data - the handler issues an authenticated session without verifying the SMS OTP or any server-side single-use state. Exploitation requires that the target account enrolled a phone through this plugin and that the attacker knows that phone number; impact escalates to full site compromise when the targeted account is an administrator. No public exploit code has been identified at time of analysis, and the issue is prioritized for remediation this week.