Missing authorization in Arraytics WP Event Solution versions through 4.1.25 allows remote, unauthenticated attackers to make limited unauthorized changes under the plugin's default installation, as reflected by the integrity-only CVSS 5.3 score. The target site must have the vulnerable plugin installed and activated, and no user interaction is required; there is no KEV confirmation or public exploit code identified in the provided data. This is a moderate-to-low priority access-control flaw (CWE-862) rather than a confidentiality or availability compromise.
Unauthenticated arbitrary file upload in the WP-BusinessDirectory WordPress plugin (through version 4.0.2) allows remote attackers to write files with attacker-controlled content to attacker-chosen locations on the web server. Any default installation running the vulnerable plugin with the upload endpoint reachable is exposed without credentials or user interaction, but the plugin vendor notes that this arbitrary write does not translate into code execution on a default server configuration - achieving remote code execution requires a non-default or misconfigured server (for example, writable and executable web paths) or chaining with a second weakness. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); this is a moderate-severity integrity issue that warrants patching but is not a drop-everything emergency on the available signals.
Authenticated MongoDB Server users who hold read access can receive field values in aggregation-framework output that their query did not intend to return, because certain constant values are handled incorrectly during internal query rewriting. Exploitation requires valid credentials with read privileges and a specifically shaped aggregation pipeline; there is no unauthenticated path, no write primitive, and no code execution or denial-of-service impact, so this is best treated as a medium-severity information-disclosure issue despite reference tags that mention RCE and code injection. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the assessed CVSS 3.1 score of 5.3 is driven by low confidentiality impact with no integrity or availability effect.
Insecure default file permissions in the Okta RADIUS Agent Windows installer (versions 2.17.5 up to but not including 2.28.0) grant write and read access to NT SERVICE\ALL SERVICES and CREATOR OWNER on the directories holding the agent configuration, AES encryption key, and logs. Any local service account on the host can therefore read the AES key and the encrypted Okta API token, and could also tamper with configuration or log files; exploitation is strictly local and requires only the ability to run code in a service context, with no admin rights and no user interaction. No public exploit code has been identified at time of analysis and there is no CISA KEV listing, so this remains a low-priority local information-disclosure issue rather than a remote or actively exploited threat.
XBackBone through 3.8.2 performs no ownership check in MediaController::createVanity(), so any authenticated low-privileged user can rewrite the vanity/share code of another user's upload by POSTing to /upload/{id}/vanity with an attacker-chosen id. Because upload ids are sequential and easily enumerated, an attacker can break existing share links (availability) and then claim the vacated vanity code for their own upload (integrity), while no data is disclosed (CVSS 3.1 base 5.3, C:N/I:L/A:L, PR:L, UI:N). Exploitation requires only a valid account and no admin rights or user interaction, and the available intelligence shows no confirmed active exploitation and no public exploit code identified at time of analysis (SSVC Exploitation: none); a fix exists upstream as commit 5e91a2a9859d20e41ee2e2403cfbe673804f6221 / PR #671, but a tagged patched release was not independently confirmed.
Business-logic manipulation in the MacroZheng mall e-commerce platform (mall-portal component) up to version 1.0.3 allows an authenticated storefront user to tamper with the coupon_amount and pay_amount parameters submitted to the /order/generateOrder endpoint, causing the OmsPortalOrderServiceImpl order-generation logic to compute incorrect order totals and payment records. The issue is a CWE-840 business-logic weakness rated 5.3 (CVSS 4.0) by the reporter; the assessed impact is limited to integrity (no confidentiality or availability effect), and exploitation requires a valid authenticated account plus the ability to submit an order - so it is a moderate-priority flaw rather than an urgent one. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no vendor patch was published; notably, the vendor deleted the associated GitHub issue without explanation, which reduces the information available to defenders.
Path traversal in the DeepPavlov Model Download Handler (through version 1.7.0 inclusive) allows an attacker-supplied tar archive to write files outside the intended model directory when the 'untar' extraction routine processes entries containing traversal sequences such as '../'. The flaw is remotely reachable and unauthenticated per the CVSS vector (PR:N), but exploitation is gated by user interaction (UI:P): an operator must initiate a model download or unpack operation that fetches and trusts the malicious archive, which keeps this a moderate, low-priority issue rather than a drive-by compromise. No public exploit code or confirmed active exploitation was identified at time of analysis, the vendor had not responded to the upstream issue report, and no vendor-released patch is confirmed.
Path traversal in jbardin scp.py through 0.16.1 lets a malicious or compromised SCP server write or overwrite files outside the client's intended download directory when a client-side receive operation processes crafted SCP protocol file entries. This affects applications that use scp.py as a client to pull files, most impactfully during recursive gets, and requires the victim to initiate the download from an attacker-controlled endpoint (unauthenticated from the client's perspective, but dependent on passive user interaction). Impact is confined to integrity and availability of local files on the client through arbitrary write/overwrite, with no confidentiality disclosure; there is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, and the issue is best characterized as a moderate defense-in-depth-class weakness rather than an emergency. The vendor released a fixed version, 0.16.2.
WordPress sites running the ThemeGrill User Registration plugin through version 5.2.8 can be queried by unauthenticated remote attackers to retrieve embedded sensitive data, because a missing authorization check (CWE-862) leaves a data-exposing code path reachable without any privilege. Per the assessed CVSS vector (AV:N/AC:L/PR:N/UI:N), no authentication, user interaction, or non-default configuration is required, and the impact is confined to Low confidentiality with no integrity or availability effect - the attacker gains read access to specific exposed data rather than full account or site compromise. Exploitation is limited to sites that have not upgraded past 5.2.8, and there is no public exploit identified at time of analysis and no confirmation of active exploitation (not listed in CISA KEV); this is a routine patch-management item rather than an emergency.
Information disclosure in Active Products Tables for WooCommerce through version 2.1.3 lets unauthenticated remote visitors retrieve embedded sensitive data from rendered product tables. The issue is CWE-201 and is rated CVSS 5.3 with low confidentiality impact only, no integrity or availability impact; WordPress/WooCommerce sites running the affected plugin are exposed. No public exploit was identified at time of analysis, and there is no CISA KEV confirmation of active exploitation.
Missing authorization in the FOX (WooCommerce Currency Switcher) WordPress plugin through version 1.5.4 allows remote attackers to reach plugin functionality that should require privileged access, tampering with data or settings within the plugin's scope. The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N means it is exploitable over the network by unauthenticated attackers with no user interaction, but the consequence is confined to a partial integrity impact - no data disclosure and no availability loss. Severity is moderate (CVSS 5.3), and no public exploit identified at time of analysis; there is no CISA KEV listing for this CVE.
Missing access control checks in ThemeGrill's User Registration plugin for WordPress, versions through 5.2.8, let unauthenticated remote users (CVSS PR:N/UI:N) reach restricted functionality that should require higher privileges, resulting in low-impact disclosure of protected data (C:L, I:N, A:N). The issue is rated moderate at CVSS 5.3 and does not by itself enable account takeover, data modification, or code execution, so its practical value to an attacker is information gathering rather than full compromise. No public exploit code and no confirmed active exploitation (CISA KEV) have been identified at time of analysis, and the specific registration endpoint or feature that is improperly authorized is not named in the available data, so the exact exposure surface remains unscoped pending the vendor advisory.
Missing authorization in the Amelia WordPress booking plugin (TMS Amelia) through version 2.4.10 allows unauthenticated remote attackers to tamper with restricted plugin actions due to insufficient access control checks. This medium-severity flaw (CVSS 5.3, CWE-862) carries only limited integrity impact (I:L) with no effect on confidentiality or availability, and no public exploit or active exploitation has been identified at time of analysis. Affected are WordPress sites running the plugin at version 2.4.10 or earlier; the issue requires no authentication, user interaction, or non-default configuration per the CVSS vector.
Missing authorization in the Pay for Payment for WooCommerce WordPress plugin (all versions through 3.0.1) allows unauthenticated remote attackers to reach functionality that should require an elevated capability, with impact limited to a low-integrity effect. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, base 5.3 Medium), no authentication or user interaction is required, but no data disclosure or denial of service results; the site must have the plugin installed and active at version 3.0.1 or earlier and the vulnerable action must be network-reachable. No confirmed active exploitation and no public exploit code were identified at time of analysis.
An unauthenticated remote attacker can invoke access-controlled functionality in the Fullworks Plugins Quick Paypal Payments WordPress plugin (versions through 6.0.3) because the plugin does not enforce the authorization checks that gate those code paths. Successful exploitation yields a bounded Low integrity impact - an attacker can reach and manipulate plugin/payment-related data but cannot read confidential data or affect availability through this issue alone, which is why this is a moderate-risk, not high-priority, issue per our assessment. No public exploit code was identified at time of analysis and the plugin has no CISA KEV listing, but the endpoint is trivially reachable over the network with no credentials or user interaction required, and no vendor-released fixed version is confirmed in the available data.
Unauthenticated retrieval of embedded sensitive data is possible on WordPress sites running the WPGraphQL plugin through version 2.23.1, because the plugin omits an authorization check on the affected GraphQL operation (CWE-862). Any network-reachable instance exposes the flaw to unauthenticated requesters requiring no privileges and no user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, score 5.3), with impact confined to low confidentiality loss and no integrity or availability effect. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation; the practical exposure is limited to sites that run the plugin and publish their GraphQL endpoint, and this is assessed as a genuine but moderate-priority issue rather than a top-tier emergency.
An open redirect in the Frappe Framework OAuth/social login flow lets a crafted 'state' value control where a user is sent after completing third-party authentication, so a victim who clicks an attacker-supplied login link can be bounced to an attacker-chosen site under the trusted Frappe domain. Only instances that have OAuth social login configured and enabled are affected, and exploitation requires the victim to click the link and finish authenticating at the provider (CVSS 5.1, UI:A, PR:N, S:C, with impact limited to low confidentiality/redirection). No public exploit code or confirmed active exploitation was identified at time of analysis; the issue is modest severity and best handled as routine patch-cycle work, with fixes shipped in Frappe 15.116.0 and 16.29.0.
Stored cross-site scripting in IBM's MCP Context Forge (versions 0.2.0 up to but not including 0.3.1) lets an authenticated user who can create or save a Global Prompt store markup with script-capable event handlers, which then executes in the browser of any other user who views that saved prompt in the MCP Admin UI. Successful exploitation can rewrite the interface, display phishing content, capture keystrokes reachable by the page, and perform actions with the victim's browser session, but it requires a valid account, an enabled Admin UI, and a second user to open the prompt. There is no public exploit identified at time of analysis, no KEV listing, and the vendor-released patch in version 0.3.1 (commit acd1619, PR #337) also flips MCPGATEWAY_UI_ENABLED and MCPGATEWAY_ADMIN_API_ENABLED to false by default, removing the surface entirely for patched deployments.
Reflected cross-site scripting in Omnispace Agora Project before 26.10.0 lets unauthenticated attackers run arbitrary JavaScript in a victim's browser by luring that user into opening a crafted URL whose visioUrl parameter carries an HTML attribute-breakout payload; no login is required (CVSS 4.0 vector PR:N), but the victim must click the link (UI:A), and the injected script executes in the origin of the Agora instance. Tracked as CVE-2026-63156 (CWE-79, CVSS 4.0 base 5.1 Medium; independently assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), the flaw is fixed in version 26.10.0, and no public exploit code was identified at time of analysis.
Server-side request forgery in Shaarli through 0.16.9 lets a logged-in user force the server to issue blind GET requests to loopback, RFC 1918, or link-local cloud-metadata addresses by creating a bookmark whose URL is fetched for thumbnail generation. The practical barrier is authentication (the supplied CVSS 4.0 vector is PR:H; the independent assessment scores it PR:L under CVSS 3.1), and that barrier disappears when the open_shaarli configuration setting is enabled, at which point any unauthenticated visitor can trigger the fetch. Scoring is moderate (base 5.1, confidentiality-only, no integrity or availability impact) and the effect is blind - no response is returned to the attacker - but real-world risk rises sharply on cloud-hosted instances that can reach internal metadata endpoints; no public exploit code and no CISA KEV entry were identified at time of analysis.
Arbitrary file read and write in Citrix UniconOS affects releases before 2607.2 CR and before 2603 LTSR CU2, letting an unauthenticated attacker on the same adjacent network segment read or modify files on the appliance, provided a legitimate user is induced to perform an interaction that triggers the primitive. The vendor rates this medium severity (CVSS 4.0 base 5.1; our independent assessment aligns at CVSS 3.1 5.1 with low confidentiality and integrity impact and no availability impact), and the practical blast radius is constrained by the AV:A adjacency requirement, which keeps the issue off the internet-wide attack surface, plus the mandatory user interaction that prevents fully automated exploitation. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing), so this is a real but non-urgent patching priority - prioritize assets where untrusted parties share a network segment with the appliance.
Stored cross-site scripting in Omnispace Agora Project before 26.10.0 allows an authenticated user who can reach the LDAP/person import feature to persist unsanitized markup into a user profile, which then executes in the browser of any other user who views that profile. The bypass works because the paramsFilter() request-parameter sanitizer handles only flat parameters and does not recurse into two-dimensional (nested) POST arrays, so a payload submitted in that shape survives filtering and is stored verbatim; a flat parameter with the same content would have been neutralized. Exploitation requires an authenticated account with import access plus a second user viewing the poisoned profile (passive user interaction, CVSS 3.1 PR:L/UI:R, scope changed), impact is confined to the victim's browser context with no server-side code execution or data loss, and no public exploit code has been identified at time of analysis.
Stored cross-site scripting in wallabag 2.6.13 through 2.6.14 allows an authenticated user to upload a crafted HTML file (containing script but no anchor elements) via a deliberately failed Pocket HTML, Pocket CSV, or Shaarli import, leaving the payload at a predictable /uploads/import/<user-id>.html path. When another logged-in user visits that URL, the script executes in their wallabag session, granting limited cross-site script execution (assessed CVSS 3.1: AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N; CVSS 4.0 base 5.1, medium severity). No public exploit identified at time of analysis; exploitation requires an authenticated account and victim interaction.
Reflected cross-site scripting (XSS) in QloApps through 1.7.0 allows an attacker to execute arbitrary JavaScript in the browser session of an authenticated back-office administrator by luring them into submitting a crafted request to the AdminHotelFeaturePricesSettings form. The vulnerability is triggered after validation fails, when the feature_price_name and impact_value POST parameters are echoed unescaped in the form template. This medium-severity issue (CVSS 5.1) requires the victim to be an authenticated back-office user with access to the hotel reservation module and to interact with a malicious link or auto-submitting form; no public exploit code has been identified at the time of analysis.
Stored cross-site scripting in the YouMind web application lets an authenticated user abuse the avatar update endpoint by pointing it at an arbitrary URL that hosts an SVG image containing embedded JavaScript, which the platform's CDN then serves unsanitised as image/svg+xml; the payload only executes when a victim navigates directly to that CDN-hosted avatar URL, running in the CDN origin rather than the main YouMind application domain. Rated Medium at CVSS 5.1 (CVSS 4.0: AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N, no subsequent-system impact), the flaw requires a valid account with avatar-update privileges and active victim interaction, and the cross-domain execution context bounds what an attacker can reach; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in bbs-go through 4.4.6 lets an authenticated low-privilege user upload HTML or SVG content by spoofing the multipart Content-Type on POST /api/upload, with the resulting file then served inline from /res. Because the pre-patch upload path trusted the client-declared type rather than sniffing the file's actual bytes, an attacker can plant script-bearing content and socially engineer an administrator into opening the published URL, executing script in the admin's session on the forum's own origin. Exploitation requires a valid account plus victim interaction (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), and there is no anonymous path; no public exploit code or confirmed active exploitation was identified at time of analysis, and upstream fix code is available in commit 5bebf98 (PR #306) though a tagged patched release is not independently confirmed.
Stored cross-site scripting in Omnispace Agora Project before 26.10.0 lets an authenticated user who can create or edit forum categories inject script that executes in the browsers of other users who later view that category. The injection works because a crafted category description containing a double-quote character breaks out of an HTML input value attribute, and the application's HTMLPurifier configuration preserves double-quotes instead of entity-encoding them. Exploitation requires the attacker to hold the relevant forum-category permission (PR:L) and requires a victim to view the affected page (UI:P); there is no public exploit identified at time of analysis, no CISA KEV listing, and impact is confined to the victim's browser session with no server-side compromise. This is a medium-severity issue (CVSS 4.0 base 5.1, CWE-79) and patching to 26.10.0 removes the condition.
Stored cross-site scripting in Omnispace Agora Project versions before 26.10.0 allows an authenticated user with access to the Links module to persist a malicious 'adress' (link address) value that escapes an onclick event-handler attribute, executing script in the browser of any user who later opens the links list and enabling client-side session hijacking. The issue is medium severity (CVSS 4.0 base 5.1; independent assessment vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), with the impact confined to a victim's browser context rather than the server, and it requires an already-authenticated attacker plus a victim who actually loads the links listing. Exploitation is bounded: no public exploit code and no confirmed active exploitation were identified at time of analysis, and a fixed version 26.10.0 has been released.
Stored cross-site scripting in Koillection through 1.8.4 lets any authenticated user upload an HTML file as a Datum attachment through POST /api/data/{id}/file, because the upload path applies no MIME-type or extension restriction; the file is then served as text/html from the public/uploads directory and its JavaScript runs in the session of any other user who opens the attachment. Exploitation is gated by two real prerequisites: the attacker must hold a valid low-privilege account with permission to create or edit a Datum (PR:L in the vendor's CVSS 4.0 vector and in the independent CVSS 3.1 assessment), and a separate victim must actively view the stored payload (UI:P/UI:R), so the realistic severity sits below a naive network-vector reading. Impact is confined to the victim's browser session, with no server-side code execution or data confidentiality/integrity effect on the server; there is no public exploit identified at time of analysis and no CISA KEV listing.
Stored cross-site scripting in Omnispace Agora Project before version 26.10.0 allows authenticated users with file-upload rights to embed HTML/SVG script markup in an uploaded file's name, which is stored unsanitized and later rendered to other users, executing script in their browsers. The payload survives because uploaded-file names arrive through the PHP $_FILES superglobal rather than $_GET or $_POST, so the application's paramFilter never inspects them. Exploitation requires a valid account with upload permission plus a victim who views the affected listing or page (authentication required per the PR:L vector; CVSS 3.1 base 5.1), and no public exploit identified at time of analysis; vendor patch version 26.10.0 resolves the issue.
Stored cross-site scripting in philz1337x/clarity-upscaler allows a low-privileged authenticated user to execute script in another user's browser by manipulating the Description metadata of an Extra Networks card, which is then rendered unescaped by create_html_for_item in modules/ui_extra_networks.py. Every repository version is affected because the project ships as a rolling release whose codebase descends from AUTOMATIC1111/stable-diffusion-webui v1.7.0; the upstream project fixed the same flaw in v1.8.0 (March 1, 2024), but clarity-upscaler's maintainers were notified early via an issue report and have not responded. No public exploit has been identified at time of analysis, and practical exposure is limited to multi-user instances or deployments that load untrusted third-party model files, since a single-user local WebUI where the operator controls all card metadata has little realistic risk; this is assessed as a medium-severity, low-priority issue in practice.
Stored cross-site scripting in Omnispace Agora Project before 26.10.0 allows authenticated users to inject persistent HTML/script markup through the filename of a poll-response attachment, which is later rendered in application pages such as the dashboard controller (CtrlDashboard) and executes in the browser of any user who views the affected content. The vulnerable flow applies paramFilter sanitization to request parameters but that filtering does not cover the $_FILES upload array, so a specially crafted filename survives storage and is emitted unsanitized on render. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), exploitation requires a legitimate low-privileged account plus victim interaction, and impact is confined to the victim's browser session rather than the server; this is a medium-severity, moderate-priority issue, with no public exploit identified at time of analysis and a vendor patch available (26.10.0).
FreeRDP clients on Unix built with PKCS#11 support (3.0.0-beta1 up to but not including 3.32.0) can be crashed by a stack-based buffer overflow in WinPR's NCrypt PKCS#11 provider when an attacker-supplied PKCS#11 token or module presents a key and matching certificate whose CKA_ID is between 55 and 64 bytes long and the victim triggers key enumeration, typically during smart-card authentication. The helper wprintKeyName() hex-encodes the CKA_ID into a fixed 128-byte stack buffer, so a 64-byte ID produces 128 characters with no room for the terminating NUL, and the write is not bounded by the destination size. Impact is confined to a client-side crash with no demonstrated code execution or data disclosure, and exploitability is sharply narrowed by three prerequisites: the non-default PKCS#11 build configuration, physical delivery of a malicious token/module to the victim, and user interaction to start enumeration; no public exploit code or active exploitation has been identified at time of analysis, and this is a low-priority issue despite the CWE-121 classification.
Reflected cross-site scripting in QloApps through 1.7.0 lets an attacker execute JavaScript inside a logged-in back-office administrator's session by inducing that administrator to submit a crafted alias or search value to AdminSearchConfController::processSave() which fails validation and is echoed back unescaped into the admin error output. The vulnerable endpoint is admin-only and the victim must be socially engineered into submitting the crafted request, so this is a moderate-priority issue rather than a remotely wormable one; publicly available proof-of-concept material is referenced in the reporting, and no CISA KEV entry has been reported. Successful exploitation can expose the administrative session (cookies, CSRF tokens) and, because the assessment scores a scope change, pivot into privileged back-office functionality, with low confidentiality and integrity impact.
Reflected cross-site scripting in the QloApps back-office (all versions through 1.7.0, per EUVD QloApps 0 <= 1.7.0) lets an attacker run arbitrary JavaScript inside an authenticated administrator's session by supplying a crafted value to the price parameter of the Additional Facilities (global demand) form, which is re-rendered unescaped after the input fails validation. Exploitation is tightly constrained: the endpoint is not public, so the attacker must already hold a low-privileged authenticated back-office session (PR:L) and must socially engineer a back-office user into submitting the crafted request (UI:P), which is why the independent assessment scores this CVSS 3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (base 5.1 under CVSS 4.0). No public exploit code identified at time of analysis, no confirmed active exploitation, and SSVC records Exploitation: none with Automatable: no and Technical Impact: partial, so real-world urgency is low across every available signal; an upstream fix is available in pull request #1809, but a released patched version was not independently confirmed.
Path traversal in Ivanti Xtraction (all versions before 2026.4) lets a remote authenticated attacker create or modify directories at arbitrary locations on the host file system by supplying crafted path input to a directory-handling feature. The vendor rates it 5.0 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N), reflecting a scope change onto the underlying host with integrity-only impact and no confirmed confidentiality or availability effect; exploitation requires a valid Xtraction account, and no public exploit code has been identified at time of analysis. Upgrading to 2026.4 removes the vulnerable condition.
Denial of service in Microsoft SQL Server 2017, 2019, 2022, and 2025 can be triggered by a privileged database user (CVSS AV:N/PR:H) who supplies externally-controlled format-string input that crashes the engine, causing availability loss (C:N/I:N/A:H). The high-privilege prerequisite (PR:H) means an unauthenticated or low-privileged attacker cannot reach the vulnerable path, so realistic risk is confined to malicious insiders or post-compromise activity on the database host. There is no public exploit identified at time of analysis, CISA SSVC records Exploitation: none and Automatable: no, and vendor patches are available; the EPSS-like signals and low CVSS base of 4.9 reinforce that this is a low-priority hardening item rather than an urgent exposure.
An out-of-bounds read (CWE-125) in Microsoft SQL Server lets an authenticated attacker who already holds high privileges on the database instance disclose in-process memory contents over the network. The flaw is network-reachable (AV:N) and requires no user interaction (UI:N), but the CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N vector and the vendor's 'authorized attacker' wording confirm the high-privilege prerequisite, so anonymous or low-privileged callers cannot reach it; impact is limited to confidentiality (C:H) with no integrity or availability effect, for an overall base score of 4.9. CISA's SSVC decision framework rates exploitation as 'none' and automatable as 'no', so no public exploit code has been identified at time of analysis, and Microsoft has published vendor-released patches that resolve the affected SQL Server 2017, 2019, 2022, and 2025 builds - making this a moderate-severity, low-priority issue despite the ubiquity of the product.
Insufficient driver signature validation in the MEARWService component of Zoho Corp's ManageEngine Malware Protection Plus (all versions before 1.0.64.12) allows an attacker who already holds administrative rights on the endpoint and has local or physical access to load a driver that the service fails to validate. Successful abuse can extend beyond the service into the kernel, yielding high confidentiality, integrity, and availability impact (scope-changed), though the AV:P/PR:H vendor vector and the need for pre-existing admin plus physical presence keep this a low-to-moderate real-world priority. The issue is patched in 1.0.64.12, no public exploit code has been identified, and there is no confirmed active exploitation (not in CISA KEV) at time of analysis.
Second-order SQL injection in the Animated Number Counters WordPress plugin (all versions up to and including 3.0) allows an authenticated user with editor-level capabilities or higher to plant a crafted 'counterid' value that is later concatenated unsanitized into SQL queries, enabling extraction of sensitive data from the WordPress database. Successful exploitation requires the attacker to first store the payload through the plugin's counter-save feature and then trigger the vulnerable read/render path, so the privilege requirement (PR:H) keeps realistic risk moderate rather than critical. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited, although the vulnerability class and the appearance of an upstream code change in the plugin repository make prompt patching advisable for any site granting editor accounts to untrusted users.
Open redirect in Active Directory Federation Services (AD FS) allows an authenticated attacker to craft a federation/redirect URL that sends a victim to an attacker-controlled site while appearing to originate from a trusted AD FS endpoint. Only Windows systems with the AD FS role configured and reachable by users or the internet are affected - Windows Server 2016, 2019, 2022 and 2025 (including Server Core) plus Windows 10 1607 and 1809 builds below their listed fixed build numbers. Exploitation requires an authorized/high-privilege AD FS actor and a victim who interacts with the crafted URL, and the resulting impact is limited to spoofing (low confidentiality and integrity, no availability impact); there is no public exploit identified at time of analysis, KEV status is negative, and the moderate CVSS 4.8 score places this in a low-priority, hardening-class remediation bucket rather than an emergency one.
Incorrect order money calculations in macrozheng mall 1.0.3 (commit dcaa93b) let a backend administrator manipulate the values processed by OmsOrderServiceImpl.updateMoneyInfo through the privileged /order/update/moneyInfo endpoint, producing deliberately wrong order totals. Exploitation requires an authenticated mall-admin session with administrative privileges (CVSS PR:H) plus operator interaction with the order-editing workflow (UI:P), so there is no anonymous or unauthenticated path; impact is confined to integrity of order money fields, with no data disclosure and no availability loss. No public exploit code has been identified at time of analysis and no EPSS scoring was supplied, and the vendor deleted the associated GitHub issue (#1004) without explanation, leaving no official patch guidance.
Code injection in the AutoBackend model-loading path of iMoonLab yolov13 (all versions up to commit 73289949533efac82bb5f72ec19b746618656bd2) allows a local, low-privileged attacker to execute arbitrary code by supplying or tampering with a model artifact whose imgsz, names, or kpt_shape metadata is passed to eval() in ultralytics/nn/autobackend.py. Exploitation is not remote: the attacker must already be able to plant or modify a model file that the victim's pipeline later loads (for example an untrusted downloaded checkpoint, a shared model registry, or a writable model directory), and the CVSS 4.0 vector confirms local access with low privileges (AV:L/PR:L). No public exploit code and no confirmed active exploitation were identified at time of analysis, and the upstream project was notified via GitHub issue #81 but has not responded, so no vendor-released patch exists as of this analysis.
Information disclosure in the Windows Kernel allows an authenticated attacker who can already execute code locally on a vulnerable host to read sensitive data that the kernel fails to properly initialize or sanitize before exposing it (CWE-497). Exploitation is not remotely reachable: the assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N requires local authenticated access plus code execution, and the high attack complexity means the attacker must both reach the specific kernel code path and satisfy timing/memory-state conditions to capture meaningful leaked content rather than zeroes or stale noise. Impact is strictly confidentiality (C:H with I:N/A:N) and stays within the current security context (S:U) rather than escalating privileges; there is no confirmed active exploitation (CISA SSVC Exploitation: none) and no public exploit identified at time of analysis, making this a genuinely low-priority item despite the HIGH confidentiality metric. All supported Windows 10, Windows 11, and Windows Server builds up to the January-class update thresholds listed by EUVD are affected, and vendor patches are available.
Information disclosure in the Windows Win32 kernel subsystem allows an authenticated local attacker holding low-level privileges to read sensitive system data that should be confined to a more privileged control sphere. Unpatched Windows 10, Windows 11 and Windows Server builds are affected, and triggering the flaw requires local interactive or code-execution access plus a hard-to-control precondition, which is why the vendor scores it only 4.7 (AV:L/AC:H/PR:L/UI:N, C:H/I:N/A:N - confidentiality impact only, no integrity or availability loss). No public exploit was identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' and the issue as not automatable, and vendor-released patches are available from Microsoft.
Information disclosure in the Windows Shell lets an attacker who already holds a valid low-privileged local account on a Windows host read sensitive system information that should fall outside that account's access sphere. The CVSS vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms this is not remotely reachable, requires an authenticated local logon, needs no user interaction, and is gated by high attack complexity such as a race condition or a specific system state the attacker must win, so reliability is limited; only confidentiality is affected. No public exploit code and no confirmed active exploitation have been identified at time of analysis (CISA SSVC records Exploitation: none, Automatable: no), and the patch is available from the vendor, making this a low-to-moderate priority issue despite the critical confidentiality rating.
Information disclosure in the Windows Win32 kernel subsystem lets an attacker who already holds a low-privilege local account (or equivalent local code-execution context) on a target host read sensitive kernel-maintained information that they should not be able to see. The vulnerability affects default configurations of a broad set of Windows 10 and Windows 11 releases and Windows Server 2012 through 2025 builds that have not yet been updated to the fixed build levels published in Microsoft's advisory; it is not remotely reachable (CVSS AV:L, PR:L) and the high attack complexity (AC:H) means a specific, attacker-uncontrolled kernel condition must be met before information is disclosed, so success is not guaranteed on every attempt and there is no user-interaction step (UI:N). Impact is confined to confidentiality (C:H, I:N, A:N) with no code execution or system modification, and this is confirmed as not actively exploited (CISA SSVC exploitation: none) with no public exploit identified at time of analysis; no EPSS score was supplied with the source data, and vendor-released patches are available.
Information disclosure in Microsoft Windows Installer allows an authenticated local attacker holding only low privileges to read sensitive system information that should remain outside their control sphere. Affected versions span Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025 including Server Core installations, with a CVSS v3.1 base score of 4.7 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N). Exploitation requires prior local interactive authentication plus a high-complexity, non-deterministic condition; there is no remote vector, no user interaction, no public exploit identified at time of analysis, CISA SSVC rates exploitation as none and automatable as no, and vendor patches are available per the Microsoft advisory.
Information disclosure in the Windows Win32 Kernel Subsystem allows an authenticated local user who can already execute code on the host to read sensitive system information that should remain outside their control. Exploitation is gated by a hard-to-satisfy, attacker-uncontrollable condition (CVSS AC:H), so the flaw is unreliable to trigger, and the impact is confidentiality-only with no integrity or availability loss. There is no CISA KEV listing and no public exploit identified at time of analysis, and Microsoft has shipped fixed builds for every affected Windows client and server branch, making this a genuinely low-priority, moderate-severity issue despite the ubiquity of the platform.
Information disclosure in the Windows NTFS file system driver lets a locally authenticated low-privilege user read sensitive data that leaks out through error messages when the filesystem is driven into a specific fault condition. Only hosts running the affected Windows client and server builds are exposed, and because the assessed vector is AV:L/AC:H/PR:L/UI:N the issue is neither remotely reachable nor anonymous: the attacker must already hold local, authenticated low-privilege access and must hit a precise, difficult-to-control race or system state, with impact confined to confidentiality (C:H/I:N/A:N). Microsoft has shipped fixes through the MSRC update guide, and independent intelligence (CISA SSVC: exploitation none, automatable no, technical impact partial) reports no active exploitation and no public exploit code identified at time of analysis, making this a low-priority hardening item rather than an urgent response.