Monthly
Authenticated Subscriber-level users on WordPress sites running WP Booking System - Booking Calendar through 2.1.0.5 can delete calendar notes belonging to any calendar, because the wpbs_action_ajax_calendar_remove_note() AJAX handler performs no capability check before removing a note. The vendor-reported score is 9.1 and vuln.today assigns an act_now decision label, while our assessment scores the issue CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N: the discrepancy turns on authentication (the advisory vector uses PR:N, but an account is required per the description) and on whether note deletion constitutes an availability impact. No public exploit identified at time of analysis; exposure is concentrated on sites that permit open Subscriber-level registration, and the effect is confined to integrity loss of calendar notes with no confidentiality exposure or code execution.
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.
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.
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 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.
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.
Authenticated Subscriber-level users on WordPress sites running WP Booking System - Booking Calendar through 2.1.0.5 can delete calendar notes belonging to any calendar, because the wpbs_action_ajax_calendar_remove_note() AJAX handler performs no capability check before removing a note. The vendor-reported score is 9.1 and vuln.today assigns an act_now decision label, while our assessment scores the issue CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N: the discrepancy turns on authentication (the advisory vector uses PR:N, but an account is required per the description) and on whether note deletion constitutes an availability impact. No public exploit identified at time of analysis; exposure is concentrated on sites that permit open Subscriber-level registration, and the effect is confined to integrity loss of calendar notes with no confidentiality exposure or code execution.
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.
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.
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 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.
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.