Credential exfiltration in Heym before version 0.0.106 allows an authenticated collaborator who has been granted shared access to a credential to cause the server to transmit the credential owner's decrypted secret to an attacker-controlled endpoint. The flaw lives in the POST /api/credentials/test endpoint, where the destination URL supplied in the config parameter is not validated, so a low-privileged collaborator can redirect a credential-verification request (CWE-918 server-side request forgery) and harvest plaintext secrets they were never entitled to read. The vendor CVSS 4.0 assessment (7.1, AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N) confirms high confidentiality impact with no integrity or availability effect, and no public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis; risk is concentrated in multi-user, self-hosted deployments that rely on collaborator sharing, while single-user instances are not meaningfully exposed.
Server-side request forgery in AzuraCast before 0.23.8 allows an authenticated user with the station-scoped WebHooks permission to make the server send outbound HTTP POST requests to internal, loopback, or RFC1918 addresses through the Generic and Discord webhook connectors. The AbstractConnector::getValidUrl() validation only rejects literal link-local IPs and skips validation entirely when the hostname is not a literal IP, and the same user can trigger the request on demand via the webhook test endpoint. No public exploit identified at time of analysis; risk is moderate because exploitation requires a low-privileged account and impact is largely a blind Now Playing POST unless the target internal service is reachable and responsive.
Missing authorization on AzuraCast's GET /api/station/{station_id}/file/{id}/play endpoint lets any authenticated user - including one whose API key or session is scoped to a single station - download the complete media library of every other station on a multi-tenant installation running 0.23.5 or earlier. Because the endpoint accepts sequential auto-increment media IDs, an attacker can trivially enumerate and exfiltrate files from stations they have no permissions on, with no user interaction and impact limited to confidentiality (vendor CVSS 4.0 base 7.1; assessed as CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). The vendor advisory (GHSA-qff7-q5fm-8p76) ships step-by-step proof-of-concept reproduction instructions; there is no indication of confirmed active exploitation (CISA KEV) at time of analysis.
Credential exfiltration and server-side request forgery in utcp-http 1.1.3 and earlier allow an attacker who supplies a malicious OpenAPI specification to redirect a victim's OAuth2 client_id and client_secret to an arbitrary token endpoint. The library validates discovery and tool-invocation URLs via ensure_secure_url() but never applies the same guard to the OAuth2 tokenUrl taken from a remote spec, so the attacker-chosen endpoint receives the credentials in cleartext when a generated OAuth2-protected tool is invoked. Exploitation requires victim interaction (the victim must register the attacker-controlled spec and call the generated tool) and no attacker authentication; the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N (7.1), with the unvalidated endpoint also usable for SSRF against internal HTTP ranges. No public exploit identified at time of analysis.
Server-side request forgery in AzuraCast (Composer package azuracast/azuracast, versions before 0.23.8 per the advisory) lets an authenticated user who holds the station-scoped RemoteRelays permission set a station's Remote Relay URL to loopback, private-network, or cloud-metadata addresses such as http://127.0.0.1:<port>/ or http://169.254.169.254/latest/meta-data/. Because the URL is validated only for syntax and an http/https scheme, the platform's periodic background Now Playing sync (AbstractRemote::getNowPlayingAsync) then automatically and repeatedly fetches that attacker-chosen address on the server's behalf, yielding blind SSRF against internal services and - on cloud-hosted instances with a reachable metadata endpoint - potentially exposing instance credentials or configuration. This is not an unauthenticated internet-facing flaw: exploitation requires an authenticated account with the RemoteRelays permission (PR:L in both the vendor's CVSS 4.0 vector and our CVSS 3.1 assessment), there is no public exploit code identified at time of analysis, and no patched release was confirmed at the time of the advisory.
Server-side request forgery in python-utcp (utcp-http) before 1.1.12 allows an unauthenticated remote attacker to cause a victim's client to issue requests to loopback services and return response bodies if the victim registers a malicious UTCP manual served from a non-loopback origin. Exploitation requires user interaction (registering the manual) and is limited to loopback interfaces, with further prerequisites of a loopback service that answers unauthenticated requests with useful data. No public exploit code exists, and the issue is fixed in utcp-http 1.1.12; this is a conditional-severity issue rather than a mass-exploitation threat.
Coordinator impersonation in Edgeless Systems Contrast (a confidential-computing runtime for Kubernetes) before version 1.4.1 lets an attacker who can redirect traffic to a rogue Coordinator recover arbitrary secrets of workloads deployed after the attack. The recovering Coordinator fails to verify the seed supplied by the recovering party, so a rogue Coordinator whose manifest passes validation but whose secret seed is attacker-controlled can issue certificates chaining to its own root CA, impersonating a workload owner when the `contrast` CLI `set` call does not compare the returned root CA certificate against the existing one (the CLI's default behavior) or when `verify` is run without comparing against a trusted reference. Exploitation is unauthenticated but conditional - it requires a network-position/man-in-the-middle prerequisite plus a victim workload-owner action - so this is a genuine but conditional integrity and confidentiality flaw rather than a widespread emergency; no public exploit is identified at time of analysis and the issue is not in CISA KEV.
Authenticated privilege escalation in Nezha Dashboard before 2.3.5 lets any account holding the nezha:service:write scope escalate into privileged Agent operations by creating or updating a service monitor whose Task.Type is set to a command or configuration task value, since the service API never validated that the submitted type belonged to the supported probe set. Because service monitors and privileged operations share the same protobuf Task.Type integer namespace, the crafted task is accepted and dispatched to Agents within the attacker's existing authorization scope, resulting in command execution or Agent reconfiguration (CWE-269). The independent assessment rates this as a genuine but authentication-gated privilege-escalation issue whose urgency is moderate and whose blast radius scales with how broadly service:write is delegated; the vendor has released a fix in 2.3.5 (commit 38824dbc11a63964c5b9296ae4c68e62b34fa04b) and no public exploit has been identified at time of analysis.
Denial of service in the Nezha monitoring dashboard before 2.3.8 lets any authenticated non-administrator account crash the dashboard process by submitting a malformed alert rule (invalid rule type or out-of-bounds duration) to POST /api/v1/alert-rule, which triggers an unrecovered panic in the alert evaluator goroutine. Because the offending rule is persisted, the dashboard enters a crash loop on every restart, taking down monitoring and the control plane until the bad record is manually removed from the backing datastore. No public exploit code was identified at time of analysis, exploitation requires only a low-privileged account (CVSS PR:L) and network reachability to the dashboard API, and impact is confined to availability with no confidentiality or integrity loss.
Authenticated directory deletion in the Event Gallery extension for Joomla (svenbluege.de) below version 6.5.0 allows a high-privileged Joomla backend user to supply a traversal payload in the `images` parameter of the `cache.process` clear-cache task and recursively delete any directory the web server account is permitted to write to. The impact is confined to integrity and availability of web-server-writable paths - there is no confidentiality loss (VC:N/SC:N) and no privilege gain beyond the actor's existing administrator-level access, which is the main limiting factor (PR:H), giving a CVSS 4.0 base score of 7.0. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the root cause is a CWE-22 path traversal that accepts unsanitised relative paths before file deletion.