Monthly
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.
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.
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.
An authorization bypass in Netmaker through 1.7.0 lets an authenticated user who holds external-client permissions on just one network reach into external clients belonging to other networks by sending PUT requests to /api/extclients/{network}/{clientid} - replacing public keys, disabling clients and retrieving WireGuard private keys. The CVSS 4.0 score of 8.7 reflects network reachability, low complexity, high confidentiality and integrity impact with only low privileges required (PR:L) and no user interaction, and the unscoped lookup is present in default deployments rather than needing special configuration. No public exploit code or confirmed active exploitation (CISA KEV) is identified in the available data, and the upstream fix is carried in PR #4153 / commit 332d8b9.
Cross-organization schedule deletion and disabling in Trigger.dev before 4.5.6 allows authenticated users with their own project schedule route to target another organization's IMPERATIVE cron schedule by supplying the victim schedule's friendlyId to delete or disable actions. The flaw is a CWE-639 authorization bypass/IDOR in DeleteTaskScheduleService and SetActiveOnTaskScheduleService, which resolve the friendlyId without scoping it to the caller's organization; exploitation requires authentication and knowledge or enumeration of the victim's friendlyId, and impact is limited to schedule integrity/availability with no data disclosure. No public exploit was identified at the time of analysis, and CISA KEV does not list this CVE.
Trigger.dev before 4.6.0 fails to enforce organization scoping in the waitpoint token wait endpoint, allowing an authenticated attacker who holds any valid secret API key to supply another organization's run ID and make that run block indefinitely on a waitpoint the victim cannot complete; the same path can also inject resume data into the targeted run. This is an IDOR-class authorization flaw (CWE-639) affecting default multi-tenant deployments prior to 4.6.0, with the greatest practical impact on shared instances where keys from one organization can reference another organization's runs. No public exploit identified at time of analysis.
Trigger.dev prior to 4.7.0 fails to enforce ownership checks on the parentRunId supplied to batch-creation endpoints, allowing authenticated holders of unrestricted environment API keys to suspend, indefinitely block, or inject errors into runs they do not own, including cross-organization or production runs on shared deployments. The flaw is rated CVSS 7.2 and is an IDOR-style missing authorization issue (CWE-639); no public exploit code or CISA KEV entry was identified at time of analysis. Risk is concentrated in multi-tenant or shared instances where foreign run IDs are reachable, and is materially lower in isolated single-tenant deployments.
Authorization bypass in OpenChoreo (1.0.0 through 1.0.5, 1.1.0 through 1.1.6, and 1.2.0 through 1.2.4) lets an authenticated user holding workflowrun:update on one project or component rewrite the ownership labels of a different WorkflowRun in the same namespace. Because the PUT .../workflowruns/{runName} handler derives its authorization hierarchy from the openchoreo.dev/project and openchoreo.dev/component labels in the request body while loading the target run from the URL path, an attacker who names a victim run in the path and submits labels for a scope they control is subsequently treated as authorized to read build logs and Kubernetes events, delete the run, modify pending spec.workflow.parameters, or drive the run into a permanent ComponentValidationFailed state. CVSS 3.1 scores this 7.4 with scope change (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L), but exposure is limited to deployments where multiple projects or components share a single namespace; it is not anonymously reachable and not cross-tenant, and no public exploit code was identified at time of analysis. Vendor-released patches exist in 1.0.6, 1.1.7, and 1.2.5.
Cross-session task access in the MCP TypeScript SDK (@modelcontextprotocol/sdk 1.24.0 through 1.31.0) allows any client sharing a single InMemoryTaskStore to list, read, and cancel other clients' experimental task records and results, an IDOR-style authorization bypass rated 8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L) with high confidentiality impact and low integrity/availability impact. The flaw is only reachable where an HTTP MCP server explicitly passes a shared taskStore to McpServer or Server and serves multiple sessions from it using the deprecated experimental tasks feature; stdio servers, stateless HTTP servers, and one-store-per-session deployments are not exposed, and 2.x packages are unaffected. There is no public exploit identified at time of analysis and no confirmed active exploitation; the vendor patched the SDK in 1.32.0 by binding each task to the session that created it.
Authenticated users on multi-user Stirling-PDF 3.0.0 through 3.2.0 can reach other tenants' stored documents by creating a processing folder whose path points into the server's storage directory at storage/<victimUserId>, then listing and running pipelines against that folder to read, alter, or delete the victim's files. The flaw is an authorization bypass through a user-controlled key (CWE-639) exposed by the proprietary processing-folder API (POST /api/v1/processing-folders) and the FolderAccessGuard check shipped in those releases. Publicly available exploit code exists, published alongside a technical write-up and a proof-of-concept repository, so the barrier to reproduction is low for anyone holding a valid account on an instance that hosts more than one user's files; EPSS scoring was not supplied in the available intelligence. The supplied CVSS 4.0 vector rates it 7.1 with PR:L, while our independent CVSS 3.1 assessment scores it 8.8 (C:H/I:H/A:H), and neither rating reflects anonymous exploitation - the practical exposure is a multi-tenant deployment risk rather than an internet-wide mass-exploitation event.
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.
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.
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.
An authorization bypass in Netmaker through 1.7.0 lets an authenticated user who holds external-client permissions on just one network reach into external clients belonging to other networks by sending PUT requests to /api/extclients/{network}/{clientid} - replacing public keys, disabling clients and retrieving WireGuard private keys. The CVSS 4.0 score of 8.7 reflects network reachability, low complexity, high confidentiality and integrity impact with only low privileges required (PR:L) and no user interaction, and the unscoped lookup is present in default deployments rather than needing special configuration. No public exploit code or confirmed active exploitation (CISA KEV) is identified in the available data, and the upstream fix is carried in PR #4153 / commit 332d8b9.
Cross-organization schedule deletion and disabling in Trigger.dev before 4.5.6 allows authenticated users with their own project schedule route to target another organization's IMPERATIVE cron schedule by supplying the victim schedule's friendlyId to delete or disable actions. The flaw is a CWE-639 authorization bypass/IDOR in DeleteTaskScheduleService and SetActiveOnTaskScheduleService, which resolve the friendlyId without scoping it to the caller's organization; exploitation requires authentication and knowledge or enumeration of the victim's friendlyId, and impact is limited to schedule integrity/availability with no data disclosure. No public exploit was identified at the time of analysis, and CISA KEV does not list this CVE.
Trigger.dev before 4.6.0 fails to enforce organization scoping in the waitpoint token wait endpoint, allowing an authenticated attacker who holds any valid secret API key to supply another organization's run ID and make that run block indefinitely on a waitpoint the victim cannot complete; the same path can also inject resume data into the targeted run. This is an IDOR-class authorization flaw (CWE-639) affecting default multi-tenant deployments prior to 4.6.0, with the greatest practical impact on shared instances where keys from one organization can reference another organization's runs. No public exploit identified at time of analysis.
Trigger.dev prior to 4.7.0 fails to enforce ownership checks on the parentRunId supplied to batch-creation endpoints, allowing authenticated holders of unrestricted environment API keys to suspend, indefinitely block, or inject errors into runs they do not own, including cross-organization or production runs on shared deployments. The flaw is rated CVSS 7.2 and is an IDOR-style missing authorization issue (CWE-639); no public exploit code or CISA KEV entry was identified at time of analysis. Risk is concentrated in multi-tenant or shared instances where foreign run IDs are reachable, and is materially lower in isolated single-tenant deployments.
Authorization bypass in OpenChoreo (1.0.0 through 1.0.5, 1.1.0 through 1.1.6, and 1.2.0 through 1.2.4) lets an authenticated user holding workflowrun:update on one project or component rewrite the ownership labels of a different WorkflowRun in the same namespace. Because the PUT .../workflowruns/{runName} handler derives its authorization hierarchy from the openchoreo.dev/project and openchoreo.dev/component labels in the request body while loading the target run from the URL path, an attacker who names a victim run in the path and submits labels for a scope they control is subsequently treated as authorized to read build logs and Kubernetes events, delete the run, modify pending spec.workflow.parameters, or drive the run into a permanent ComponentValidationFailed state. CVSS 3.1 scores this 7.4 with scope change (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L), but exposure is limited to deployments where multiple projects or components share a single namespace; it is not anonymously reachable and not cross-tenant, and no public exploit code was identified at time of analysis. Vendor-released patches exist in 1.0.6, 1.1.7, and 1.2.5.
Cross-session task access in the MCP TypeScript SDK (@modelcontextprotocol/sdk 1.24.0 through 1.31.0) allows any client sharing a single InMemoryTaskStore to list, read, and cancel other clients' experimental task records and results, an IDOR-style authorization bypass rated 8.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L) with high confidentiality impact and low integrity/availability impact. The flaw is only reachable where an HTTP MCP server explicitly passes a shared taskStore to McpServer or Server and serves multiple sessions from it using the deprecated experimental tasks feature; stdio servers, stateless HTTP servers, and one-store-per-session deployments are not exposed, and 2.x packages are unaffected. There is no public exploit identified at time of analysis and no confirmed active exploitation; the vendor patched the SDK in 1.32.0 by binding each task to the session that created it.
Authenticated users on multi-user Stirling-PDF 3.0.0 through 3.2.0 can reach other tenants' stored documents by creating a processing folder whose path points into the server's storage directory at storage/<victimUserId>, then listing and running pipelines against that folder to read, alter, or delete the victim's files. The flaw is an authorization bypass through a user-controlled key (CWE-639) exposed by the proprietary processing-folder API (POST /api/v1/processing-folders) and the FolderAccessGuard check shipped in those releases. Publicly available exploit code exists, published alongside a technical write-up and a proof-of-concept repository, so the barrier to reproduction is low for anyone holding a valid account on an instance that hosts more than one user's files; EPSS scoring was not supplied in the available intelligence. The supplied CVSS 4.0 vector rates it 7.1 with PR:L, while our independent CVSS 3.1 assessment scores it 8.8 (C:H/I:H/A:H), and neither rating reflects anonymous exploitation - the practical exposure is a multi-tenant deployment risk rather than an internet-wide mass-exploitation event.