An open-redirect flaw (CWE-601) in the Atlas SQL JDBC Driver's authentication component lets a hostile or compromised endpoint steer the driver into handing an attacker-chosen URI to the operating system's default protocol handler during interactive sign-in. Only users who choose to connect the driver to an endpoint outside their trust boundary are exposed, and no confidentiality or availability impact is assessed - the outcome is a low-integrity effect from opening an arbitrary local address. No public exploit code or CISA KEV entry is associated with this issue at time of analysis, and it is rated a moderate, not high, priority (this_month) because exploitation hinges on user interaction and endpoint selection.
Denial of service in the AMD Compressonator SDK affects applications that parse untrusted DirectDraw Surface (DDS) files, where an integer overflow can crash or hang the consuming process when a local attacker supplies a crafted file. The CVSS 4.0 vector (AV:L/AC:L/PR:L/UI:P/VA:H, with VC:N and VI:N) means a local user or process with low privileges must actually load or process the malicious asset; there is no confidentiality or integrity impact and no network vector. No public exploit code or CISA KEV entry is identified in the available data, and the vendor bulletin AMD-SB-6032 is the primary reference; the vuln.today decision label is this_month, consistent with a medium-severity, availability-only issue rather than an emergency.
Stored cross-site scripting in PostfixAdmin through 4.0.5 lets an authenticated mailbox user persist a script payload in the description field of a TOTP exception, which then executes in the browser of a global administrator who opens totp-exceptions.php and can issue authenticated admin requests using that page's CSRF token. The same output-escaping defect exists in the application-password list (app-passwords.php), which the vendor commit fixes alongside the TOTP list. Exploitation is bounded: it needs a legitimate low-privilege mailbox account, the TOTP feature in use, and an administrator actually viewing the affected list page; the upstream fix is public (PRs #1172 and #1186), no tagged patched release is confirmed in the supplied data, and no public exploit code or active exploitation was identified at time of analysis.
Path traversal in SQLBot through 1.10.3 allows an authenticated workspace administrator to read files outside the upload directory by supplying an absolute path or ../ sequences in the filePath parameter of the /datasource/importToDb endpoint, with the imported content materialized into queryable excel_* tables. Impact is confidentiality-only and practically constrained: the targeted file must parse as CSV or a spreadsheet, so arbitrary binaries are not straightforwardly disclosed, and the attacker must already hold a high-privilege admin role (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N). The published score is 5.1 (CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N); a vendor fix exists in commit 3d15c67 and no public exploit code was identified at time of analysis, so this is a moderate-severity, high-privilege information-disclosure issue slotted for this-month remediation rather than an emergency.
Stored CSV formula injection in AzuraCast 0.23.8 and earlier allows a station user holding the Media permission to persist formula-prefixed values (leading =, +, -, @, tab, or carriage return) in media titles, artists, albums, genres, lyrics, ISRC, extra metadata, or station custom fields through POST /api/station/{station_id}/files/bulk. The injected payload is neutralized nowhere on export, so it becomes live the moment a second authorized user downloads the station's bulk media CSV via GET /api/station/{station_id}/files/bulk and opens it in a formula-evaluating spreadsheet such as Microsoft Excel. Impact is confined to the downstream spreadsheet client - the advisory explicitly disclaims server-side or OS-level code execution inside the AzuraCast process - and success depends on victim interaction plus the spreadsheet's version and security settings; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, consistent with a medium-severity, non-urgent priority.
CRLF injection in AzuraCast's public PLS playlist generation lets a station user who holds only the Station:MountPoints or Station:RemoteRelays permission plant extra FileN=/TitleN= entries into /public/{station}/playlist.pls, pointing guest listeners at an attacker-controlled stream that still displays the victim station's own name. The advisory scopes affected installations as AzuraCast before 0.24.0 and verifies the flaw on rolling release commit 2cb84e2f874d08ad9ff743ebda94fb30bc77041f; exploitation is second-order and depends on a guest downloading the playlist and using a media player that honors the injected entries, so impact stays within content spoofing and listener redirection with no code execution and no data exposure (assessed CVSS:3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N). Step-by-step reproduction requests are published in GitHub advisory GHSA-cqgx-rqjr-5gf4, so a public PoC reference exists, but it is not verified as working exploit code; no CISA KEV entry or other active-exploitation signal is present, and priority is this_month.
SurrealDB 3.1.0 through versions before 3.3.0 lets a database Owner bypass operator-defined port-specific deny-net rules and reach explicitly denied internal services, because the JWKS fetch path resolves URL ports with Url::port(), which returns None when an HTTP or HTTPS URL relies on the implicit default port. An attacker who can configure a JWT or record access method simply supplies a JWKS URL such as http://127.0.0.1/jwks.json (no :80) so that a rule like deny-net 127.0.0.1:80 receives a host-only target and no longer matches, producing a blind server-side GET against the denied endpoint. Exploitation requires authenticated Owner privileges (CVSS PR:H) and is only meaningful where port-specific deny rules are in place; the response is blind and parsed only as JWKS, so impact is limited to reachability, timing and parse-success inference with no integrity or availability effect. Scoring is medium (CVSS 4.0 base 5.1; internally assessed CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N), no public exploit code was identified at time of analysis although the vendor advisory includes a full reproduction test, and the issue is prioritised as this-month rather than emergency.
Stored cross-site scripting in AM System's Alo Suite lets an authenticated user persist JavaScript through the 'Nombre' field of the /Trabajadores/Create (worker creation) workflow, which is later rendered unsanitized in the delivery-note functionality and executes in the browser of any other user who opens the affected record. Exploitation requires a valid low-privileged account plus victim interaction - a second user actually viewing the record - after which the script can alter displayed content and act within the victim's session. Rated medium severity (CVSS 4.0 base 5.1; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), this aligns with a 'this_month' remediation priority rather than an emergency, and no public exploit has been identified at time of analysis.
Stored cross-site scripting in AM System Alo Suite's delivery-note functionality allows an authenticated user to persist JavaScript through the "Observaciones" field on the /Terceros/Create endpoint, which then executes in another user's browser when that record is viewed. The vendor-supplied CVSS 4.0 score is 5.1, with exploitation requiring a valid account that can create or edit delivery notes and a victim who subsequently opens the affected record; the payload can alter displayed content and perform actions in the victim's session. No public exploit code or CISA KEV entry was identified at time of analysis.
Stored cross-site scripting in Alo Suite (AM System) lets an authenticated user with access to the mail-template editor inject JavaScript through the 'Nombre' field at /PlantillasMail/Edit; the payload is persisted and then executes in the browser of another user who views the affected delivery-note records, allowing the attacker to alter displayed content and act within the victim's session. The vendor rates it CVSS 4.0 base 5.1, and the assessed impact is confined to the victim's session (S:C/C:L/I:L, no server-side confidentiality, integrity or availability impact). No public exploit was identified at time of analysis and there is no KEV listing; priority is routine (this_month).
Stored cross-site scripting in AM System's Alo Suite lets an authenticated user persist JavaScript through the 'Nombre' field of the delivery note / PDF template editor at /PlantillasPdf/Edit/1273129, which then runs in the browser of any other user who opens the affected record. The vendor-agnostic CPE entry (cpe:2.3:a:am_system:alo_suite:*:*:*:*:*:*:*:*) gives no version boundary, so all deployments of the affected module should be treated as potentially exposed until the vendor confirms a fixed release. Impact is confined to the victim's browser session in the application context (VC:N/VI:N/VA:N, SC:L/SI:L) and requires a second user to view the poisoned record; INCIBE rates it CVSS 4.0 5.1 (medium) and no public exploit code has been identified at time of analysis.
Stored cross-site scripting (CWE-79) in AM System Alo Suite lets an authenticated, low-privileged user persist JavaScript through the NombrePF field submitted to /Empresas/Create, which then executes in the browser of any user who later opens the affected company or delivery note record. Because the payload runs inside the victim's session, it can alter displayed content and perform actions as that user, although the vendor/NVD CVSS 4.0 score of 5.1 (AV:N/AC:L/AT:N/PR:L/UI:P, subsequent confidentiality and integrity Low) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) both keep the rating moderate: valid credentials and a second user viewing the stored record are prerequisites. No public exploit code was identified at time of analysis and the CVE is not in CISA KEV, so this is a this-month priority rather than an emergency.
Stored cross-site scripting in Alo Suite lets an authenticated user with access to /Inmuebles/Create persist JavaScript in the 'Nombre' field, which executes in another user's browser when that person views the affected delivery note or property record. The CVSS 4.0 base score is 5.1 (medium), and the issue is a scheduled, this-month remediation item; no public exploit was identified at time of analysis, and exploitation requires valid low-privilege credentials plus a victim viewing the poisoned record.
Stored cross-site scripting (CWE-79) in AM System's Alo Suite lets an authenticated low-privilege user plant JavaScript in the 'Nombre' field reached through the /Familias/Edit/{id} endpoint of the delivery-note functionality; the script is persisted without adequate sanitization and executes in the browser of any other user who later opens the poisoned record. Because the payload runs in the victim's authenticated session context, it can alter displayed content and perform actions as that user, although impact is confined to the victim's browser (scope change limited to low confidentiality and integrity). Exploitation is not remote-unauthenticated: it requires a valid low-privilege account to write the field plus a second user who views the record; no public exploit code and no CISA KEV active-exploitation listing were identified at the time of analysis, and the vendor priority signal rates it as an issue to handle this month.
Stored cross-site scripting in AM System's Alo Suite lets authenticated users with access to the current-accounts creation function persist JavaScript in the 'Nombre' field of delivery-note records, where it executes in another user's browser when that record is viewed. The issue is medium severity (CVSS 5.1, CVSS 4.0; CWE-79) and requires both a valid low-privileged account and victim interaction, so the payload does not fire automatically or affect unauthenticated users. Impact is limited to the victim's browser session (SC:L/SI:L), with no stated effect on the server's own confidentiality, integrity, or availability; no public exploit was identified at time of analysis.
Stored cross-site scripting in AM Systems Alo Suite lets an authenticated user with write access to the 'Codigo' field of the '/CategoriasFicheros/Edit/{id}' endpoint persist JavaScript that later executes in other users' browsers when they open the affected delivery-note record. The injected script runs in the victim's session context, allowing the attacker to alter displayed content and perform actions as that user; there is no direct server-side confidentiality, integrity or availability impact. Rated CVSS 4.0 base 5.1 (assessed CVSS 3.1 vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), it requires a valid account with access to this feature plus victim interaction, and no public exploit code or active exploitation has been identified at time of analysis; priority is this_month.
Stored cross-site scripting in Alo Suite lets authenticated users with article or delivery-note creation rights inject JavaScript through the Nombre parameter of /Articulos/Create, and the script executes in the browser of another user who later views the affected record. The reported CVSS 4.0 base score is 5.1 (medium), with the independent assessment scoring it CVSS 3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Impact is limited to the victim's browser session, and no public exploit was identified at time of analysis.
Stored cross-site scripting in Alo Suite's delivery note editor allows a user who can edit delivery notes to persist JavaScript through the ReferenceOtherParty field on the /Documents/DeliveryNotes/Edit/{id} endpoint, which then executes in the browser of any other user who opens the affected record. The vendor rates it CVSS 4.0 base 5.1 and our assessment scores it CVSS 3.1 6.1 with scope change, reflecting that impact is confined to the victim's browser session (content modification and actions performed as that user) rather than the server. Exploitation requires an authenticated low-privilege account plus a second user viewing the tampered note; no public exploit code or CISA KEV entry was identified at time of analysis, and the priority label is 'this_month' rather than an emergency.
Clickjacking in the AM Systems Alo Suite web application lets an attacker embed the login interface inside an attacker-controlled page and trick a victim into clicking disguised controls, so the practical impact is tampering with user interactions rather than disclosure of data. Deployments are exposed when the login page is served without X-Frame-Options or a Content-Security-Policy frame-ancestors directive; the CPE entry carries a wildcard version, so no specific release range is pinned in the available data. Severity is moderate (CVSS 4.0 base 5.1, integrity-only impact rated Low, active user interaction required), the issue is not listed in CISA KEV, and no public exploit code was identified at time of analysis.
Path traversal (CWE-22) in Tanium Data Service, with Tanium Interact also listed among the affected components, allows a high-privileged, authenticated attacker reaching the service over the network to manipulate files in a way that compromises integrity (rated High) and, to a lesser degree, availability (Low), with no confidentiality impact. Tanium reports it has addressed the issue in advisory TAN-2026-082, and the CVSS 3.1 base score is 5.0 (AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:L). No public exploit code or confirmed active exploitation was identified at time of analysis, and the vuln.today priority decision places it in the this_month remediation cadence rather than an emergency one.
SQL injection in WooCommerce Multilingual & Multicurrency with WPML up to and including 5.5.7 lets an authenticated attacker with Shop Manager-level access or above store a crafted currency exchange-rate value that is later concatenated into an ORDER BY clause, allowing additional SQL queries to read sensitive database contents. The weakness is confidentiality-only and requires the plugin to be active with multicurrency configured; no public exploit or CISA KEV entry was identified at time of analysis. CVSS 4.9 reflects the high privilege prerequisite rather than low real-world exposure.
WSO2 Identity Server and the related WSO2 Carbon OAuth family of products will issue OAuth2 access tokens for JWT Bearer and SAML2 Bearer grant requests even when the federated Identity Provider (IDP) that vouched for the assertion has been disabled, because the IDP's enabled state is not re-validated before the token is minted. Remote unauthenticated attackers can exploit this only if they already hold a valid assertion issued by that now-disabled IDP, which is why the vendor rates it CVSS 4.8 with high attack complexity (AC:H) and limited confidentiality/integrity impact. It is not listed in CISA KEV and no public exploit has been identified at time of analysis, but the priority label is this_month, so it warrants scheduling rather than emergency response.
pybddisasm 0.3.0 and earlier can disclose residual process memory to any consuming application that reads an INSTRUX object returned by a failed instruction decode. The four decode entry points leave the returned object uninitialized when decoding fails, including failures caused by invalid parameters, so an application that surfaces those members after a failure may expose leftover heap or stack contents; a caller that checks the decode status first is unaffected. The package is unmaintained with no fixed release, the vector is local and privilege-gated with confidentiality-only impact, and no public exploit has been identified at time of analysis.
Out-of-bounds reads in the pybddisasm Python bindings for the Bitdefender disassembler can expose up to roughly 15 bytes of adjacent process memory when an integrating application decodes a buffer that is shorter than the length it declares. nd_decode may read up to 15 bytes regardless of the actual Python buffer length, while nd_decode_ex, nd_decode_ex2, and nd_decode_with_context pass a caller-supplied size to the decoder without checking it against the real buffer, and nd_get_instrux_bytes then returns a fixed 16-byte list that can carry the leaked bytes. Exploitation is not self-contained: it requires a host application to make these calls with mismatched buffer/length arguments and to surface the decoded bytes to an attacker, and the affected package is no longer maintained, so fix responsibility falls to integrators. All quantitative signals point to a modest, non-urgent issue; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Stored cross-site scripting in AWS Amplify's maplibre-gl-js-amplify library (versions through 4.0.2) lets an authenticated user who can write location or geofence data persist an HTML/JavaScript payload that later executes in a different user's browser session when the affected map popup or geofence list item is rendered. The vulnerable sinks are the GeoJSON feature properties title, address and place_name used by popupRender, plus the geofenceId value rendered in AmplifyGeofenceControl list items and the delete-confirmation prompt; the payload fires only when a victim interacts with the element, such as clicking the marker or opening/deleting a geofence entry, so this is not a drive-by issue. No public exploit code or active exploitation has been identified at time of analysis, and the vendor-released patch is version 4.0.3, which escapes the affected values via a new escapeHtml() utility.
An out-of-bounds read in wlroots's XWayland window-management code (read_surface_class() in xwayland/xwm.c) lets a local X11 client leak a small amount of compositor heap memory by setting a WM_CLASS property whose instance string is NUL-terminated but whose class string is not. All wlroots releases before 0.20.2 are affected, but only when the compositor runs with XWayland support active and an attacker already has a local client inside that session. The over-read bytes are surfaced back as the window class or app_id over IPC, giving confidentiality-only exposure with no integrity or availability impact; the vendor shipped a fix in 0.20.2, and no public exploit code was identified at time of analysis.
Server-side request forgery guard bypass in SurrealDB 3.2.x lets an authenticated user reach internal or private IPv4 endpoints by routing outbound HTTP through IPv6 transition addresses (NAT64, 6to4, Teredo) that the FilteringResolver's is_private_ip check fails to unwrap. Only deployments that actually have one of those transition mechanisms active, and whose users can trigger outbound requests via SurrealQL http:: functions, webhook deliveries, or OIDC metadata fetches, are exposed; targets of interest include localhost services, internal hosts, and cloud instance metadata at 169.254.169.254. The GitHub security advisory (GHSA-c9wc-jcr5-8974) publishes illustrative payloads such as 64:ff9b::7f00:1 and 2002:a9fe:a9fe::, but no verified working exploit code was identified, and there is no CISA KEV confirmation of active exploitation; the vulnerability.today decision label is this_month, reflecting a conditional, moderate-severity issue rather than an emergency.
A use-after-free in Zephyr's MCTP over USB device class lets a physically attached USB host race class teardown against the RX parsing worker, freeing the packet buffer at usb->rx_pkt while the worker still writes host-supplied bytes through it. Only builds of Zephyr 4.4.0 through 4.4.x (fixed in 4.5.0) that enable the experimental CONFIG_MCTP_USB binding are affected; the host needs no credentials or user interaction but must control the bulk OUT endpoint and the SET_CONFIGURATION/bus-reset timing. A public PoC reference exists and was reproduced on native_sim, but it is not verified as working exploit code on real USB hardware, natural-hardware trigger probability remains unverified, and no active exploitation is confirmed.
Sensitive information disclosure in the underlying operating system of HPE Networking Fabric Composer allows an authenticated, low-privileged user who already holds local access to the appliance to read data they should not be able to see, with a published CVSS 3.1 base score of 4.7 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N). Exploitation is constrained: the HPE advisory states that 'certain preconditions outside of the attacker's control' must be met, which is why the attack complexity is rated High and why the issue should be treated as opportunistic rather than reliably repeatable - the specific feature, configuration or system state involved is not described in the available sources. Only confidentiality is affected; there is no integrity or availability impact, no public exploit code or PoC reference appears in the supplied intelligence, and the issue is not listed in CISA KEV, so no public exploit was identified at time of analysis.
HDF5 through 2.2.0, when compiled with szip support, reads past the end of a chunk buffer while decoding a szip-compressed chunk in H5Z__filter_szip(): the function subtracts the 4-byte uncompressed-length header from the chunk length without first verifying the chunk is longer than that header, so a truncated or corrupted chunk record makes the size_t subtraction wrap to a very large value and the decompressor reads far beyond the stored data, crashing the process. An attacker triggers it by getting a user or application to read a dataset from a crafted HDF5 file, so the attack is local (AV:L) and requires the victim to open the file (UI:R / UI:P), with impact confined to denial of service (assessed CVSS 3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H; CVSS 4.0 4.7). Only szip-enabled builds (libaec or the szip library) are affected, the CVE is not in CISA KEV, and the CVSS 4.0 vector records Proof-of-Concept-level exploit maturity (E:P) while no verified working exploit code is identified in the available sources; the issue is rated medium severity and prioritized 'this_month' rather than as an emergency.
Zephyr 4.4.0 through 4.4.x (fixed in 4.5.0) drops a Bluetooth Classic AVRCP Target connection without cancelling its vendor-dependent response transmit work or releasing the response buffers still parked on the pending list, so a partly transmitted fragmented response is left behind with the TX_ONGOING flag set. Because the Target objects are static and reused by connection index, the next peer landing on that index inherits a permanently stalled TX machine: every vendor-dependent response queues behind the stale head and never leaves the device, one buffer leaks per cycle from a shallow pool, and a new peer that issues REQUEST_CONTINUING_RESPONSE can be sent the un-transmitted remainder of the previous peer's response. The attack is deterministic but requires an already-paired peer within radio range because the AVCTP control channel mandates an encrypted BR/EDR link; no user interaction is needed, the severity is moderate (CVSS 4.6), and no public exploit code was identified at time of analysis.
BuildKit through v0.34.0 lets a client holding access to the daemon's control API set an extended attribute on a file outside the BuildKit state directory, including attributes in the trusted. and security. namespaces, which can leave a program on the host with more privilege than it should have. The flaw is genuine but conditional: the vector is local with high privileges required (a legitimate control-API client), so only build services that accept build requests from untrusted users - multi-tenant or hosted CI build backends - are realistically exposed, while default single-user Docker builds are not. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); the vendor fix is v0.34.1.
Tanium Discover contains an uncontrolled resource consumption flaw (CWE-400) that a network-reachable, low-privileged authenticated user can trigger to degrade availability, rated CVSS 4.3 with impact limited to a low availability loss and no confidentiality or integrity effect. Only the Discover asset-discovery module is affected, not the wider Tanium platform, and the sources do not specify which feature or input triggers the resource exhaustion. There is no KEV listing and no public exploit identified at time of analysis; this is a low-priority item despite being a tracked CVE, with the authentication prerequisite being the principal limiting factor.
Information disclosure in Tanium Discover lets an authenticated low-privileged user retrieve limited confidential data over the network without user interaction. The flaw carries a CVSS score of 4.3 and is rated this_month in priority; no public exploit was identified at time of analysis. The specific Discover feature, configuration, or request that triggers the exposure is not described in the available sources, and impact is confined to confidentiality with no integrity or availability effect.
Information disclosure in Tanium Discover allows an authenticated, low-privilege user with network access to obtain limited confidential information from the platform (CVSS 4.3, C:L). Tanium addressed the issue in its Discover module; the affected CPE covers Tanium Discover with no specific version range enumerated in the available data. No public exploit identified at time of analysis, and the vendor-reported severity plus the PR:L requirement keep this a moderate, this-month priority rather than an emergency.
Improper input validation in Tanium Threat Response (CVSS 4.3) gives an authenticated low-privilege user a limited ability to affect data integrity over the network, with no confidentiality or availability impact and no scope change. The flaw requires an existing Threat Response session (PR:L) and low attack complexity, and the specific endpoint or parameter that is improperly validated is not named in the available sources. No public exploit was identified at the time of analysis, and the issue is a moderate-severity, lower-priority item rather than an urgent threat.
A business logic error in Tanium Threat Response (CWE-628) lets a remote attacker who already holds a valid low-privileged account cause a limited integrity impact; the CVSS 4.3 vector rates confidentiality and availability as unaffected. Tanium published the issue under advisory TAN-2026-081, and no public exploit code or CISA KEV entry was identified at time of analysis. The authentication prerequisite (PR:L) is the main limiting factor, keeping this at moderate rather than urgent priority.
Uncontrolled resource consumption in Tanium Threat Response lets a network-positioned user who already holds valid low-privilege credentials exhaust service resources and degrade availability, scored CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) with availability as the only impacted property. The flaw is rated this_month under the vuln.today priority decision, reflecting low-to-moderate urgency rather than an emergency: authentication is a hard prerequisite (PR:L, so this is not a pre-authentication flaw), there is no confidentiality or integrity impact, and no public exploit has been identified at time of analysis. There is no CISA KEV listing, and the description does not name the specific feature, API, or protocol that triggers the resource exhaustion.
Authenticated information disclosure in HPE Networking Fabric Composer lets a remote attacker with low-level credentials query a specific API endpoint and obtain limited details about the affected system (CVSS 4.3, PR:L, C:L). The issue is low-to-moderate priority: it requires prior authentication, has no integrity or availability impact, and no public exploit identified at time of analysis. The available advisory data does not name the vulnerable endpoint, the exact required role, or a fixed version.
Authenticated visitor-role users on MyTube deployments running versions before 1.10.6 can submit crafted event batches to the statistics ingest endpoint and falsify the analytics an administrator sees, corrupting view counts, download counts, platform breakdowns, source attribution and session metrics. Exploitation depends on a non-default configuration in which the administrator has turned on both statisticsEnabled and statisticsTrackVisitorActivity, and on the attacker knowing the shared visitor password to obtain a session; the server-derived actorRole and surface dimensions cannot be forged this way. Impact is integrity-only against reporting data - no sensitive data disclosure, no code execution, no availability loss - and the advisory's reproduction is a hand-crafted curl request rather than confirmed working exploit tooling; this is a scheduled, low-to-moderate priority fix rather than an emergency.
Non-terminating symbolic-reference resolution in isomorphic-git 1.38.5 and earlier lets a malicious or man-in-the-middle-controlled Git remote brick a client repository: circular symref= capabilities advertised by the server are persisted to disk by updateRemoteRefs, and any later operation that resolves refs/remotes/origin/a or refs/remotes/origin/b (log, status, checkout, branch) hangs indefinitely. The attack is gated on the victim choosing to clone from the untrusted or compromised remote (UI:R, PR:N), and the result is a persistent denial of service only - no data exposure or code execution (CVSS 3.1 base 4.3, A:L). No CISA KEV entry or confirmed in-the-wild exploitation is reported; the GHSA advisory references a public proof-of-concept repository demonstrating the hang, which is a PoC reference rather than exploit code independently verified as working.
Unbounded memory allocation in isomorphic-git before 1.38.6 allows a malicious or man-in-the-middle-controlled Git remote to force git.clone() or git.fetch() to allocate roughly 2 GB from a single packfile delta, causing denial of service on memory-constrained hosts. The server-controlled delta targetSize is passed to Buffer.alloc without an upper bound in src/utils/applyDelta.js, and Node.js heap limits do not mitigate the off-heap allocation. The vendor fixed this in 1.38.6; a public PoC reference exists but is not verified as working exploit code, and no CISA KEV active-exploitation confirmation is provided.
CVE-2026-97072 is a missing authorization flaw (CWE-862) in the myCred WordPress plugin affecting all versions up to and including 4.0.2, allowing an attacker holding a low-privilege authenticated account to perform actions that should require higher access, with integrity-only impact. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, 4.3) confirms exploitation requires a valid low-privilege account on the target site and is not remote-unauthenticated; no public exploit code or CISA KEV entry is associated with this issue. Risk is moderate and the priority signal points to patching in the normal cycle, since a valid WordPress account on a site running the affected plugin is a prerequisite and no confidentiality or availability impact is assessed.
The myCred WordPress plugin (all versions through 4.0.2) fails to enforce authorization checks on at least one of its actions, letting a logged-in low-privilege user such as a subscriber or customer trigger operations that should require higher capabilities. The impact is integrity-only - site data or myCred point balances and settings may be altered - with no confidentiality or availability impact and no user interaction required beyond having an account. No public exploit code has been identified at time of analysis, and the issue is rated low-to-moderate priority for remediation within the current monthly cycle.
Missing authorization in the WC Lovers WCFM Membership WordPress plugin (wc-multivendor-membership) through 2.12.0 lets a low-privilege authenticated user - for example a registered customer or vendor on a WCFM-powered marketplace - perform actions that should require higher privileges, producing an integrity-only impact (CVSS 4.3, PR:L, no confidentiality or availability loss). Exploitation requires a valid account on the target site and is reachable over the network without user interaction; the specific plugin feature, action or endpoint lacking the check is not described in the available sources. There is no KEV entry and no public exploit identified at time of analysis, and the priority is 'this_month' rather than emergency - a genuine but low-urgency issue.
Script-related HTML injection in the WPMU DEV Forminator plugin for WordPress, in versions up to and including 1.58.3, allows a low-privileged authenticated user to place script-bearing markup into a Forminator feature that accepts input, where the plugin fails to neutralize it. Successful abuse depends on a second party - typically an administrator or another site user - subsequently rendering the injected content, and the scope change in the assessed vector reflects that the payload executes in the victim's browser context rather than the attacker's. No public exploit code and no CISA KEV entry were identified at time of analysis, and this is a low-to-moderate priority issue rather than an emergency.
Information disclosure in Elasticsearch lets an authenticated user whose role applies field-level security (FLS) read the value of a constant_keyword field that the role is supposed to exclude, because certain search and query features do not enforce the FLS restriction for that field type. Only clusters where FLS is configured to exclude a constant_keyword field are exposed, and the leaked data is a single constant value shared across the index, so confidentiality impact is low with no integrity or availability effect; the underlying flaw is an incorrect authorization check (CWE-863 / CAPEC-1). The issue is addressed by the Elastic security update ESA-2026-209 covering versions 8.19.24, 9.4.9 and 9.5.6, and no public exploit identified at time of analysis; priority is assessed as this_month rather than immediate action.
Information disclosure in Elastic Kibana lets an authenticated user who holds read access to connectors in one Kibana space retrieve connector execution log records from other spaces they are not authorized to view. The exposed data is metadata only: connector names and identifiers, execution status, timestamps, error messages and aggregated execution statistics, with no integrity or availability impact (CVSS 4.3, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N). Exploitation requires a valid low-privilege account and a deployment that uses multiple spaces for access segregation; no public exploit or PoC has been identified at time of analysis, and the issue is not in CISA KEV.
Information disclosure in Elastic Kibana's Machine Learning feature allows an authenticated user with Machine Learning read access in one Kibana space to read audit and error messages for data frame analytics jobs in other spaces, exposing destination index names, analyzed field names, and failure details. The issue is a low-to-moderate severity authorization bypass (CVSS 4.3) limited to job metadata, with no integrity or availability impact, and no public exploit identified at time of analysis. Elastic has released fixes in Kibana 8.19.24, 9.4.9, and 9.5.6.
Elastic APM Server can hand an authenticated APM agent the central agent configuration belonging to a different service - including sampling settings - because of a duplicate-identifier flaw (CWE-694) in how agent configuration requests are resolved. The mix-up lasts only until the cached configuration expires, so the result is timing-dependent rather than reliably attacker-controlled, and it only manifests where one APM Server provides central configuration to more than one service. Exploitation requires agent credentials (CVSS PR:L, network-reachable) and yields limited confidentiality impact; no public exploit has been identified at time of analysis, and Elastic has published fixed releases 8.19.24, 9.4.9 and 9.5.6.