Authenticated code injection in XWiki Rendering (the xwiki-rendering-xml module, versions before 14.10.2) lets any user who can edit their own user profile - or any other document - close the surrounding HTML macro and inject Groovy or Python script macros that execute with programming rights, granting remote code execution and unrestricted read/write access to all wiki contents. Exploitation requires only a low-privilege, authenticated account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, severity 9.9) and needs no victim interaction beyond the affected page being rendered; the attacker reaches the flaw through rendered output that is embedded in an HTML macro without escaping, with exploitable sinks including the user profile (since XWiki syntax 2.0, demonstrably exploitable from XWiki 3.3 Milestone 1) and the extension point org.xwiki.platform.search.ui.docdoesnotexist (added in XWiki 8.3 Milestone 1). No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, though the vendor advisory documents a detailed reproduction payload and the scope change (S:C) combined with high confidentiality, integrity and availability impact makes this a genuine high-priority issue; vendors have released the fix in XWiki 14.10.2 and 15.0 RC1.
Privilege escalation in Microsoft's Azure Billing service allows unauthenticated, remote attackers to reach full compromise of confidentiality, integrity, and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) by abusing insufficient verification of data authenticity (CWE-345); publicly available exploit code exists, yet CISA's SSVC framework currently records Exploitation as none. Signals therefore conflict and must be weighed carefully: the flaw is rated critical and marked Automatable with Technical Impact total, but EPSS is low at 0.32% (25th percentile) and there is no KEV listing confirming active exploitation. Because Azure Billing is a Microsoft-hosted cloud service, customer-side exposure depends on Microsoft's server-side remediation rather than on local deployment choices, and the description names no specific feature, endpoint, or configuration prerequisite.
Buffer overflow in the TOTOLINK A3002MU router (firmware Hh-B20211125.1046) lets remote attackers corrupt memory by sending a crafted submit-url value to the /boafrm/formWlEncrypt endpoint, with the vendor's CVSS 4.0 vector rated 9.3 and full confidentiality, integrity, and availability impact on both the vulnerable and subsequent systems (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H). The CVSS 4.0 vector specifies PR:N and UI:N, meaning the attack is unauthenticated and requires no user interaction, and publicly available exploit code exists, though no confirmed active exploitation has been reported (no CISA KEV listing). The dominant practical gating factor is exposure of the device's boa-based HTTP management interface, which on most SOHO deployments is reachable only from the LAN, narrowing the threat to local or adjacent-network attackers unless remote administration is enabled.
Authenticated, low-privileged users with access to the Cohesity NetBackup Flex OS management shell can inject crafted argument input into a privileged administrative command and achieve arbitrary code execution as root, gaining unrestricted control of the Flex appliance host and every container it runs. The issue is network-reachable with low attack complexity and requires no user interaction, so the only real prerequisite is a valid low-privileged shell account; scoring 9.4 under CVSS 4.0 (assessed 9.1 under CVSS 3.1), it rates as a genuine high-priority vulnerability. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, so exploitation is currently limited to attackers who already hold credentials.
Authentication bypass in the Mnemosyne sync server (mnemosyne-memory through v3.10.0) lets an unauthenticated, network-positioned attacker forge a JWT bearer token - including one using alg: none or signed with the wrong key - and impersonate any user_id to read that victim's synchronized memory state or push malicious state that corrupts their local database. Rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) with no availability impact, the flaw is remediated in v3.10.1, and a token-forging reproduction is published in the vendor's GHSA-xcw4-53cc-hv32 advisory, meaning publicly available exploit code exists, although no confirmed active exploitation has been reported. Practical exploitability is governed entirely by network exposure: deployments that bind the sync endpoint to localhost, front it with mTLS, or firewall it to trusted clients are not reachable and the vendor explicitly notes the issue 'is not exploitable against an unreachable endpoint,' reducing effective severity to High or Medium for those configurations.
Remote code execution in the AF Companion WordPress plugin before version 2.2.0 lets an authenticated user who holds the plugin's low-privileged 'store-management' role upload arbitrary files, including PHP, through an import feature that performs no file-type validation. Because the uploaded PHP is executable by the web server, an attacker with that mid-tier account - a WooCommerce shop-manager-tier role rather than a full administrator - can place and run code on the host with no user interaction and no non-default configuration required. Publicly available exploit code exists for this issue, and the vendor has released version 2.2.0 to fix it; the practical limiting factor is the authenticated mid-tier role, so sites that never delegate store-management accounts to untrusted parties face materially lower risk.
CareCam CM2507 IP cameras running firmware v251211.1507 store the root account password as a fixed, legacy hash that offers insufficient resistance to offline cracking, so anyone who obtains the firmware image or the on-device password database can potentially recover the root credential. The exposure is not a single-step remote compromise: the independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, because an attacker must first acquire the hash artifact (vendor firmware download, physical/debug filesystem access, or a chained bug) and then crack it offline, and the recovered credential is only useful if it remains valid and is genuinely shared across the firmware line - the advisory says cross-device reuse 'may' occur rather than confirming it. No public exploit code and no confirmed active exploitation have been identified at time of analysis, and the vendor's CVSS 4.0 score of 9.3 overstates real-world risk relative to the assessed vector.
Cleartext storage of wireless network credentials in CM2507 IP cameras running HMT.CM2507 firmware v251211.1507 lets anyone who already holds the device's filesystem read the configured SSID and pre-shared key directly, with no cracking, decryption, or privilege escalation required once that access exists. Reaching the filesystem requires physical possession of the camera, use of an exposed on-board debugging interface, or chaining a separate vulnerability; it is not remotely reachable against a default network-facing configuration. There is no public exploit identified at time of analysis and the issue is not in CISA KEV, and the vendor's CVSS 4.0 score of 9.3 (AV:N) materially overstates real-world risk - our independent assessment scores it CVSS 3.1 AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (approximately 3.7, Low), since impact is confined to disclosure of stored Wi-Fi credentials with no integrity or availability effect on the camera itself.
A pre-authentication heap buffer overflow in IBM MQ Appliance protocol message processing lets a remote, unauthenticated attacker crash the appliance (denial of service) or potentially execute arbitrary code in the context of the MQ appliance firmware. Only network reachability to the appliance's protocol message listener is required - no credentials, session, or user interaction - and the vendor rates this 10.0 with a scope change, while our independent assessment keeps the same base metrics but scores scope as unchanged (S:U) because the overflow occurs in the MQ process itself rather than crossing a security boundary. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV), but the combination of a CVSS 10.0, zero-click pre-auth reachability, and confirmed code-execution potential makes this a genuine top-priority vulnerability rather than a high-CVSS-but-low-real-risk case; an IBM vendor advisory with a patch is available.
Authentication bypass by spoofing in Microsoft Fabric lets unauthenticated network attackers impersonate a trusted identity and elevate privileges, with a scope change indicating the bypass can cross the initial authorization boundary to affect resources or tenants beyond the attacker's own. Microsoft and independent assessment both score this CVSS 3.1 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting full confidentiality, integrity, and availability impact on the affected multi-tenant analytics service. No public exploit code exists and there is no confirmed active exploitation (no CISA KEV listing) at time of analysis, and because Fabric is a Microsoft-operated SaaS, exposure depends on vendor-side remediation rather than customer patching.
Sandbox escape in vm2 through 3.12.0 lets unauthenticated remote attackers execute arbitrary code on the host when the embedding application exposes at least one non-strict (sloppy-mode) host function to the sandbox. By calling such a function with a nullish receiver (`fn()`, `fn.call()`, `Reflect.apply(fn, undefined, [])`, etc.), sandboxed script causes V8 to substitute the host realm’s global object for `this`, which vm2 then wraps and returns as a live proxy of the host global; the attacker can then reach `process` and run commands such as `process.getBuiltinModule('child_process').execSync`. Vendor-released patch: upgrade to 3.12.1; no public exploit identified at time of analysis, but the required pre-condition is common because ordinary JavaScript functions are non-strict by default, and vm2 is deprecated, so unmaintained deployments remain exposed-independent assessment rates this a top-tier priority.
Sandbox escape in vm2 NodeVM before 3.12.1 allows unauthenticated remote attackers to execute arbitrary commands on the host, but only when the application has been configured to allow child_process via builtin:['*'] or an explicit allowlist entry. Exploitation requires the host application to run untrusted JavaScript inside a NodeVM instance and to have this misconfiguration; default configurations that do not allow child_process are not vulnerable. The vendor-supplied CVSS 4.0 vector rates this 10.0, while the independent CVSS 3.1 assessment reflects high attack complexity (AC:H) due to the required misconfiguration. No public exploit code or active exploitation has been identified at time of analysis.
Cross-site request forgery in IBM Common Licensing Agent and ART 9.0.x allows remote attackers to execute unauthorized actions on behalf of an authenticated user, with high integrity impact but no confidentiality or availability impact. Exploitation requires the victim to visit a malicious page while authenticated to the licensing web interface; no public exploit identified at time of analysis. Vendor assigned CVSS 10.0, but independent analysis assesses a more moderate risk due to the UI:R and S:U characteristics typical of CSRF.
SQL injection in the pg_partman PostgreSQL extension before version 5.5.0 lets an authenticated database role that holds the documented partman_user INSERT/UPDATE privileges on the part_config table store SQL text in the writable time_encoder column instead of a legitimate function name. When the pg_partman_bgw background worker next creates a child partition for a text- or UUID-keyed set, that stored SQL is interpolated into a dynamically executed SELECT and runs with the privileges of pg_partman_bgw.role, which the pre-5.5.0 documentation defaults to a superuser such as 'postgres'; because the payload persists in the configuration row, elevated access can be re-established on subsequent maintenance ticks and can lead to database-wide compromise and operating-system command execution as the PostgreSQL service account. The issue is rated CVSS 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) and is fixed in 5.5.0; no public exploit identified at time of analysis, and exploitation requires an attacker to already possess partman_user grants plus a deployment where the background worker runs as a superuser.
Privilege escalation in Azure Database for PostgreSQL allows an authenticated attacker with low privileges to elevate privileges over the network, potentially achieving full control over database resources. With a critical CVSS score of 9.9 due to scope change and high impact, the flaw requires a valid low-privileged identity to exploit; no public exploit code has been identified at time of analysis.
Sandbox escape in vm2 3.12.0 and earlier allows unauthenticated remote attackers who can supply JavaScript to an application embedding vm2's VM or NodeVM to break out of the sandbox and execute arbitrary code on the host, provided the embedder exposes at least one host API returning a host-realm (native) Promise whose rejection value is host-pivotable - the advisory cites a host process object as the example. The flaw is an incomplete rejection-sanitization failure in lib/bridge.js: the sandbox-side Symbol.species and .then neutralization is installed only on the sandbox intrinsic Promise.prototype, so it never applies to host Promises, letting sandboxed code overwrite p.constructor[Symbol.species] and call p.then() without an onRejected handler, after which V8's internal Thrower re-throws the raw host rejection value into an attacker-controlled resolve/reject closure, bypassing handleException and hostPromiseSanitizeReject and yielding an unsanitized, fully functional bridge proxy of the host object. No public exploit identified at time of analysis, but the CVSS 4.0 base score is 10.0 and the issue is fixed in 3.12.1.
SQL injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker to execute arbitrary SQL commands against the appliance's back-end database, and the vendor rates it Critical (9.9) on a scope-changed vector while our independent assessment retains high impact on confidentiality, integrity, and availability on a scope-unchanged basis. Exploitation requires valid low-privilege credentials to the Guardium web/management console (CVSS PR:L) with no user interaction (UI:N), so a standard operator or auditor-level account is enough to reach the vulnerable query path, and Guardium is normally deployed on internal management networks rather than exposed to the internet, which meaningfully constrains realistic exposure. No public exploit code exists and there is no evidence of active exploitation at time of analysis (no CISA KEV listing), and a vendor patch is available.
Unauthenticated remote attackers can bypass security restrictions in IBM Guardium Data Protection 12.2 through the ChangeTrackerServlet, which is missing authentication (CWE-306). The vendor CVSS 3.1 vector rates this 9.9 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:L), and the independent assessment preserves the unauthenticated network-reachable nature while treating scope as unchanged; no public exploit was identified at time of analysis and there is no CISA KEV confirmation. IBM has published patch information, so affected deployments should be updated and have network access to the management web tier restricted until patched.
Missing authentication in the LoadBalancerServlet of IBM Guardium Data Protection 12.2 allows unauthenticated, network-reachable attackers to invoke privileged load-balancer operations, compromising the integrity and availability of the affected deployment. The flaw is rated 9.9 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N) and maps to CWE-306, so no credentials or user interaction are required; the practical barrier is that the Guardium management interface exposing the servlet must be reachable across the network, and such interfaces are usually confined to segmented internal networks. Impact is concentrated on load-balancer control operations rather than broad data exposure (confidentiality impact is low), and no public exploit identified at time of analysis; the issue is not listed in CISA KEV. IBM has published a patched release through its support advisory.
Cross-workspace impersonation and complete authorization bypass in kcp (kcp-dev) before 0.31.4 and 0.32.x before 0.32.2 let any authenticated tenant forge Kubernetes-style identity headers that the shard accepts as trusted authentication assertions. Because the front-proxy and the server localproxy forward inbound X-Remote-User, X-Remote-Group, and X-Remote-Extra-* headers without clearing them, an attacker with valid credentials for any single workspace can supply values such as X-Remote-Group: system:masters, authorization.kcp.io/warrant, authentication.kcp.io/scopes, or a group used for per-workspace required-group gating to read, write, or delete resources, secrets, RBAC data, APIExports, APIBindings, and LogicalClusters across the installation. Exploitation requires authenticated access (CVSS vector PR:L, AV:N, no UI), yields changed scope per the vendor vector (CVSS 9.9), and no public exploit code or confirmed active exploitation was identified at time of analysis; fixed releases 0.31.4 and 0.32.2 are published.
Privilege escalation and cross-tenant data disclosure in WACRM 0.7.0 and earlier allow any authenticated user - a read-only 'viewer' is sufficient - to self-promote to account owner, relocate their profile into another tenant's account, and then read or modify that tenant's resources, or to directly pull another tenant's AI knowledge-base chunks, all through the default Supabase/PostgREST REST API. The flaw is two-fold: an overly permissive row-level security policy on the profiles table that lets users edit their own account_role and account_id columns, and two SECURITY DEFINER RPCs (match_ai_knowledge_fts, match_ai_knowledge_semantic) that are GRANTed to the authenticated role and trust a caller-supplied p_account_id without any is_account_member check. Rated CVSS 3.1 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, CWE-639); exploitation requires a valid low-privilege JWT but no admin rights, no user interaction, and no non-default configuration, and no public exploit identified at time of analysis - practical risk is tempered mainly by how rarely this self-hosted template is deployed.
Unauthenticated remote code execution in LMDeploy 0.9.2 through 0.15.x lets any attacker who can reach a DistServe/PD-disaggregation deployment's POST /distserve/p2p_connect endpoint run arbitrary code with the privileges of the LMDeploy serving process. The endpoint accepts an attacker-supplied ZeroMQ peer address; the engine connects to it and deserializes the reply with PyZMQ's recv_pyobj(), which is backed by Python pickle and therefore executes code during object reconstruction, before any type or schema check can run. Rated CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-502); exploitation is unauthenticated only in the default configuration where the operator has not enabled API-key authentication, and no public exploit code has been identified at time of analysis. A vendor patch is available in LMDeploy 0.16.0, which replaces the pickle-based ZeroMQ protocol with JSON plus Pydantic validation.
Out-of-bounds heap write in FluidSynth's command handler lets an attacker supply an out-of-range channel argument to the pitch_bend_range command, which is written through the selected synth channel without bounds checking. The worst-case exposure is unauthenticated remote code execution or denial of service (CVSS 3.1 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) when FluidSynth runs as a TCP command server via new_fluid_server() or 'fluidsynth -s'; absent that network mode, the flaw is only locally reachable through malicious commands fed to the interactive shell on standard input, and applications that embed the library without the shell, command handler, or TCP server are unaffected. The vendor has released a fix in FluidSynth 2.5.6 (spanning affected releases from 1.1.2); no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the appliance interface that processes serialized input run arbitrary code in the context of the affected service, yielding full loss of confidentiality, integrity and availability (CVSS 9.8, AV:N/AC:L/PR:N/UI:N). The root cause is insecure deserialization of untrusted data (CWE-502), and because the assessed vector carries PR:N and UI:N, no credentials or user interaction are needed, so real-world exposure is determined almost entirely by network reachability to the Guardium management/collector segment rather than by the public internet. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; IBM has published a vendor patch, which keeps this a top-tier remediation priority rather than an actively exploited emergency.
Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2 allows a network attacker who can reach TCP port 16017 to submit crafted serialized messages that are insecurely deserialized and used for attacker-controlled reflective method dispatch, potentially resulting in unintended code execution on the Guardium appliance with high confidentiality, integrity, and availability impact. The vendor-reported base score is 9.8 (AV:N/AC:L/PR:N/UI:N); our independent assessment keeps the unauthenticated, no-user-interaction profile but applies AC:H, because the practical gating factor is whether an attacker has a network path to the non-standard CAS port rather than any product configuration toggle. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV); IBM has published a vendor patch advisory, and this should be treated as a genuinely high-priority issue for any deployment where port 16017 is reachable from untrusted networks, while remaining lower-risk in segmented or hardened environments where the listener is internal-only.
Heap buffer underflow in IBM MQ for HPE NonStop 8.1.0 through 8.1.0.40 allows an authenticated remote attacker to crash or destabilize the queue manager, and potentially to execute arbitrary code, by submitting a crafted multi-segment message that is reassembled during processing. The dependable outcome is denial of service: reliable code execution is not confirmed, and exploitation requires valid low-privilege credentials (PR:L) plus access to a channel or queue that accepts submitted messages. There is no public exploit identified at time of analysis and the flaw has not been added to CISA KEV; urgency is real but constrained because only the specialized HPE NonStop build is affected, not general IBM MQ distributions.
Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based access controls guarding the Guardium management interface and reach that interface without satisfying the network allowlist. IBM rates the flaw 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but our independent assessment scores it materially lower (C:L/I:N/A:N) because the bypass defeats the IP filter rather than the interface's own authentication, so real impact hinges on what the management interface permits once reached and whether it applies its own credentials. No public exploit code has been identified at time of analysis, and exploitation is only possible where the management interface is network-reachable and administrators treat IP allowlisting as the primary or sole control; deployments whose management plane is fully segmented behind a firewall with no attacker path are not exposed.
Unauthenticated SQL injection in IBM Guardium Data Protection 12.2 lets a remote attacker submit crafted input that is concatenated into a SQL statement without proper neutralization, enabling execution of arbitrary SQL commands with full confidentiality, integrity, and availability impact (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N). Per the assessed vector, no credentials and no user interaction are required, so any party who can reach the affected interface over the network can attempt exploitation; the practical barrier is deployment exposure, since Guardium management interfaces are normally placed on segmented internal or security-monitoring networks rather than being internet-facing. There is no public exploit code identified at time of analysis and the vulnerability is not listed in CISA KEV, but successful exploitation could allow reading or altering the data Guardium is entrusted to protect, which makes internal-network reachability the key risk factor. The specific injectable endpoint or parameter is not named in the available description, and if the flaw is second-order rather than first-order, real-world exploitation would require more steps than the AC:L rating implies. No EPSS score was supplied with the source data.
Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL that is stored and later processed by the generateInsertQuery logic in change-tracker-data.sql, potentially compromising confidentiality, integrity, and availability. The supplied CVSS is 9.8 (AV:N/AC:L/PR:N/UI:N), but our independent assessment raises attack complexity to High because the second-order path requires both initial acceptance/storage of the payload and a subsequent internal operation that builds the INSERT query; this two-stage requirement is the main practical constraint. No public exploit identified at time of analysis or KEV-confirmed active exploitation is present in the supplied data, and IBM has published vendor patch information at its support advisory.
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds heap write, allowing a remote attacker to crash the queue manager and, potentially, execute arbitrary code in the MQ process. The issue affects IBM MQ 9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / up to 9.3.5.1 CD, 9.4.0.0-9.4.0.25 LTS / up to 9.4.5.1 CD, and 10.0.0.0, with the CVSS base of 9.8 reflecting a network-reachable, unauthenticated worst case, though our assessed vector raises attack complexity to High (AC:H) because the channel must be explicitly configured with compression and reachable by the attacker. Denial of service is the readily achievable outcome, while reliable code execution requires defeating the process's memory protections; no public exploit code has been identified at time of analysis, SSVC rates exploitation as none, and EPSS is low at 0.37% (31st percentile).
SQL injection and cross-tenant data exposure flaws in HCL BigFix Service Management allow an attacker who can reach the application's request-handling layer to inject database commands and to manipulate tenant/organization scoping values so that another organization's profile data and PII can be read. The vendor rates this 9.8 Critical using a vector that encodes PR:N, but the advisory text itself states the attack requires an authenticated attacker - an internal contradiction; our independent assessment resolves it as AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, so exploitability hinges on whether a valid account is genuinely required, and the cross-tenant half of the impact only applies to multi-tenant deployments hosting multiple organizations. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no fix version was disclosed in the provided data; organizations should treat the vendor KB article as the authoritative source for patched builds.
Unauthenticated remote code execution affects the Interchange e-commerce platform (the interchange/interchange project) through its admin 'quick question' page, where attacker-supplied yes/no parameters flow into a reparsed [calc] template block and injected Perl is evaluated server-side. The flaw is reachable without authentication in default installations, as confirmed by the upstream fix adding a previously absent [if-mm super] superuser gate, and SSVC rates it Automatable with total technical impact; however, injected code executes inside Interchange's Safe compartment, so unrestricted, full-impact code execution additionally requires the non-default AllowGlobal directive to be enabled on the catalog being accessed. The vendor rates this 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) while our independent assessment rates it AC:H given the sandbox constraint; no public exploit code and no confirmed active exploitation were identified at time of analysis, and a vendor patch/advisory is available.
Synology DiskStation Manager (DSM) login logic uses insufficiently random values, letting remote unauthenticated attackers (CVSS PR:N) read or write arbitrary files and mount denial-of-service attacks on NAS devices running DSM before 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4, and 7.4-90075. Synology rates the flaw 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), while independent assessment keeps the same impact but raises attack complexity to High, since the attacker must successfully predict or reproduce the weakly-random login value, potentially requiring repeated attempts or offline computation. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the unaudited attack surface (DSM's web login on typical management ports) and full CIA impact make prompt patching the priority for any internet-reachable instance.
Improper output encoding in the SCGI service of Synology DiskStation Manager (DSM) lets unauthenticated remote attackers read or write arbitrary files on the appliance and mount denial-of-service attacks against it. Every DSM build prior to 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4, or 7.4-90075 is affected, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, 9.8) confirms no credentials, user interaction, or non-default settings are needed - the only real precondition is network reachability to the SCGI interface, which makes internet-facing NAS units the highest-risk deployments while firewall/VPN-isolated devices carry substantially lower risk. No public exploit code has been identified at the time of analysis and the issue is not in CISA KEV, but the combination of full confidentiality, integrity, and availability impact with no authentication requirement makes rapid patching a priority.
Stored cross-site scripting in IBM Guardium Data Protection 12.2 lets an authenticated user of the web management console inject script that executes in a second user's browser when the affected page is rendered. The vendor scores this 9.6 (scope change, high confidentiality and integrity impact), but the independent assessment scores it CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, treating the impact as confined to the victim's browser/session context rather than the underlying appliance operating system; the record's 'RCE' tag and the vendor's UI:N rating overstate what a CWE-79 input-neutralization flaw realistically delivers. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and IBM has published a patch advisory. This is a high-CVSS-but-lower-real-risk issue where the vendor scoring and tags overstate severity.
Unauthenticated attackers who can reach the PD Master's /pd_register WebSocket endpoint can register arbitrary nodes in LightLLM through 1.2.0, causing full user prompts routed to the attacker's socket to be disclosed, disrupting service by displacing legitimate nodes, and forcing the PD Master to issue requests toward internal network addresses. The root cause is CWE-306 (missing authentication for a critical function): the registration handler accepts crafted JSON without validating the peer address, and the CVSS 4.0 score of 9.3 with PR:N/UI:N reflects high confidentiality, integrity, and availability impact requiring no credentials or user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis, and practical exposure is limited to multi-node prefill-decode (PD) disaggregated deployments where the endpoint is network-reachable; single-node or properly firewalled deployments are not exposed.
Root shell compromise of NetBackup Flex OS appliances is possible for authenticated, low-privileged users who have access to the NetBackup Flex OS management shell. By supplying a specially formed access credential, such a user can bypass the cryptographic signature verification step of a privileged support command (CWE-347), gaining unrestricted root control over the Flex appliance host and all hosted containers, with complete confidentiality, integrity, and availability impact. The vendor CVSS 4.0 score is 9.4 (PR:L, no user interaction); supplied intelligence does not indicate CISA KEV active exploitation or publicly available exploit code, so no public exploit identified at time of analysis.
CordysCRM before 1.7.2 exposes its SSE notification endpoints anonymously, allowing a remote unauthenticated attacker who can reach the backend HTTP interface to read another user's workflow events, approval requests, mentions, and alerts, inject SYSTEM_HEARTBEAT messages into that user's stream, or close that user's SSE channel. The flaw is missing authentication (CWE-306) in the Shiro public-path whitelist and the controller's trust in a caller-supplied userId; the provided source advisory CVSS 4.0 score is 9.3, while the independent CVSS 3.1 assessment is 8.6 because confidentiality impact is high but integrity and availability impact are limited to a selected user's notification stream. No CISA KEV entry or public exploit code was identified at time of analysis, but exploitation requires only network reachability and a target userId.
Unauthenticated HTTP requests to the OpenShift console's /api/devfile/ and /api/devfile/samples/ endpoints let remote attackers trigger server-side request forgery from the console pod into internal cluster services and exhaust console memory through repeated large requests lacking a Content-Length header. Red Hat rates this 9.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L); our assessment agrees on the unauthenticated, network-reachable SSRF crossing a trust boundary but lowers confidentiality to C:L because only partial internal responses are reflected, producing a lower composite score. Clusters that expose the web console to untrusted networks are most at risk; no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV).
TLS certificate validation bypass in AnyIO (pip/anyio) versions before 4.14.2 lets an attacker who already holds an on-path man-in-the-middle position impersonate a server named with a non-ASCII internationalized domain name. AnyIO's TLSStream.wrap() encoded the target host name with IDNA 2003 (via the Python standard library) instead of IDNA 2008 before matching it against the peer certificate, so a host like 'faß.de' was compared against the certificate for 'fass.de' - an attacker can obtain a legitimately CA-issued certificate for that wrong domain and have it validate on the client. Exploitation requires all three of: an application calling connect_tcp(tls=True) or TLSStream.wrap() with an affected unicode host name, a pre-existing connection hijack/redirect the vulnerability does not itself provide, and attacker acquisition of a valid certificate for the IDNA 2003-encoded name; ASCII-only host names are unaffected. No public exploit code has been identified at time of analysis, and patched version 4.14.2 is available.
Unauthenticated attackers can reset the password of any Cotonti account, including administrator accounts, because password-recovery validation tokens in Cotonti through 1.0.0 are derived from md5(microtime()) rather than a cryptographically secure random source, leaving roughly one million predictable candidate values per second. Exploitation requires the attacker to trigger the recovery flow for a target account, read the server's Date header to bootstrap the microtime() timing window, then precompute and probe candidate tokens against the passrecover endpoint before the seed drifts - a timing-constrained but fully unauthenticated attack (assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H; CVSS 4.0 base 9.2). No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; any endpoint rate-limiting or short token lifetime further constrains the probing step, so this is a genuine high-priority flaw rather than a CVSS-inflation case.
Unauthenticated remote code execution affects HGiga's OAKlouds Custom Page module in the 2.0, 3.0 and 4.0 lines at builds below 26, where an attacker who can reach the Custom Page endpoint can submit malicious serialized content and have it deserialized into arbitrary code running with the web service's privileges. The CVSS 4.0 score of 9.3 reflects the worst case for an unauthenticated network attacker (PR:N, UI:N, AT:N, high confidentiality, integrity and availability impact on the vulnerable system), and the practical limiter is exposure - whether the affected instance is reachable from untrusted networks - rather than any technical precondition. No public exploit code has been identified at time of analysis and the flaw is not currently listed as confirmed actively exploited (CISA KEV), but the low attack complexity, unauthenticated access and full-system impact make this a genuinely high-priority issue for any organization running the affected builds, and a vendor fix is available.
Data disclosure and permanent record deletion in Mongoid can be triggered by an unauthenticated remote attacker when an application passes an externally supplied field name to certain in-memory query methods for embedded documents, exploiting an unsafe reflection weakness (CWE-470). The vendor CVSS 4.0 base score of 9.2 reflects the network vector and high impact across confidentiality, integrity, and availability, though the attack requires a developer-dependent data flow (AT:P) where untrusted input reaches a field name parameter. No public exploit code or active exploitation has been identified at time of analysis, and affected/fixed versions remain unconfirmed due to an unbounded CPE (mongoid:*).
Authentication bypass in IBM Sterling File Gateway lets a remote, unauthenticated attacker forge or inject an unvalidated SSO header and obtain a fully authenticated session on the gateway's web interface. The flaw is rated CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) because no credentials, privileges, or user interaction are required, and a successful bypass yields high confidentiality and integrity impact over file-transfer workflows. No public exploit identified at time of analysis, but exploitation is trivial for anyone who can reach an SSO-header-enabled deployment, so internet-exposed instances should be treated as high priority; IBM has published a fix advisory.
SQL injection in IBM Guardium Data Protection 12.2 allows a remote attacker who already holds a valid low-privilege session to execute arbitrary SQL commands against the appliance's backend database by supplying crafted input to a request parameter that is not properly neutralized before being used in a SQL statement. IBM rates this CVSS 9.1, driven by a high confidentiality impact on a platform whose core function is monitoring and protecting sensitive databases, though exploitation prerequisites are meaningful: the attacker must be authenticated (CVSS vector PR:L), needs network reach to the management interface, and only version 12.2 is named as affected. There is no CISA KEV listing and no public exploit code identified at time of analysis, so risk is concentrated in environments where low-privilege credentials can be obtained or are broadly distributed, and a vendor patch is available.
Ultraviolet CoCoS through version 0.8.2 contains a session-misbinding flaw in the intra-handshake attested TLS (aTLS) verification path for Intel TDX: the verifier fails to copy the expected current-session freshness value into the TDX quote-body policy before quote validation, so any structurally valid TDX QuoteV4 Evidence is accepted without checking that its REPORT_DATA field matches the reportData expected for that session. An unauthenticated remote counterparty (CVSS vector AV:N/PR:N) that can supply or relay such a quote - acting as the attesting party or replaying a previously captured or foreign quote - can therefore cause a relying party to release application data bound to an unintended attestation context, giving high confidentiality and integrity impact. No public exploit code and no confirmed in-the-wild exploitation were identified at time of analysis, and the vendor's 9.1 score (AV:N/AC:L) slightly overstates ease of exploitation versus our assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, since a valid TDX quote and use of the affected TDX aTLS branch are prerequisites. The issue is fixed in version 0.9.0.
An attestation-freshness and origin-validation failure in the aTLS AMD SEV-SNP verification path of Cocos AI (Ultraviolet) affects versions up to and including 0.8.2: when a relying party invokes the intra-handshake verification path with no expected reportData value (nil, empty, or omitted), the SEV-SNP policy ReportData is left unset and the verifier will accept unrelated or stale Evidence that is not bound to the current TLS connection. An attacker who possesses a valid but foreign or replayed SEV-SNP attestation blob can therefore induce a trusting party to accept an unintended attestation context, undermining the core trust guarantee of the confidential-computing platform and potentially enabling both integrity and confidentiality compromise in any workflow where aTLS output drives a trust or authorization decision. Exploitation is unauthenticated at the network layer (CVSS PR:N) but constrained by high attack complexity and specific prerequisites - the caller must omit the expected reportData, and only SEV-SNP aTLS deployments up to 0.8.2 are exposed; no public exploit code or confirmed active exploitation has been identified at time of analysis. The issue is fixed in version 0.9.0.
An attacker-supplied Truevision TGA image can force the Perl Imager module (versions before 1.036) to kill the entire hosting process: a colour map length of 32768 or more is read into a signed short, becomes negative, is cast to size_t, and turned into a near-SIZE_MAX allocation request that fails and makes Imager's allocator call exit(3). Exploitation requires only that the application pass untrusted image bytes to Imager->read() with TGA handling (explicit type 'tga' or auto-detection) - the CVSS vector is PR:N, so no authentication is needed, and the exit(3) is uncatchable, meaning Perl eval and Try::Tiny handlers cannot trap it and a single malicious file terminates the worker, request handler, or CLI process. Publicly available exploit code exists per the SSVC assessment (exploitation: poc), but the input does not record confirmed active exploitation (CISA KEV); the vendor CVSS of 9.1 (C:H/I:N/A:H) is overstated, since the independently assessed vector is C:N/I:N/A:H - this is a pure denial-of-service condition with no code execution, memory corruption, or data disclosure.
Script injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker with low-privileged web credentials to inject unsanitized input into web-generated pages, which then executes as JavaScript when another user views the affected page. The independent assessment treats this as a client-side cross-site scripting issue requiring victim interaction, with low confidentiality and integrity impact in the browser/session context and no availability impact, rather than host operating system code execution despite the vendor description's 'arbitrary code' phrasing. No public exploit was identified at time of analysis, and a vendor patch is available from IBM.
Sustained brute-force attacks against the HCL BigFix Service Management v27 login interface are possible because the product fails to adequately lock out or throttle repeated failed authentication attempts, letting remote unauthenticated attackers (CVSS PR:N/UI:N) make unlimited credential guesses that, if successful, grant full access as scored (C:H/I:H/A:H). The vendor scores this 9.8, but our independent assessment uses AC:H because the missing lockout does not itself grant access - the attacker must still obtain or guess valid credentials, so real-world impact hinges on password strength, MFA, and whether the login page is internet-exposed. Competing signals frame this as a high-severity design weakness with low current urgency: EPSS is 0.25% (17th percentile), SSVC records Exploitation: none with partial technical impact, no CISA KEV listing exists, and no public exploit code has been identified at time of analysis.