Cross-site scripting in the oik plugin for WordPress (versions 4.15.4 and earlier) allows script injection that executes in a victim's browser session, with the Patchstack advisory scoping the issue to Subscriber-level users. The reported CVSS 3.1 vector scores 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L), but the PR:N rating conflicts with the 'Subscriber' qualifier, which indicates a low-privilege authenticated account is the probable prerequisite, and exploitation additionally requires a victim to render the injected payload (UI:R). No public exploit code, no CISA KEV listing, and no confirmed patched release were identified at time of analysis, and the plugin's niche deployment combined with the authentication and interaction requirements keeps practical risk below what the raw 7.1 figure implies.
Cross-site scripting in the Trusted Shops Easy Integration for WooCommerce plugin through version 2.0.6 allows unauthenticated attackers to deliver crafted input that executes as script in a victim's browser session once that victim is induced to follow a malicious link or request (UI:R, PR:N). Impact is bounded to Low for confidentiality, integrity and availability while the vulnerable component's scope is changed (S:C), producing a 7.1 CVSS base score, and no public exploit code or confirmed active exploitation was identified at time of analysis. Because successful attacks depend on social engineering a store visitor or authenticated administrator, this is a moderate-risk issue rather than an urgent priority; the site must have the plugin installed and active.
Unauthenticated reflected cross-site scripting in the WooCommerce Product Table Lite WordPress plugin (versions up to and including 5.6.7) allows an attacker to execute arbitrary script in a victim's browser within the affected store's origin by luring that user to a crafted URL or request that reflects the malicious payload, potentially leading to session theft or actions performed as the victim. Exploitation is gated by mandatory user interaction (CVSS 3.1 7.1 High, AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) and requires the plugin to be installed and active on a WordPress site that also runs WooCommerce, so practical risk is bounded by the social-engineering step needed to deliver the link. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS data was provided; the issue was reported by Patchstack.
Cross-site scripting (XSS) in YITH WooCommerce Ajax Search versions 2.28.0 and earlier allows unauthenticated attackers to inject malicious scripts into web pages viewed by other users, requiring victim interaction such as clicking a crafted link. The vulnerability is rated CVSS 7.1 with a scope change (S:C) and low confidentiality, integrity, and availability impact. No public exploit code or active exploitation has been identified at time of analysis, but the plugin is widely used in WordPress e-commerce sites, making timely patching advisable.
Unauthenticated cross-site scripting (XSS) in the Classified Listing WordPress plugin (by radiustheme) affects versions up to and including 6.1.3, allowing remote attackers to inject malicious JavaScript that executes in the browser of a victim user who views a crafted page. The CVSS 3.1 score is 7.1 (High) with vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, indicating network exploitation without privileges but requiring user interaction, and limited impact on confidentiality, integrity, and availability. No public exploit code or active exploitation has been identified at time of analysis, but the plugin's widespread use on WordPress sites makes it a potential target for attackers seeking to compromise administrative sessions or deface sites.
Missing authorization checks in the FormGent WordPress plugin (versions through 1.12.2) allow an authenticated user holding only a subscriber-level account to reach form-management functionality and data normally reserved for higher-privileged roles, yielding high confidentiality impact and limited integrity impact. The flaw is network-reachable and needs no user interaction, but it does require a low-privileged account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, 7.1), so sites that permit open user self-registration are the most exposed while registration-restricted sites are considerably less at risk. No public exploit identified at time of analysis, and the vulnerability has not been confirmed as actively exploited (CISA KEV).
Unauthenticated cross-site scripting in the WordPress Persistent Login plugin (author lukeseager) at versions 3.1.3 and earlier allows a remote attacker to execute arbitrary script in a victim's browser by luring them into loading attacker-influenced content that reaches the vulnerable sink; per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) exploitation needs victim interaction but no authentication. The issue is rated High at 7.1, with scope change and low impact to confidentiality, integrity and availability confined to the victim's browser session, and the exact vulnerable parameter is not detailed in the advisory data. No public exploit code was identified at time of analysis, and there is no indication of confirmed active exploitation (no CISA KEV listing); no EPSS score was supplied.
Cross-site scripting in the Site Reviews WordPress plugin through version 8.3.1 allows unauthenticated remote attackers to inject script that executes in a victim's browser when the victim loads a page rendering the malicious content, with CVSS 3.1 scoring it 7.1 High due largely to scope change and unauthenticated reach. Exploitation requires user interaction (UI:R) and is most realistic on sites that accept untrusted or public review submissions or otherwise render attacker-controlled input to a privileged viewer, and there is no public exploit identified at time of analysis. Impact is limited to the browser context, such as session or credential theft and action forgery, rather than direct server compromise.
Cross-site scripting (XSS) in the WP Statistics WordPress plugin (versions 14.16.13 and earlier) enables remote, unauthenticated attackers to inject malicious scripts into web pages. Exploitation requires a victim to interact with a crafted link or page, after which the script executes in the victim's browser context, potentially leading to session hijacking or data theft. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated cross-site scripting in the WordPress plugin Notification for Telegram (versions up to and including 3.5.2) lets a remote attacker inject script that executes in a victim's browser when the crafted content is rendered. No authentication is required to deliver the payload (PR:N), but exploitation depends on a logged-in or administrative user visiting the page where the injected script is displayed (UI:R), and the resulting impact is limited to the client side with low confidentiality, integrity, and availability effects under a scope change (S:C). No public exploit code has been identified and there is no confirmed active exploitation (no CISA KEV listing); EPSS data was not provided, so no exploitation-probability figure is asserted here.
Unauthenticated cross-site scripting in JW Player for WordPress 2.3.11 and earlier allows remote attackers to inject script into a victim's browser when the victim interacts with a crafted link or attacker-influenced page. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) reflects a network-reachable, low-complexity flaw that requires no attacker authentication but does require user interaction; successful exploitation runs script in the victim site's origin due to scope change. The issue is reported via Patchstack, and no public exploit or CISA KEV active-exploitation confirmation was provided at time of analysis.
Reflected cross-site scripting (XSS) in WPFunnels plugin versions 3.13.1 and earlier allows unauthenticated attackers to execute arbitrary JavaScript in a victim's browser when they are tricked into clicking a crafted link. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) indicates network-reachable, low-complexity exploitation requiring user interaction but no authentication, with a scope change and limited confidentiality, integrity, and availability impact. No public exploit code or active exploitation has been identified at the time of analysis.
Arbitrary file read in Digiwin EasyFlow .NET allows an authenticated remote user to download files from the underlying host outside the intended document scope, exposing configuration files, credentials, or other sensitive data. Exploitation requires a valid low-privilege session (PR:L per the CVSS v4.0 vector and the corroborating CVSS v3.1 assessment) but no user interaction and only low attack complexity, so any party holding a legitimate account can reach the flaw over the network. Impact is confined to confidentiality - the vulnerability does not modify data or affect availability - and no public exploit code or confirmed in-the-wild exploitation has been identified at time of analysis.
SQL injection in Digiwin EasyFlow .NET allows an authenticated, low-privilege remote user to read arbitrary contents of the application's backend database. Per the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N), exploitation is network-reachable and low-complexity but requires a valid account (PR:L) and produces high confidentiality impact only - no integrity or availability effect, consistent with a read-only data-exfiltration primitive. The CVSS base score is 7.1; no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, and no EPSS score was provided with the source data.
An out-of-bounds write in the Pgpool-II connection pooling and load-balancing middleware allows an authenticated remote attacker to trigger abnormal termination of the Pgpool-II process, denying service to PostgreSQL clients routed through it. Exploitation requires valid credentials accepted by the Pgpool-II frontend (PR:L) and network reachability to its listening port; no user interaction or high privileges are needed, and the assessed impact is availability only (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, vendor-scored 7.1 under CVSS 4.0). Affected releases are Pgpool-II 3.5.x through 4.2.x, 4.3.0-4.3.20, 4.4.0-4.4.17, 4.5.0-4.5.12, 4.6.0-4.6.7 and 4.7.0-4.7.2. There is no public exploit identified at time of analysis and the CVE is not listed in CISA KEV, so this is a genuine but bounded-severity availability issue rather than an active exploitation campaign.
Stored cross-site scripting in the WP Mobile Menu WordPress plugin (versions 2.7.4 up to but not including 2.9) lets an attacker import arbitrary plugin settings through a forged cross-site request in a logged-in administrator's session, because the settings-import routine does not correctly verify its nonce. The imported values are then rendered unescaped to every site visitor, so the injected script persists and executes for all users until the malicious setting is removed. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) shows the attacker needs no account of their own but must socially engineer a privileged, authenticated admin into loading the crafted request; there is no public exploit code identified at time of analysis, exploitation has not been observed, and patch status is vendor-released version 2.9.
Authenticated plugin installation in the Vayu X WordPress theme before 1.0.6 allows any logged-in user - even a Subscriber - to install and activate arbitrary plugins hosted on the WordPress.org repository. The theme's AJAX action omits a capability check (CWE-284) and leaks its guarding nonce to every authenticated user, so the nonce provides no protection whatsoever; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L, 7.1) reflects high integrity impact with no user interaction required. Exploitation is limited to WordPress.org-hosted plugins rather than arbitrary code upload, so maximum impact depends on chaining to a vulnerable installable plugin; no public exploit code has been identified at time of analysis, there is no confirmed active exploitation (CISA KEV), and CISA SSVC rates exploitation as none and automatable as no.
Stack exhaustion in the Gosub browser engine (gosub-engine through 0.1.0 and main before commit 46868b3) lets a remote, unauthenticated attacker crash any application built on the engine by getting it to render an SVG document containing an excessive number of deeply nested elements. The malicious SVG can be embedded via the SRC attribute of an IMG element on an attacker-controlled page, so exploitation requires only that a victim visit that page (UI:P) - no credentials are needed (PR:N) and the attack is network-reachable (AV:N). Impact is availability-only (a hard crash of the host application; no data exposure or code execution), no public exploit code has been identified at time of analysis, and the practical exposure is limited to the narrow set of deployments embedding the engine at those revisions, making this a genuine but low-priority issue.
Authorization bypass in the MSSP (multi-tenant) module of AiSOC 10.0.0 through before 12.0.0 allows any authenticated user who already owns at least one portfolio to submit arbitrary tenant UUIDs to the add_tenants_to_portfolio endpoint and pull unclaimed tenants into their own portfolio without those tenants' consent. Once a victim tenant is claimed, the attacker can read its security alerts, incidents, and posture metrics, giving high confidentiality impact with limited integrity impact but no availability loss (assessed CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N). Exploitation requires a valid account with portfolio ownership in an MSSP-enabled deployment and only works against tenants not already managed by another organisation; single-tenant installations are unaffected, and no public exploit code was identified at time of analysis.
Unauthenticated XML External Entity (XXE) processing in Kiteworks Email Protection Gateway allows a remote sender to read files accessible to the gateway service account - including cryptographic key material and credentials - and have them sent to a destination the sender controls. The vulnerable parsing path is only reachable when the optional, non-default message-processing feature is enabled, which is the sole reason the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L carries AC:H despite needing no authentication or user interaction; default installations are not exposed. Per the provided intelligence, no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status, and impact is bounded to files readable by the gateway service account plus the limited integrity/availability side effects typical of XXE.
Axios versions 1.15.0 through 1.19.x silently ignore CIDR-form NO_PROXY entries in its Node.js adapter, so requests destined for loopback, RFC1918 private, Kubernetes, CI, or cloud-metadata ranges can be routed through a configured HTTP_PROXY/HTTPS_PROXY that the operator intended to bypass. The assessed severity is moderate (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N, 4.8) because exploitation depends on a specific non-default configuration - Node.js adapter, proxy environment variables set, and CIDR notation used in NO_PROXY - and only causes exposure or tampering of proxied traffic rather than code execution or authentication bypass. There is no confirmed active exploitation (CISA KEV) and no EPSS data supplied, but the vendor advisory ships a working local proof-of-concept demonstrating that NO_PROXY=127.0.0.0/8 does not prevent HTTP_PROXY from receiving a request to 127.0.0.1; the vendor-released fix is axios 1.20.0.
Unauthenticated information disclosure in the yii2-starter-kit application template through version 4.2.0 allows remote attackers to download file attachments that belong to unpublished (draft) articles by calling the attachment-download endpoint directly. The endpoint in frontend/controllers/ArticleController.php serves the requested file without verifying the publication status of the parent article, and because attachment identifiers are sequential and predictable, an attacker can enumerate them to harvest draft content; no credentials, user interaction, or non-default configuration are needed (CVSS:4.0 PR:N/UI:N, assessed as CVSS:3.1 AV:N/AC:L/PR:N/UI:N with C:L only). Impact is confined to reading draft attachments - there is no write, modification, or denial-of-service effect - and no public exploit code or confirmed active exploitation has been identified at time of analysis, so real-world risk depends mainly on whether a deployed site built from this starter kit leaves the vulnerable controller unmodified.
Local privilege escalation, code execution, denial of service, information disclosure, and data tampering are possible in NVIDIA GPU Display Driver for Linux due to a use-after-free in the open-source kernel module's event-delivery path. An authenticated local user with access to NVIDIA GPU device nodes can race asynchronous event delivery against file close (CVSS 7.0, AV:L/AC:H/PR:L/UI:N), though the high attack complexity makes success non-deterministic and typically requires repeated attempts; no public exploit has been identified at time of analysis. Risk is concentrated on Linux hosts using the affected open-source kernel module, particularly multi-tenant vGPU, VDI, and cloud GPU deployments.
Local privilege escalation in the NVIDIA GPU Display Driver for Linux kernel-mode layer allows an already-present local user or code-execution foothold (PR:L) to write to memory that should be read-only because memory permissions are not preserved, potentially achieving code execution and elevated privileges on affected GeForce, RTX/Quadro/NVS, and Tesla systems, including vGPU Guest Driver deployments. Exploitation requires local access and high attack complexity, with no remote or unauthenticated network path; no public exploit was identified at time of analysis and the CVE is not listed in CISA KEV. The vendor-supplied CVSS vector uses AV:P while our independent assessment uses AV:L, so the physical-access requirement should be confirmed against NVIDIA bulletin 5861.
Out-of-bounds write in the NVIDIA GPU Display Driver for Windows kernel module can let a local, authenticated low-privileged user execute code, escalate privileges, cause denial of service, disclose information, or tamper with data on affected GeForce, RTX/Quadro/NVS, and Tesla systems. Exploitation requires local access to the GPU-equipped Windows host plus a low-privileged account able to reach the kernel module, and the high attack complexity means it is not reliably one-shot; multi-user, VDI, and cloud/virtual-GPU environments are the main risk. No public exploit identified at time of analysis, and CVSS is 7.0 with high confidentiality, integrity, and availability impact.
LightLLM through version 1.2.0 accepts image_url and audio_url parameters on its multimodal inference endpoints without validating or restricting the supplied URLs, allowing unauthenticated remote attackers to coerce the server into making arbitrary outbound HTTP requests (CWE-918 server-side request forgery). An attacker who can reach an instance configured to serve a vision or audio model can point those parameters at internal-only resources, and because the fetched content is passed into model processing, the results (or the resulting error messages) can leak internal content and network topology back to the caller. Impact is limited to confidentiality and topology disclosure rather than code execution; the issue is a genuine but moderate-severity exposure, no public exploit code has been identified at time of analysis, and it has not been confirmed actively exploited (no CISA KEV listing). Deployments that only serve text models, or that do not expose multimodal endpoints to untrusted networks, are out of scope.
IP whitelist and blacklist enforcement in the Pecee simple-php-router library through version 5.4.1.7 can be bypassed by remote unauthenticated attackers, allowing access to routes that are supposed to be restricted by client IP. The IpRestrictAccess middleware derives the caller's address from spoofable HTTP headers - X-Forwarded-For, CF-Connecting-IP, and Client-IP - instead of the trusted socket address, so a crafted request can impersonate a whitelisted host or slip past a blacklist. Impact is limited to confidentiality and integrity of the protected routes (moderate severity); no public exploit code has been identified at time of analysis and there is no CISA KEV listing, but exploitation requires only that the target application actually uses this middleware, and no credentials or user interaction are needed.
Unauthenticated information disclosure in the WPMobile.App (wpappninja) WordPress plugin through version 11.83 lets a remote attacker retrieve embedded sensitive data from the plugin without any credentials or user interaction. The underlying issue is a missing authorization check (CWE-862), and per the assessed CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) the impact is limited to a low-magnitude confidentiality leak with no integrity or availability effect, so it is a data-exposure bug rather than a site-takeover path. No public exploit code or active exploitation has been identified at time of analysis, and overall risk is capped by deployment scope: the target must actually run this mobile-app-builder plugin and expose its endpoint to the network.
Pgpool-II deployments that run in watchdog-based high-availability clustering mode can have an arbitrary watchdog node promoted to leader by an unauthenticated network attacker, because the node-authentication algorithm is implemented incorrectly (CWE-303). The flaw is only meaningful on multi-node clusters with use_watchdog enabled and where the watchdog communication interface is reachable by the attacker - standalone or non-watchdog instances are not exposed - so the practical risk is a genuine but deployment-constrained integrity and availability concern rather than a broadly exploitable one. No public exploit code was identified at time of analysis, and no CISA KEV entry or EPSS data was supplied; authentication is not required (CVSS PR:N) and no user interaction is needed (UI:N) once the watchdog precondition is met.
Missing authentication checks in baserCMS (CWE-306) let remote, unauthenticated attackers reach a critical function and read sensitive information without supplying any credentials. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score 5.3), meaning the constraint is impact scope rather than access: only partial confidentiality is lost, and there is no path to modify data or disrupt the site. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so this is a moderate-severity, low-real-risk issue by current signals; the specific affected endpoint and version should be confirmed against JVN14353754.
Client certificate authentication in Pgpool-II can be bypassed by a remote unauthenticated attacker because affected versions fail to properly validate client certificates, allowing access that should require a valid certificate. The flaw carries a vendor CVSS 3.0 base score of 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) and affects multiple 4.x release trains through 4.7.2. Exploitation is conditional: it only matters when the Pgpool-II instance is configured to enforce client TLS certificate authentication; no public exploit was identified at the time of analysis, and it is not confirmed actively exploited (not in CISA KEV).
Arbitrary file deletion in the WEBO MCP WordPress plugin (versions 3.0.18 and earlier) allows authenticated attackers with at least the Author role to delete files on the server, causing availability impact. The vulnerability is a path traversal (CWE-22) that requires a valid content-creator account but no user interaction, and it has a scope change affecting resources outside the plugin. No public exploit code has been identified at time of analysis, and the CVSS base score is 6.8 (Medium).
Arbitrary file deletion in the WordPress plugin Template Kit - Import (versions up to 1.0.16) allows an authenticated attacker with Editor-level privileges to delete files on the hosting filesystem via a path traversal flaw (CWE-22). The vulnerability requires a network-reachable authenticated session (CVSS 3.1 vector AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H, base 6.8) and results in availability and file-integrity impact, with no data disclosure. No public exploit code or active exploitation has been identified at time of analysis.
Arbitrary local file disclosure in the Cato Windows SDP Client (versions before 6.12.6) lets a low-privileged local user coerce the client's Windows service, which runs as Local System, into reading and returning files that user cannot otherwise access, exploiting improper file-path validation combined with missing TLS certificate enforcement (CWE-295). The impact is confidentiality-only with no integrity or availability effect, and the attacker must already hold a foothold on the Windows host, which is why the assessed CVSS 4.0 base score is 6.8 (Medium) with a CVSS 3.1 assessment of AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. No public exploit code or confirmed active exploitation was identified at time of analysis, and upgrading the client to 6.12.6 remediates the issue.
Stored cross-site scripting in the Content Egg plugin for WordPress before 11.9.0 allows an authenticated attacker holding contributor-level access or higher to plant arbitrary web scripts inside posts that the plugin creates under a more privileged author's identity. The root problem is a missing authorization check on the bulk content-import feature: the plugin never verifies that the acting user is permitted to use the import preset they select, and it then switches to that preset author's identity before the post is written, so the injected markup is stored and later executes in the browser session of anyone who views the content - most damagingly an administrator. No public exploit code has been identified at time of analysis, and the vendor has released a fix in version 11.9.0; exploitation requires the site to grant contributor accounts to untrusted users and requires a victim to view the tainted post.
Authenticated cross-site scripting in the Hostinger Reach WordPress plugin before 1.8.3 lets a user with contributor-level access or higher store an unsanitized widget setting that is rendered without escaping in the editor preview, executing arbitrary JavaScript in the session of a higher-privileged user (typically an administrator) who opens the crafted content in the WordPress editor. Exploitation is not remote-unauthenticated: it requires a foothold contributor account plus victim interaction, and the payload fires only inside the editor preview context rather than on the public front end. No public exploit code or KEV-listed active exploitation was identified at time of analysis, and this is best treated as a low-to-moderate real-world priority on multi-author sites where untrusted users can create content. Our independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (6.8 from NVD is derived from a PR:H/S:U vector), reflecting an authenticated, interaction-dependent issue with limited confidentiality and integrity impact rather than an urgent threat.
Stored cross-site scripting in the Audio Player Block WordPress plugin (affected versions 1.1.0 up to but not including 1.6.3) lets a user with the Contributor role or higher save a post whose Audio Player block uses an unvalidated 'javascript:' style URL as its link target, so the payload executes in the browser session of the administrator or editor who later reviews and clicks that link. Exploitation is not automatic and not unauthenticated: it requires an authenticated low-privilege authoring account (Contributor+) and deliberate interaction by a more privileged victim, which is why our independent assessment rates the real-world risk as LOW-to-MEDIUM rather than the 6.8 score published by NVD. There is no confirmed active exploitation (CISA SSVC records Exploitation: none), no public exploit code identified at time of analysis, and a vendor patch is available in 1.6.3.
Stored XSS in EmbedPress before 4.6.7 lets authenticated users with Contributor role or above inject JavaScript through an Elementor widget setting that is not sanitized or escaped before being output into an HTML attribute. Exploitation requires the Elementor page builder to be active and a victim to view the affected content, and no public exploit or active exploitation is known at time of analysis. The independent assessment rates this as CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, reflecting Contributor-level authentication, user interaction, and limited confidentiality and integrity impact.
A kernel-mode out-of-bounds write in the NVIDIA GPU Display Driver for Linux lets a local attacker who already holds high privileges corrupt kernel memory in the driver's kernel mode layer, which the vendor states may lead to code execution, denial of service, privilege escalation, information disclosure and data tampering. The flaw carries a CVSS 3.1 base score of 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is strictly local and requires pre-existing elevated/administrative access on the host; there is no network attack vector and no user interaction is needed. Affected systems are Linux hosts running GeForce, RTX/Quadro/NVS or Tesla driver branches below the fixed releases published in NVIDIA security bulletin 5861, and there is no public exploit identified at time of analysis.
Out-of-bounds read in the firmware component of NVIDIA GPU Display Drivers for Windows and Linux allows a local attacker who already holds high privileges (PR:H, per CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) to read memory beyond intended firmware buffer bounds, most plausibly resulting in memory disclosure or a driver/GPU crash, with the vendor also flagging the potential for code execution, escalation of privileges and data tampering. The CVSS 3.1 base score is 6.7; the attack path is local-only, requires no user interaction, and is gated behind pre-existing high privilege, which materially limits real-world exposure. No public exploit code has been identified for this issue and it is not in CISA KEV, so no public exploit identified at time of analysis.
Code execution, privilege escalation, denial of service, information disclosure, and data tampering are all possible on Windows and Linux hosts running unpatched NVIDIA GPU Display Driver branches, because the kernel-mode layer fails to validate an array index (CWE-129) when processing a crafted GPU command. The flaw is strictly local: per the CVSS vector (AV:L, PR:H, UI:N) and our independent assessment, an attacker must already hold high privileges on the machine and be able to submit work to the GPU kernel driver, and there is no network or unauthenticated path. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so this is a genuine but moderate-priority hardening target for GeForce, RTX/Quadro/NVS, and Tesla deployments; fixed driver builds exist for each affected branch.
An out-of-bounds read in the kernel-mode layer of NVIDIA's GPU Display Driver for Windows and Linux can be triggered by a locally present attacker who already holds high privileges, potentially leading to kernel-context code execution, privilege escalation, denial of service, information disclosure, or data tampering. Exploitation requires local code execution at an elevated privilege level (CVSS vector PR:H) against a vulnerable driver build that is installed and loaded, so there is no remote or unauthenticated path and the practical risk is a defense-in-depth and privilege-boundary concern rather than an initial-access vector; no public exploit has been identified at time of analysis. NVIDIA has published fixed driver builds per product line and branch, and the affected install base spans GeForce, RTX/Quadro/NVS, and Tesla GPUs.
Denial of service in JetBrains YouTrack affects all builds before 2026.2.19197, where a project administrator can craft a notification template that drives uncontrolled resource consumption on the server. The requirement for an authenticated account holding project Admin rights (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, score 6.5) confines realistic exposure to malicious or compromised administrators rather than ordinary or anonymous users, and the impact is limited to availability with no confidentiality or integrity loss. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited, though JetBrains has shipped a vendor patch in 2026.2.19197 and the flaw is tracked in ENISA EUVD as EUVD-2026-90018.
Two cluster-management operations in Kiteworks Core before 9.5.1 fail to validate attacker-supplied file paths, letting an attacker who already holds backend root on one node of a multi-node cluster write files as root onto another node and have them executed there. Exploitation is heavily gated: it is local-only (AV:L), requires pre-existing high privilege (PR:H, backend root), and depends on a software patch being simultaneously pending/staged on the target node to serve as the execution trigger - making this a lateral-movement and privilege-persistence primitive for an already-compromised cluster rather than an initial-access bug. This is a genuine but heavily gated post-compromise flaw, not a top-of-queue emergency; vendor patches are available and no public exploit code has been identified at time of analysis.
Code execution as the gateway service account can be achieved by a trusted party in a Kiteworks Email Protection Gateway cluster that has database replication enabled, via submission of a crafted serialized object that is deserialized without sufficient validation (CWE-502). The flaw is heavily gated: replication is disabled by default, so standard standalone deployments are not exposed, and the attacker must either control a trusted cluster peer or already hold administrative access to the appliance - meaning realistic exploitation is limited to insider abuse, post-compromise lateral movement, or a malicious administrator rather than opportunistic remote attack. All releases below 9.5.1 are affected, a vendor patch (9.5.1) is available, and no public exploit code or confirmed active exploitation was identified at time of analysis; the assessed CVSS is 6.6 (AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H), reflecting the high attack complexity and high privileges required.
Command injection in the optional repository-connector feature of Kiteworks Core allows an authenticated system administrator to append shell commands to a user-supplied path, resulting in code execution as the connector's service account and arbitrary file writes within that account's permissions. Only deployments running Kiteworks Core below 9.5.1 that have licensed and enabled the non-default repository connector are exposed, and successful exploitation additionally requires the appliance to be able to reach an attacker-controlled host over the network, as the injected command must pull or deliver content externally. Rated CVSS 6.6 (AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H); there is no public exploit code identified at time of analysis and the vulnerability is not confirmed actively exploited (no CISA KEV listing), so real-world risk is best characterised as LOW-to-MEDIUM despite the high-integrity/high-availability outcome, given the layered prerequisites of admin privilege, a separately licensed feature, and outbound egress.
Improper numeric conversion in NVIDIA vGPU Virtual GPU Manager for Linux can be triggered from the kernel-mode layer by a local attacker who already holds high privileges, potentially enabling code execution, denial of service, privilege escalation, information disclosure, or data tampering. The assessed CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) shows the dominant constraint is PR:H: an unprivileged guest or local user cannot reach the vulnerable path, and only Linux vGPU Manager deployments are in scope. No public exploit or CISA KEV confirmation is identified at time of analysis; this is a genuine but not urgent issue requiring a privileged local actor.
An out-of-bounds read in the kernel-mode layer of NVIDIA's vGPU Virtual GPU Manager for Linux allows a local, already highly privileged user on the hypervisor host to drive the driver past the bounds of an allocated buffer, with the potential for kernel code execution, privilege escalation, information disclosure, denial of service, or data tampering. The issue is rated CVSS 3.1 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and is confined to Linux hosts running the Virtual GPU Manager in vGPU/VDI or cloud-GPU deployments; no public exploit has been identified at time of analysis. Because the attacker must already be authenticated with high privileges on the host and the attack surface is local-only, this is a moderate-priority, defense-in-depth issue rather than an urgent remote threat.
Improper input validation in NVIDIA GPU Display Driver firmware for Windows and Linux (GeForce, RTX/Quadro/NVS, and Tesla product lines) allows a locally positioned attacker who already holds high privileges to trigger code execution, denial of service, privilege escalation, information disclosure, and data tampering within the GPU firmware handling path. Scoring 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), the flaw is not remotely reachable and cannot be exercised by an unprivileged local user, so it is best characterized as a post-compromise privilege/kernel-boundary escalation rather than an initial-access vector. No public exploit code was identified at time of analysis and there is no indication of confirmed active exploitation; EPSS scoring was not provided in the available intelligence.
Local high-privileged attackers can exploit improper input validation in NVIDIA GPU Display Driver firmware on Windows and Linux to potentially achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering. The assessed CVSS vector (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) confirms local access and high privileges (PR:H), so this is realistically a post-compromise escalation/persistence primitive rather than an initial-access vulnerability. No public exploit identified at time of analysis.