Cross-site scripting in the patient registration workflow of subhajitkhan's Online Clinic Management System (patientregistration.php, pat_name parameter) lets an authenticated user inject markup or script that executes in another user's browser when the affected page is rendered, yielding low integrity impact with no confidentiality or availability loss per the assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N vector. The project does not use versioning, so all snapshots through commit e9ee77a8827a1446220fa07ee693dc4d9a29a578 are treated as affected and no fixed release has been published; the maintainer was notified through GitHub issue #12 and has not responded. Risk is low in practice (EPSS 0.25%, 17th percentile, priority label 'monitor', no CISA KEV listing and no confirmed active exploitation), and the publicly referenced proof-of-concept is an issue-tracker reference rather than verified working exploit code.
Stored cross-site scripting in FFXIV Teamcraft up to and including 11.4.31 lets comment content be rendered as trusted HTML in the desktop/Electron renderer, so an attacker who can post comments can execute script in the context of another user who later views them. Exploitation requires a low-privileged authenticated account to plant the payload and a victim to open the affected comment view, which keeps realistic impact at medium severity (CVSS 4.0 base 5.1, CWE-79); the network vector alone overstates the practical risk. No public working exploit code is confirmed - only a public proof-of-concept reference exists - and the issue is not listed as actively exploited; upgrading to 11.4.32 is the recommended fix and the vendor patch commit is public.
Cross-site scripting in Bdtask Garage 24 Garage Management Software 1.0 lets an authenticated user inject script through the first_name or last_name fields handled by /edit_profile, executing in a victim's browser when the affected profile view is loaded. Exploitation requires an authenticated account (PR:L) and user interaction (UI:P); a public PoC reference exists but is not verified as working exploit code, and no CISA KEV entry or vendor-released patch was identified. This is a low-to-moderate priority issue that does not warrant emergency handling.
Credential leakage in Erlang hackney before 4.9.0 can expose HTTP basic_auth and cookie values when an application enables follow_redirect and a server returns a same-host redirect that changes scheme or port. The redirect handling compared only the hostname, so an https-to-http downgrade resent Authorization and Cookie headers in cleartext for an on-path attacker, while a same-host port change handed them to another service. The independent assessment rates this as medium severity (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N); no public exploit was identified at time of analysis.
An out-of-bounds read in libimobiledevice's AFC file handler can disclose a small amount of adjacent memory to a hostile or spoofed AFC peer. Applications linked against libimobiledevice 1.0 through 1.4.0 that call afc_file_open() are affected; the CVSS:4.0 vector rates confidentiality impact as low with no integrity or availability effect, and requires low privileges plus passive user interaction. A public write-up reference exists but is not verified as working exploit code, no CISA KEV entry or other active-exploitation signal is present, and priority is assessed as moderate and non-urgent.
Memory-exhaustion denial of service in Autobahn Python 26.7.1 through 26.10.0 (pip package `autobahn`) lets a remote, unauthenticated WebSocket client exhaust server memory by sending one tiny, highly compressed permessage-brotli frame; the decompressor inflates the whole frame before the configured maxMessagePayloadSize is enforced, so a 421-byte frame drove peak RSS to roughly 545 MiB under a 1 MiB message limit in the reporter's own measurement. Only servers that deliberately opt into the permessage-brotli extension (via the `compress` extra) are exposed - permessage-deflate, -bzip2 and -snappy already honor the output budget and are explicitly out of scope - and the impact is availability only, with no confidentiality or integrity exposure. Fixed in 26.10.1; a working proof-of-concept ships with the upstream advisory, no active exploitation is reported (EPSS 0.43%, 37th percentile), and the vuln.today priority is 'this_month' given the opt-in prerequisite.
Unchecked range validation in snappy-java (org.xerial.snappy:snappy-java) prior to 1.1.10.9 lets caller-supplied offsets and lengths reach a native memcpy, so negative or oversized byteLength/offset values can read or write outside Java array bounds and crash the JVM. Unauthenticated remote attackers can only reach the flaw if the embedding application forwards attacker-influenced ranges into Snappy.arrayCopy, SnappyInputStream.rawRead/read, or SnappyOutputStream.rawWrite/write (including typed-array variants), which is why the assessed vector is AV:N/AC:H with availability-only impact. There is no CISA KEV listing and no public exploit identified at time of analysis; EPSS is low at 0.41% (35th percentile) and the vendor has released 1.1.10.9 as the complete fix.
Stored cross-site scripting in Argilla's annotation text field component (argilla-frontend/components/features/annotation/container/fields/text-field/TextField.vue) allows a user who can write annotation text to persist markup that executes in another user's browser session when the poisoned record is viewed. The assessed vector requires an authenticated principal with privileges to submit or edit annotation text plus interaction from a second viewer, with impact limited to low integrity and no confidentiality or availability loss; all Argilla branches from 2.0 through 2.8.0 are listed as affected. A public proof-of-concept reference exists but is not verified as working exploit code, EPSS is 0.21% (11th percentile), and the vulnerability is not in CISA KEV - priority guidance is to monitor rather than act urgently.
Stored cross-site scripting in Argilla 2.0 through 2.8.0 allows a privileged, authenticated user to inject a crafted value into the 'template' argument of a custom annotation field, which is rendered by argilla-frontend/components/features/annotation/container/fields/sandbox/Sandbox.vue and executes in the browser of a second user who later views that field. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N) confines the outcome to limited integrity impact in the victim's browser session, with no confidentiality or availability impact, and the high-privilege prerequisite plus the need for a victim to open the crafted annotation are the main limiting factors. This is a low-priority, low-risk issue: EPSS is 0.21% (11th percentile), there is no CISA KEV entry, the priority decision is 'monitor', and a public PoC reference exists but is not verified as working exploit code. No vendor fix has been identified; the project was notified via issue #5876 and has not responded.
Recovery of a long-term X25519 private key is possible in erlang-jose 1.10.0 through 1.11.12 whenever the pure-Erlang Curve25519 fallback is the code path actually in use, because scalar multiplication there runs in secret-dependent time and lets an attacker who can submit ECDH-ES JWE ciphertexts and measure decryption timing reconstruct the private scalar bit by bit. The assessed impact is confidentiality-only (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/C:H/I:N/A:N) and depends on a service that reuses a fixed X25519 key being reachable by an attacker able to collect large numbers of low-noise timing samples, so this is a conditional cryptographic weakness rather than an opportunistic mass-exploitation issue. A public PoC reference exists in the vendor advisory - a demonstration script that forces crypto_fallback and shows a stable timing delta between two victims differing only in their private scalar - but it is not verified as working key-recovery exploit code; there is no CISA KEV listing and EPSS is 0.14% (3rd percentile).
The Erlang/Elixir JOSE library (potatosalad/erlang-jose) can be driven into an unbounded tail-recursive loop through JOSE.JWK.shared_secret/2 when an application derives an ECDH shared secret from an attacker-supplied peer JWK whose key type differs from the application's own key. A single mismatched JWK (for example an RSA public key submitted to a server holding an EC P-256 key) never returns and never crashes, pinning one BEAM scheduler at 100% CPU; repeated submissions exhaust schedulers and degrade or take down the service. Only deployments on jose 1.5.0 through 1.11.12 that actually call shared_secret/2 on untrusted input are reachable - applications using jose purely for JWS/JWE/JWT signing and verification do not hit the vulnerable clause. Severity is a genuine but modest-priority availability issue: EPSS is 0.14% (3rd percentile), there is no CISA KEV listing, priority is 'this_month', but a public proof-of-concept script published with the vendor advisory demonstrates the scheduler hang. Fixed in 1.11.13.
Authentication-tag forgery in the Erlang JOSE library (jose 1.2.0 through 1.11.12) lets an unauthenticated remote attacker defeat AES-GCM integrity wherever decryption routes through the pure-Erlang jose_jwa_aes fallback - FIPS builds, or stripped or older OTP releases where :crypto does not expose a native AES-GCM NIF. Because verification compares only as many bits of the real 128-bit tag as the attacker-supplied tag contains, truncating the tag to a single byte drops forgery resistance to 2^-8, so a forged JWE with attacker-chosen ciphertext is accepted within 256 attempts without knowledge of the key; an over-length tag instead triggers a badmatch that crashes the decrypting process. A public PoC reference exists (advisory-attached Elixir script); it is not verified as working exploit code, there is no confirmed active exploitation (not in CISA KEV), and EPSS is 0.11% (2nd percentile), consistent with the conditional fallback prerequisite.
Bleichenbacher padding-oracle weakness in erlang-jose's pure-Erlang RSAES-PKCS1-v1_5 decryption (jose 1.3.0 through before 1.11.13) can let an unauthenticated attacker who knows only the public RSA key recover plaintext from intercepted RSA1_5 JWE content-encryption keys via roughly 10^4 to 10^6 adaptive chosen-ciphertext queries. Exploitation requires an application that unwraps RSA1_5 JWE keys with jose and exposes the decryption outcome, either as distinguishable return values (recovered key versus error) or as observable timing; the direct return-value oracle applies when the pure-Erlang jose_jwa_pkcs1 backend is active. No CISA KEV entry or confirmed active exploitation was identified, EPSS is 0.09%, and a public PoC reference exists but it is not verified as working exploit code.
Easy Digital Downloads, the WordPress e-commerce plugin from Awesome Motive, mishandles synchronization of a shared resource in versions through 3.7.1, creating a race condition (CWE-362) that a remote attacker can use to corrupt data the plugin is expected to keep consistent. The assessed vector (CVSS 5.9, AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N) means no authentication or user interaction is needed, but the attacker must repeatedly hit a non-deterministic concurrency window, so exploitation is timing-dependent rather than reliable on a single request; impact is limited to integrity, with no confidentiality or availability effect. No public exploit code or active exploitation is identified in the available data at time of analysis, and the exact vulnerable operation and endpoint are not described in the sources.
Missing authentication on the local HTTP service in 777genius agent-teams-ai through 2.17.10 allows a locally positioned attacker with existing low privileges to access service endpoints without credentials, yielding low-impact confidentiality disclosure. The service is started by doStart in HttpServer.ts and is reachable only with local access; remote exploitation is not possible per the assessed vector, and integrity and availability impacts are absent. A public PoC reference exists but is not verified as working exploit code, and no vendor patch or response is identified; priority is monitor.
Cross-site scripting in the Virtual Server page of the Edimax BR-6208AC web management interface (firmware 1.32) lets an attacker who already holds an authenticated administrator session inject script that executes when a victim subsequently loads the manipulated page. Impact is confined to low integrity in the victim's browser, with no confidentiality or availability effect, and the CVSS 4.0 base score is 1.9 (independent assessment: CVSS 3.1 AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N). The vendor was contacted and did not respond, no vendor-released fix is identified, and a public PoC reference exists; it is not verified as working exploit code, and priority signals rate this as monitor-level.
Stored cross-site scripting in gougucms affects releases up to and including 4.08.18, specifically the Add function in app/admin/controller/Level.php where the Title argument of a User Level record is not sanitized before being stored and later rendered. Exploitation requires authenticated access at administrator privilege level (PR:H) to the back-office panel, plus a second user viewing the affected admin page for the script to run (UI:P), so this is not anonymously reachable despite the network vector; impact is confined to the admin interface. A public PoC reference exists (GitHub write-up linked from the VulDB entry); it is not verified as working exploit code, there is no CISA KEV listing, and the vendor did not respond to the disclosure, so no fixed release is identified.
Stored and reflected cross-site scripting in OPNsense Firewall 26.7.1_1 and earlier lets an authenticated low-privileged GUI user execute JavaScript in another user's browser, including a root user's session, when the victim views the Dashboard, Interfaces → Overview, or submits a crafted Firewall → Log Files → Live View search. The stored variant requires write access to the Interfaces → Assignments Description field, while the reflected variant requires the victim to interact with the Live View search; both require valid GUI credentials and victim interaction. The issue is rated CVSS 5.6, no KEV status was provided, and a public PoC reference exists but is not verified as working exploit code.
Path traversal (CWE-22) in halo-dev Halo CMS through 2.27.0-beta.1 lets unauthenticated remote attackers manipulate the 'template' argument handled by DefaultViewNameResolver.resolveViewNameOrDefault, allowing traversal outside the intended theme view-name lookup and limited exposure or manipulation of files reachable by the Halo process; the reporter rates confidentiality, integrity and availability impact as Low, consistent with constrained file access rather than arbitrary full-path read or code execution. The CVSS 4.0 score is 6.9 with AV:N/AC:L/AT:N/PR:N/UI:N, and the vector carries E:P, so a public PoC reference exists; it is not verified as working exploit code, and there is no CISA KEV listing indicating active exploitation. The vendor was contacted about the disclosure and did not respond, and no vendor-released patch was identified at time of analysis, so exposure should be treated as ongoing for deployments on affected builds.
Information disclosure in Lobster_pro affects version 4.12.12-LTS and potentially other releases prior to 25.1.3, where improper permission checks let an authenticated low-privilege user on an adjacent network reach HTTP endpoints reserved for administrators. The assessed impact is confidentiality-only, with high disclosure of both the vulnerable component and dependent systems but no integrity or availability effect; the CVSS 4.0 base score is 5.6, and no public exploit was identified at time of analysis. It is a medium-severity, moderate-priority issue (this_month) rather than an emergency.
gssproxy can be persistently crashed by any local user who can reach its Unix domain socket: a GSSX_INIT_SEC_CONTEXT request that omits the target_name field triggers a NULL pointer dereference in the daemon. The issue affects gssproxy deployments on Red Hat Enterprise Linux 7, 8, 9, and 10 and is listed for Red Hat OpenShift Container Platform 4; because gssproxy does not automatically restart, Kerberized NFS and IdM services that depend on it can be disrupted until an administrator intervenes. No public exploit identified at time of analysis.
OS command injection in QuantGeekDev docker-mcp 0.1.0 and 0.2.0 allows an attacker who can influence the project_name argument to inject arbitrary shell commands through the Windows-specific command builder in docker_executor.py. The vulnerable path is exercised only on Windows deployments, and the CVSS UI:P component means a user or agent must invoke the affected MCP tool before the payload is assembled, so it does not fire passively. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; the vendor's CVSS 4.0 base score is 5.3, while our independent assessment rates it higher (7.5-equivalent impact under CVSS 3.1) because successful injection yields full command execution.
UI spoofing in Firefox for iOS before version 156.1 lets a malicious page open a 'tel:' link inside a window that is still displaying a different website, so the phone-call confirmation prompt appears to come from that trusted site. The attacker must first lure the victim into loading the malicious page and then persuade them to approve the dial prompt, so no silent action or code execution occurs; the assessed impact is integrity-only with no confidentiality or availability loss. Mozilla fixed the issue in Firefox for iOS 156.1 (MFSA2026-117); no public exploit code is identified and EPSS is low at 0.21%, with CISA SSVC rating exploitation as none.
Firefox for iOS versions before 156.1 could be made to display attacker-supplied text inside the system FaceTime call prompt, creating a UI-spoofing (CWE-451) vector for phishing messages presented as trusted Apple system UI. Only users browsing with Firefox for iOS rather than Safari and visiting a malicious page are affected, and the deception still depends on the user acting on the spoofed prompt; there is no code execution or data theft, and updating to Firefox for iOS 156.1 removes the issue. No public exploit code and no active exploitation are indicated (EPSS roughly 0.21%, SSVC exploitation: none), so this warrants routine patching rather than emergency response.
LearnPress through 4.4.11 contains a missing-authorization flaw (CWE-862, CVSS 5.4) that lets an authenticated low-privilege user perform actions outside their intended role, with limited confidentiality and integrity impact and no availability impact. The priority signal is this_month, no public exploit identified at time of analysis, and no CISA KEV entry is present, so this is a moderate rather than urgent issue; a valid account is required, although open LMS self-registration can make obtaining one easier.
SQL injection in Apache SIS's sql-storage module (versions 1.0 through 1.6) allows remote attackers to inject SQL through a crafted sort clause that is copied after ORDER BY without identifier quoting. Exploitation requires an application built on Apache SIS to use the sql-storage module and to derive the ORDER BY sort-clause identifier from attacker-controllable input; reachability is the key limiting factor. Other modules such as sis-referencing are not affected, and no public exploit identified at time of analysis.
Open redirect in Mautic's public form submission endpoint (/form/submit) causes the application to send a visitor to a return address supplied with the submission without confirming that it resolves to the Mautic instance or another trusted host, so a crafted form can bounce visitors from a legitimate Mautic domain to an attacker-chosen external site such as a phishing clone or a malware delivery page. Every Mautic release below 5.2.12, 6.0.10 and 7.2.2 is affected, and any instance with a published public form is exposed; the attacker needs no authentication (PR:N) but the victim must actually submit the attacker-prepared form (UI:R), which keeps this a moderate-priority, social-engineering-dependent issue rather than an emergency. No public exploit code was identified at time of analysis, and the vendor rates the impact as limited confidentiality and integrity only (CVSS 5.4).
Missing authorization in the Geo Mashup WordPress plugin through 1.13.22 lets a low-privileged authenticated user reach functionality that should be restricted, allowing limited reads and modifications of protected data (CVSS 5.4, AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). Any WordPress site running the plugin at or below 1.13.22 with self-registration or otherwise obtainable subscriber-level accounts is exposed; the assessed vector requires PR:L, so a valid low-privileged account is a prerequisite. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and the reported severity is capped at low confidentiality and integrity impact with no availability effect.
Tornado's HTTP/1.x header parser consumes quadratic CPU time when a header value is spread across many obsolete line-folding (obs-fold) continuation lines, allowing a client to stall the single IOLoop thread and delay every other connection that process serves. All Tornado HTTP servers running versions prior to 6.6 are affected, because header parsing happens before any application code, so no route, handler, or credentials are needed; only availability is impacted (C:N/I:N/A:L). At the default 64 KB max_header_size a single malicious request blocks the loop for tens of milliseconds, so meaningful degradation requires repeated requests, and the impact scales with the square of the configured header limit; EPSS is low (0.38%, 32nd percentile) and no public exploit has been identified at time of analysis, though the vendor has released a fix in 6.6.
Event-loop starvation in the Tornado Python web framework and async networking library before 6.6.0 allows a remote, unauthenticated attacker to stall every connection handled by a worker process by submitting an HTTP/1.1 chunked request body made of millions of one-byte chunks to any handler that reads the body. Because the decoder processes already-arrived body bytes without yielding to the event loop, a body near the default 100 MB max_body_size can block the process for close to a minute, and for handlers without @stream_request_body each retained chunk costs roughly twenty times the received bytes in memory. The same behaviour affects SimpleAsyncHTTPClient when it reads a response from a malicious server; no public exploit identified at time of analysis, and the issue is addressed in the 6.6.0 release rather than treated as an emergency by available triage signals.
Information exposure through error messages in a2aproject a2a-java up to 1.2.0.Final lets an attacker who can induce a server-side exception read raw internal exception text from the returned JSON-RPC or REST error payload. Affected deployments are those running the reference Quarkus JSON-RPC/REST routes or the gRPC transport, where the error handler built InternalError directly from the thrown exception's message; per the vendor vector the attacker holds low-level privileges (PR:L), although the real authentication bar depends on how the A2A server is exposed. Impact is limited to low confidentiality with no integrity or availability effect, there is no CISA KEV listing and no public exploit identified at time of analysis, and EPSS is 0.32% (24th percentile), consistent with a low-priority disclosure issue that is resolved by upgrading to 1.3.0.Final.
Information exposure through error messages in the .NET A2A SDK (a2aproject a2a-dotnet) up to and including 1.0.0-preview2 causes the JSON-RPC endpoint to echo raw System.Text.Json parser output back to the caller. When a request body fails parsing, A2AJsonRpcProcessor.ProcessRequestAsync returns the -32700 ParseError response containing ex.Message, which discloses JSON paths, line and byte positions, exception type names and library details rather than a generic error. The exposure is diagnostic metadata only - no credentials or user data are implicated, and the independently assessed impact is low (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N); no public exploit has been identified at time of analysis, and upgrading to 1.0.0-preview3 resolves the issue.
Code injection in the Seroval JavaScript serialization library 1.6.0 through 1.6.10 lets attacker-controlled text become executable JavaScript in the serializer's output when an application copies an untrusted own `constructor` property onto a typed array and then passes that array to serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, the Serializer class, or compileJSON. The vendor rates the result low severity because that property-copying pattern is described as unusual, and the injected script only executes once a victim loads a page that receives the serialized output (CVSS 4.0 AV:N/AC:H/AT:P/PR:N/UI:P with scope change to confidentiality and integrity). There is no confirmed active exploitation (not in CISA KEV; SSVC exploitation: none) and no public exploit identified at time of analysis, with EPSS at 0.27% (19th percentile), and the flaw is fixed in Seroval 1.6.11.
Parse Server's $relatedTo relation query does not validate the owning object reference, so an authenticated client can substitute a query operator for the object ID and slip past the owning-object ACL check introduced for GHSA-wmwx-jr2p-4j4r. The result is a limited information disclosure: the attacker learns which objects they can already read are linked to owning objects they are not permitted to read, in deployments that expose Relation fields to queries. Severity is moderate (CVSS 5.3, PR:L, confidentiality-only), EPSS is low at 0.25% (17th percentile), there is no CISA KEV listing, and no public exploit has been identified at time of analysis.
Information disclosure in the VMime C++ MIME library through 0.9.2: the uuEncoder::decode routine trusts the line-length byte of a uuencode/x-uuencode part, so a crafted part with an over-long length byte causes uninitialized stack memory to be written into the decoded output - up to 15 bytes of stack contents per over-long line. Affected are applications that use VMime (kisli:vmime, all versions up to and including 0.9.2) to parse attacker-supplied MIME messages; no authentication is required, but the victim must have the crafted message decoded by the application (UI:P in the CVSS 4.0 vector, UI:R in the assessed 3.1 vector), and the leaked bytes are only useful if they are observable in the resulting decoded attachment. There is no CISA KEV entry and EPSS is low (0.25%, 17th percentile), no public exploit code has been confirmed at time of analysis, and the vendor has published a fix upstream (PR #363, commit e85925ed); this is a genuine but low-to-moderate priority flaw rather than an emergency.
Missing authorization in OpenPanel's onboarding.project tRPC mutation lets any authenticated organization member - including a read-only one - create unlimited projects and mint plaintext write-type ingestion credentials inside that organization, bypassing the admin-only policy that the sibling procedures project.create and client.create enforce. All releases before 3.0.0 are affected (2.3.0 confirmed vulnerable), and the minted write-type secret cannot read existing data or manage resources, so impact is bounded to injecting fake analytics events, poisoning business metrics and consuming the organization's usage budget. EPSS is low (0.24%, 15th percentile), there is no CISA KEV entry, and the upstream GHSA advisory publishes a working PoC request (a single tRPC call over the dashboard httpLink with a non-admin member session cookie).
Improper escaping in OpenPanel's sankey.service.ts lets any authenticated member of a project - read access alone is sufficient - supply an events[].name value containing a backslash to the chart.sankey procedure and break out of the ClickHouse string literal, producing a parse error that takes the project's Sankey chart endpoint offline. The flaw affects OpenPanel releases before 3.0.0 and is a self-contained availability issue: only the one chart feature the attacker can already read is disrupted, with no confidentiality or integrity impact and no cross-tenant reach. The reporter could break the literal but not convert it into a working injection, so the practical effect is denial of a single feature; EPSS is only 0.23% (14th percentile), the issue is not in CISA KEV, and no confirmed exploitation has been reported. Authentication requirements are confirmed as low-privileged (PR:L in the CVSS vector). Vendor-released patch: 3.0.0.
Read-level project members in OpenPanel before 3.0.0 can retrieve the argon2id hashes of every ingestion credential in a project by calling the client.list tRPC query, which returns full Prisma Client rows because the findMany call carries neither a select nor an omit clause. The vendor advisory includes a PoC reference request showing the expected response shape; it is not verified as working exploit code, there is no CISA KEV entry, and EPSS is 0.22% (12th percentile). Realistic risk is limited: the underlying secrets are roughly 80-bit random values and the stored hashes use argon2id (m=19456, t=2, p=1), so the leak chiefly enables offline confirmation of secrets obtained elsewhere without using the credential against the live API and without leaving an audit trail.
Race condition in a2a-dotnet through 1.0.0-preview3 allows a low-privilege authenticated remote client to disturb task status and background-cancellation bookkeeping by submitting concurrent SendMessage or SendStreamingMessage requests for the same TaskId, producing limited integrity and availability impact. The trigger is a CWE-362 race in TaskProjection.ApplyStatus and the A2AServer cancellation-registration path, which the proposed fix in PR #453 replaces with lock-guarded reservation and release. Severity is moderate (CVSS 5.3), no public exploit code has been identified at time of analysis, and the fix has not yet been accepted or released.
Stored cross-site scripting in YesWiki before 4.7.0 lets unauthenticated remote attackers persist JavaScript into the wiki's referrer log by sending a single request whose Referer header carries HTML metacharacters; the payload executes for any user who subsequently opens the '?PageName/referrers_sites' handler view, giving the attacker same-origin fetch/XHR capability in that visitor's session. Because session cookies are HttpOnly and the payload stays dormant until the handler page is viewed, impact is constrained to content exfiltration and actions taken as the victim rather than direct cookie theft; EPSS is low at 0.18% (7th percentile), there is no KEV entry, and the upstream GitHub advisory includes a curl-based PoC reproduction. The vendor-released fix is YesWiki 4.7.0, and per the vuln.today decision this is a this-month priority rather than an emergency.
Reflected cross-site scripting in YesWiki before 4.7.0 lets unauthenticated remote attackers run JavaScript in a victim’s browser when the victim opens a crafted link targeting a Bazar entry that lacks a stored field key. The attacker supplies the missing field name as a query parameter, and BazarField::getValue() falls back to unsanitized $_REQUEST data rendered through Twig |raw templates; exploitation requires victim interaction and a form entry created before the field was added. Overall risk signals converge on a genuine but moderate-priority issue rather than an emergency: EPSS is 0.18% (7th percentile), no KEV listing is present, a public PoC reference exists but is not verified as working exploit code, and vendor patch 4.7.0 is available.
An app already running on an affected Mac can win a race condition to corrupt process memory or cause unexpected system termination; Apple corrected the locking defect in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, and macOS Tahoe 26.7.2. Reachability is local only (CVSS 5.3, AV:L/AC:H/PR:L/UI:N), so an attacker needs existing low-privilege code execution on the host and must then win a timing window, making success non-deterministic and matching the SSVC 'Automatable: no' rating. No public exploit code or active exploitation has been identified at time of analysis, and EPSS is 0.15% (4th percentile), which supports scheduling the update in the current monthly cycle rather than treating it as an emergency.
Service metadata tampering in Esri ArcGIS Server 11.3 through 12.0 allows a remote, unauthenticated attacker with network reachability to update service metadata without user interaction, affecting integrity only (CVSS 5.3). The vendor restricts the affected window to 11.3-12.0 and provides patches for 12.0, 11.5, and 11.3; no public exploit code or CISA KEV entry was identified at time of analysis. This is a moderate, this-month remediation priority rather than an emergency.
Out-of-bounds read in the Box-Average Downsampler engine of FastStone Image Viewer (function FUN_0062d96c) affects versions up to and including 8.5 and can be triggered when a user opens a crafted image file in the application. Exploitation requires the victim to open the malicious file (CVSS 4.0 base score 5.3; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L), and because the trigger is confined to the downsampling path there is no remotely reachable service and no unattended exploitation route. Impact is bounded to partial memory disclosure or an application crash rather than code execution; no public exploit code was identified at the time of analysis, and the vendor was contacted about the disclosure but did not respond.
Resource exhaustion in NLnet Labs Routinator lets an attacker make the validator's HTTP server unavailable by opening a large number of connections that are never closed, consuming its finite open-connection capacity (CVSS 5.3, availability-only). Only operators who deliberately expose Routinator's HTTP or RTR server to untrusted networks are reachable; in a standard deployment bound to localhost or trusted internal networks the flaw is not remotely exposed. No KEV listing and no public exploit identified at time of analysis, so urgency is driven by deployment topology rather than an active campaign.
LearnPress, the WordPress learning-management-system plugin from ThimPress, leaves access-controlled functionality reachable without proper authorization in all versions through 4.4.11, letting remote attackers retrieve restricted information from affected sites. Per the assessed vector (AV:N/AC:L/PR:N/UI:N) no credentials or user interaction are needed, but the exposure is bounded: confidentiality impact is LOW while integrity and availability are unaffected, so this is information disclosure rather than account takeover or site compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the priority decision places it in this-month remediation rather than emergency response.
Missing authorization (CWE-862) in the TMS Amelia WordPress booking plugin, affecting versions through 2.4.10, lets remote unauthenticated attackers reach functionality that should require proper access-control checks, producing a low integrity impact with no confidentiality or availability loss (CVSS 5.3, PR:N/UI:N). Any WordPress site running a vulnerable Amelia version is potentially exposed, though the sources do not identify the specific endpoint or configuration that must be reachable, and whether a non-default setup is required is not described. A public PoC reference exists in the Patchstack advisory; it is not verified as working exploit code, and there is no CISA KEV confirmation of active exploitation.
Improper authentication in the Akubela HyPanel PS51 web login handler (firmware 51.130.40.26) lets a remote attacker reach an authenticated state by sending a request to /login with the engrmode argument set to 'admin'. Severity is moderate - CVSS v4.0 5.3 from the reporter, with an independent 3.1 assessment of AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L - and all three impact axes are rated low, so the resulting access may be limited rather than full device administration. A public proof-of-concept reference exists (a GitHub repository titled 'Authentication-Bypass-Vulnerability-in-akubela-HyPanel-PS51'), but it is not verified as working exploit code; no CISA KEV listing or EPSS score was supplied, and the vendor was contacted about the disclosure without responding, so no vendor patch is available.
Kantech Entrapass before 9.20 stores embedded sensitive information in cleartext in memory, so an actor with local access, high-level host privileges, and the required user interaction can retrieve that data. The issue is rated CVSS 5.3 and assessed as a moderate, low-urgency information-disclosure risk rather than a remote compromise path, because exploitation depends on pre-existing privileged local access and realistic exposure is confined to insiders or post-compromise situations. Vendor patching is available (upgrade to 9.20 or later); no public exploit identified at time of analysis.
A use-after-free in the Zephyr RTOS Bluetooth Classic host lets an adjacent, unauthenticated remote Audio Gateway crash or permanently hang the Bluetooth host thread on devices running 4.4.0 through 4.4.2 as an HFP Hands-Free unit (CONFIG_BT_CLASSIC and CONFIG_BT_HFP_HF enabled). When bt_hfp_hf_connect() starts an SDP discovery and the following bt_rfcomm_dlc_connect() fails, the old code wiped the live HFP HF object with memset(), destroying a node still linked into the SDP client's request list and a possibly-queued work item; the host later dereferences the NULL pool and function pointers or walks a self-referential list. Impact is denial of service only (CVSS 5.3, AV:A/AC:H/PR:N/UI:N/C:N/I:N/A:H, CWE-416) - the stray indirect call goes through an all-zero pointer the attacker does not control, so there is no code execution. No public exploit code was identified at time of analysis, but reachability depends on product application code that feeds a peer-discovered RFCOMM channel into bt_hfp_hf_connect(); the only in-tree caller is the shell sample, which limits exposure in default builds.