Monthly
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.
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.
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).
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.
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.
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.
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 configuration overwrite in the Ortto plugin for WordPress (versions before 1.0.25) lets a remote attacker rewrite the plugin's stored settings and turn the site into a delivery point for arbitrary scripts. The configuration-update request is never authenticated; the only gate is a secret that is exposed in public page HTML, so no credentials, user interaction, or non-default configuration is required on any site running an affected version. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, but the vendor has released a fix in 1.0.25 and the issue was reported by Canva, the plugin's maintainer.
Unauthenticated remote attackers can drive AVideo-Encoder's privileged queue processor and read its control and status plane in default installations prior to 8.1.0. Because the application ships no global authentication layer (the bundled .htaccess denies only .git, *.log and avideo.log), the PHP endpoints view/run.php, view/queue.json.php, view/status.php and view/listFiles.json.php are directly reachable and perform their privileged actions for anonymous callers - invoking Encoder::run(), disclosing the job queue and every streamer site URL, returning host memory statistics with a wildcard Access-Control-Allow-Origin header, and enumerating media file names and paths in any directory readable by the web-server user. Impact is bounded to control-plane manipulation and information exposure (no code execution, and enumeration is limited to configured media extensions and does not return file contents); a public PoC reference with anonymous curl requests exists in the vendor advisory, but it is not verified as working exploit code and there is no KEV listing, with priority assessed as remediation this week and a vendor fix available in 8.1.0.
Unauthenticated remote attackers can pull a ZIP of the Signal K Server log/config directory from the /skServer/ziplogs route in every signalk-server release before 2.33.0, and that archive contains security.json with the server's HS256 JWT signing key. Possession of the secretKey lets an attacker forge administrator tokens or create a persistent admin account and then authenticate through the normal login flow, yielding full control over NMEA routing, plugin configuration and alarms on affected installations, including vessel deployments. The endpoint was confirmed reachable without credentials on a live signalk-server 2.32.0 instance and roughly 66 potentially affected servers were visible to Shodan at disclosure; no public exploit identified at time of analysis, and the vendor addressed the issue in 2.33.0 by placing the route behind admin middleware.
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.
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.
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).
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.
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.
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.
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 configuration overwrite in the Ortto plugin for WordPress (versions before 1.0.25) lets a remote attacker rewrite the plugin's stored settings and turn the site into a delivery point for arbitrary scripts. The configuration-update request is never authenticated; the only gate is a secret that is exposed in public page HTML, so no credentials, user interaction, or non-default configuration is required on any site running an affected version. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, but the vendor has released a fix in 1.0.25 and the issue was reported by Canva, the plugin's maintainer.
Unauthenticated remote attackers can drive AVideo-Encoder's privileged queue processor and read its control and status plane in default installations prior to 8.1.0. Because the application ships no global authentication layer (the bundled .htaccess denies only .git, *.log and avideo.log), the PHP endpoints view/run.php, view/queue.json.php, view/status.php and view/listFiles.json.php are directly reachable and perform their privileged actions for anonymous callers - invoking Encoder::run(), disclosing the job queue and every streamer site URL, returning host memory statistics with a wildcard Access-Control-Allow-Origin header, and enumerating media file names and paths in any directory readable by the web-server user. Impact is bounded to control-plane manipulation and information exposure (no code execution, and enumeration is limited to configured media extensions and does not return file contents); a public PoC reference with anonymous curl requests exists in the vendor advisory, but it is not verified as working exploit code and there is no KEV listing, with priority assessed as remediation this week and a vendor fix available in 8.1.0.
Unauthenticated remote attackers can pull a ZIP of the Signal K Server log/config directory from the /skServer/ziplogs route in every signalk-server release before 2.33.0, and that archive contains security.json with the server's HS256 JWT signing key. Possession of the secretKey lets an attacker forge administrator tokens or create a persistent admin account and then authenticate through the normal login flow, yielding full control over NMEA routing, plugin configuration and alarms on affected installations, including vessel deployments. The endpoint was confirmed reachable without credentials on a live signalk-server 2.32.0 instance and roughly 66 potentially affected servers were visible to Shodan at disclosure; no public exploit identified at time of analysis, and the vendor addressed the issue in 2.33.0 by placing the route behind admin middleware.