Monthly
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.
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.
Unauthenticated HTTP requests to the /nodered endpoint of FUXA 1.3.2-2809 can bypass authorization and reach a code-execution path, giving a network attacker high impact to confidentiality, integrity, and availability (CVSS 9.8). The vulnerable component is FUXA's Node-RED integration endpoint; the supplied intelligence does not identify a CISA KEV designation or public exploit code at time of analysis, while the vuln.today priority decision is act_now. Internet-exposed or broadly reachable FUXA deployments that expose /nodered should therefore be treated as urgent exposure, whereas strictly segmented instances are less directly reachable.
Grafana OSS and Grafana Enterprise 13.2 installations that have explicitly enabled the experimental kubernetesSsoSettingsApi feature toggle let any authenticated user read SSO client secrets and modify instance-wide SSO configuration, because the SSO settings endpoints are missing an authorization check (CWE-285). Default deployments are not exposed, since the toggle ships disabled, and an attacker needs a valid Grafana account but not the SSO-settings permission that should normally be enforced. No public exploit code or confirmed active exploitation has been identified at time of analysis; the Grafana security advisory is the authoritative reference for fixed releases and any interim guidance.
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.
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.
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.
Improper authorization in Apache bRPC before 1.18.0 lets remote attackers reach builtin services such as brpc.vars and hotspots through the public port over protobuf-based protocols, disclosing runtime metrics, flags and profiler data that operators intended to expose only on the internal port. Only deployments that use ServerOptions.internal_port (or otherwise rely on it to gate builtin/Tabbed services), expose the public port to untrusted networks, and enable at least one protobuf-based protocol (baidu_std, hulu_pbrpc, sofa_pbrpc, public_pbrpc, nshead_mcpack, nova_pbrpc, ubrpc2pb) are affected; the HTTP/h2 dispatch path already enforced the restriction. The impact is confidentiality-only: the upstream score is 7.5 with C:H, while our assessment is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3), reflecting limited information disclosure rather than full compromise. No CISA KEV entry and no public exploit identified at time of analysis; EPSS is 0.18% (7th percentile), and the internal priority label is this_week.
Oracle Solaris 11.4's Image Packaging System (IPS) can be induced to act on attacker-influenced package content delivered over HTTP, giving a network-positioned, unauthenticated attacker high confidentiality impact and limited integrity impact (CVSS 3.1: 7.1 High, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N). The attacker must either control or compromise the repository the host queries, or intercept cleartext HTTP package traffic, and exploitation still requires a Solaris operator to perform a package operation against that content - the UI:R condition is the decisive exposure limiter. Only Solaris 11.4 is listed as affected per Oracle's October 2026 CPU and ENISA EUVD; no public exploit code was identified in the provided intelligence at time of analysis.
Unauthenticated remote write access in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an attacker manipulate the shared Redis backing store under any tenant's key, collapsing the platform's credential-encryption boundary and allowing cached flow parameters to be poisoned across tenants. The issue is rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) and requires the multi-tenant deployment pattern where tenants share the same Redis instance. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.
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.
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.
Unauthenticated HTTP requests to the /nodered endpoint of FUXA 1.3.2-2809 can bypass authorization and reach a code-execution path, giving a network attacker high impact to confidentiality, integrity, and availability (CVSS 9.8). The vulnerable component is FUXA's Node-RED integration endpoint; the supplied intelligence does not identify a CISA KEV designation or public exploit code at time of analysis, while the vuln.today priority decision is act_now. Internet-exposed or broadly reachable FUXA deployments that expose /nodered should therefore be treated as urgent exposure, whereas strictly segmented instances are less directly reachable.
Grafana OSS and Grafana Enterprise 13.2 installations that have explicitly enabled the experimental kubernetesSsoSettingsApi feature toggle let any authenticated user read SSO client secrets and modify instance-wide SSO configuration, because the SSO settings endpoints are missing an authorization check (CWE-285). Default deployments are not exposed, since the toggle ships disabled, and an attacker needs a valid Grafana account but not the SSO-settings permission that should normally be enforced. No public exploit code or confirmed active exploitation has been identified at time of analysis; the Grafana security advisory is the authoritative reference for fixed releases and any interim guidance.
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.
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.
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.
Improper authorization in Apache bRPC before 1.18.0 lets remote attackers reach builtin services such as brpc.vars and hotspots through the public port over protobuf-based protocols, disclosing runtime metrics, flags and profiler data that operators intended to expose only on the internal port. Only deployments that use ServerOptions.internal_port (or otherwise rely on it to gate builtin/Tabbed services), expose the public port to untrusted networks, and enable at least one protobuf-based protocol (baidu_std, hulu_pbrpc, sofa_pbrpc, public_pbrpc, nshead_mcpack, nova_pbrpc, ubrpc2pb) are affected; the HTTP/h2 dispatch path already enforced the restriction. The impact is confidentiality-only: the upstream score is 7.5 with C:H, while our assessment is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (5.3), reflecting limited information disclosure rather than full compromise. No CISA KEV entry and no public exploit identified at time of analysis; EPSS is 0.18% (7th percentile), and the internal priority label is this_week.
Oracle Solaris 11.4's Image Packaging System (IPS) can be induced to act on attacker-influenced package content delivered over HTTP, giving a network-positioned, unauthenticated attacker high confidentiality impact and limited integrity impact (CVSS 3.1: 7.1 High, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N). The attacker must either control or compromise the repository the host queries, or intercept cleartext HTTP package traffic, and exploitation still requires a Solaris operator to perform a package operation against that content - the UI:R condition is the decisive exposure limiter. Only Solaris 11.4 is listed as affected per Oracle's October 2026 CPU and ENISA EUVD; no public exploit code was identified in the provided intelligence at time of analysis.
Unauthenticated remote write access in IBM DataStage on Cloud Pak for Data 5.4.0.0 lets an attacker manipulate the shared Redis backing store under any tenant's key, collapsing the platform's credential-encryption boundary and allowing cached flow parameters to be poisoned across tenants. The issue is rated CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) and requires the multi-tenant deployment pattern where tenants share the same Redis instance. No public exploit was identified at time of analysis, and no CISA KEV entry was provided.