Authentication Bypass

Remote code execution in Windows RPC Runtime (CVSS 8.8) arises from a type confusion flaw (CWE-843) that an unauthenticated attacker can trigger over the network, though exploitation requires user interaction-such as connecting to an attacker-controlled RPC endpoint or processing a malicious server response. No public exploit code has been identified at time of analysis, but the high impact and unauthenticated nature make this a high-priority issue for patching.

Local privilege escalation in Windows Group Policy allows an authenticated, low-privileged attacker who already has interactive or code-execution access on a Windows host to elevate privileges to a higher-integrity context. The flaw is an access-control weakness (CWE-862) in how a privileged Group Policy operation is authorized, requiring no user interaction (UI:N) and low attack complexity (AC:L) once a foothold exists, which makes it most impactful on shared multi-user systems such as terminal/RDS servers, VDI hosts, and domain-joined endpoints where untrusted users hold accounts. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Microsoft is credited as the reporting vendor.

Command permission gate bypass in Mistral Vibe before 2.25.4 lets input processed by the agent cause arbitrary shell command execution with the privileges of the agent's terminal session, while the allowlist gate reports that only a trailing, allowlisted command was run. The bypass hides a command substitution inside a single-quoted variable value that the agent's tree-sitter-bash static parser cannot see, then triggers execution at runtime through bash's ${var@P} prompt-transform operator; the vendor has fixed the misclassification in 2.25.4. Exploitation is conditional rather than opportunistic - an operator must be running an agent session over attacker-controlled content (prompt injection in untrusted files, repositories, web content, or tool output) and a bash shell with promptvars enabled must be in use - and no public exploit code and no confirmed active exploitation were identified at time of analysis.

Permission validation bypass in Mistral Vibe versions before 2.25.5 allows an attacker who can get crafted text in front of the agent to have arbitrary shell commands executed under the user's own privileges, despite the tool's command allowlist. The flaw is a parser disagreement: tree-sitter-bash truncates a backslash-newline continuation and sees only an allowlisted prefix such as 'cd', while bash joins the lines and runs a materially different command (for example a curl request), so resolve_permission grants ALWAYS for the benign-looking prefix and the hidden command executes. Exploitation requires the allowlist / auto-approval mechanism to be in use and requires the user to direct the agent at malicious input (UI:P per the CVSS 4.0 vector, UI:R in the CVSS 3.1 assessment), so it is not fully autonomous, and no public exploit code or confirmed active exploitation was identified at time of analysis. Vendor-released patch: 2.25.5.

Incorrect authorization in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source lets remote, unauthenticated attackers bypass security controls to gain unauthorized read access plus limited write access, with no user interaction required. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N (base 7.2) confirms the attacker needs no credentials and only network reachability to an affected, unpatched instance - typically an internet-facing storefront, REST/GraphQL API, or admin interface - while the changed scope (S:C) indicates the bypass can reach resources outside the vulnerable component's own security boundary. Impact is bounded rather than catastrophic: confidentiality and integrity are Low and availability is None, so this is a security-feature/authorization bypass rather than full administrative takeover or data destruction, and no public exploit code has been identified at time of analysis, making this a genuine but mid-tier priority.

Incorrect authorization checks in Adobe Commerce, Adobe Commerce B2B, and Magento Open Source allow a low-privileged authenticated user - such as a registered customer or a limited back-office/B2B account - to bypass security controls and gain unauthorized read and write access, with a limited impact on availability (CVSS 8.3, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L). No administrative role and no victim user interaction are required, so any internet-facing storefront or admin surface exposing the vulnerable authorization check is in scope; the practical gating factor is possession of some valid credential, and stores permitting open customer or B2B self-registration lower that bar considerably. At time of analysis there is no CISA KEV listing and no public exploit identified, and no EPSS score was supplied; the root cause is classified as CWE-863 (Incorrect Authorization) and Adobe has published advisory APSB26-153, which should be treated as the authoritative source for affected and fixed versions.

Remote, low-complexity code execution is possible in Adobe Commerce, Adobe Commerce B2B and Magento Open Source through an incorrect authorization flaw (CWE-863) rated CVSS 9.8, allowing an attacker to act with the privileges of the current request context and escalate to arbitrary code execution without user interaction. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) describes network-reachable exploitation requiring no prior privileges, which is the strongest signal in the available data. No public exploit code and no CISA KEV entry were identified at time of analysis, and Adobe's only provided reference is advisory APSB26-153; defenders should note Adobe's wording about 'the context of the current user,' which may indicate an existing session or request context is required even though the vector claims PR:N.

Stored cross-site scripting in Shopware 6.7 lets remote attackers upload attacker-controlled HTML that Shopware serves as text/html without effective security headers, so when an administrator views the file the attacker can exfiltrate the administrator's authentication token. The stolen token opens the Shopware Administration API, and if that administrator can manage extensions the attacker can install a malicious plugin to achieve arbitrary PHP code execution on the underlying host. No public exploit code was identified at time of analysis; EPSS is 0.28% (19th percentile), CVSS 3.1 is 8.1 (AV:N/AC:L/PR:N/UI:R) and exploitation requires administrator file viewing plus, for code execution, extension-management privileges.

Unauthenticated remote attackers can bypass the security controls that are supposed to be enforced during session establishment with an OpenText EnCase SAFE Agent, allowing an unauthorized connection to be created to the agent without any credential or user interaction (CVSS 4.0 base score 9.3; vector reports PR:N, UI:N, AT:N). The affected deployments are OpenText Endpoint Investigator, Endpoint Forensics & Response, Information Assurance, and Endpoint Security installations that embed the SAFE Agents component, with default agents whose listening interface is reachable from an untrusted network facing the greatest risk. No public exploit code has been identified and the flaw is not confirmed as actively exploited (CISA KEV), but the pre-authentication, network-reachable bypass with full confidentiality, integrity, and availability impact makes this a genuine high-priority issue rather than a high-CVSS paper tiger.

Authenticated members of fuintCatering can read other members' refund records and the personal data they contain by iterating sequential refundId values against the ClientRefundController refund detail endpoint. The flaw is an insecure direct object reference (CWE-639) present through commit 122c9e6, and because self-registration is open, an attacker only needs a freely obtainable account to harvest buyers' names, national ID numbers, addresses, WeChat openIds, and order details. No public exploit code or confirmed active exploitation was identified at time of analysis; the impact is confidentiality-only - no writing, no system compromise - and exploitation further depends on refund records actually existing to enumerate.

Unauthenticated retrieval of complete customer order records from fuint's /clientApi/order/detail endpoint exposes buyer names, national ID numbers, phone numbers, addresses, WeChat openIds and verification codes to any remote attacker who can reach the application, and because orderId values are sequential the entire order table can be enumerated in bulk. The endpoint performs no Access-Token check whatsoever (CWE-306; CVSS 4.0 8.7, assessed CVSS 3.1 7.5 with PR:N, confidentiality-only impact), so no credentials, user interaction, or non-default configuration are required against builds at or before commit 4c4bc8a. No vendor-released patch was identified at time of analysis and no public exploit code was identified; a public technical writeup describing the unauthenticated IDOR is referenced in the advisory links, and practical risk is bounded mainly by how widely the affected fuint instance is exposed rather than by any exploitation difficulty.

Authenticated low-privilege FastBee users can read and seize control of IoT devices belonging to other tenants: the DeviceController endpoints accept a caller-supplied device ID or serial number and never verify that the requesting account actually owns that device (CWE-639). Because identifiers are sequential and easy to guess, anyone who can self-register on a FastBee 2.1.0-or-earlier instance can enumerate devices, harvest owner, IP and location metadata, and then overwrite the stored user_id and tenant_id fields to permanently take over the target device. Confirmed exploitation has not been reported (no CISA KEV entry), and no public exploit code was identified at time of analysis, but a detailed third-party technical writeup of the flaw exists, and the independent assessment rates it a genuine, prioritizable authorization defect rather than a drop-everything emergency, since a valid tenant account is a prerequisite (PR:L in the vector) and cross-tenant impact only materializes on multi-tenant deployments.

Authenticated sellers on lilishop (PickMall) through 4.4 can overwrite and effectively hijack any other store's product listings by supplying a foreign goodsId to the goods update endpoint, an insecure direct object reference (CWE-639) with an assessed CVSS 3.1 base of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N). Because the seller-api update handler never verifies that the target goodsId belongs to the caller's own store, a low-privileged seller tenant can replace product details and SKUs and reassign the item to their own store, producing a high-integrity impact with no confidentiality or availability loss. Exploitation requires a valid seller account and prior knowledge of the target product's goodsId; anonymous users cannot reach the endpoint, and no public exploit code has been identified at time of analysis (no CISA KEV entry).

Missing authorization in risesoft WorkFlow-Engine through 9.6.11 allows authenticated low-privileged users to approve or reassign other users' workflow tasks by supplying a known taskId to the complete, completeTask, or reAssign handlers under the /vue/buttonOperation endpoints. The flaw is an IDOR (CWE-639) rated 7.1 under the vendor-supplied CVSS 4.0 vector (our independent CVSS 3.1 assessment is 6.5, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N), requiring only a valid low-privilege account and knowledge of a target taskId. No public exploit or CISA KEV listing was identified at time of analysis; impact is limited to workflow approval integrity, with no data disclosure or denial of service.

Missing authorization in SmartAdmin through 3.30.0 lets any authenticated low-privileged employee change system-wide level-3 protection settings, disabling login lockout and two-factor login, weakening password rules, and clearing existing lockout records through the unannotated updateConfig and loginFail batchDelete endpoints in AdminProtectController. The prerequisite is an ordinary employee session (CVSS PR:L, no user interaction, network-reachable admin API), so the barrier is the account rather than any special configuration, and default deployments up to v3.30.0 are impacted; no public exploit identified at time of analysis and no CISA KEV listing, and the assessed impact is integrity-only (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N), making this a genuine but moderate-priority issue rather than an urgent crisis. No vendor-released patch was identified at time of analysis.

JetLinks Community through 2.10.0 allows an authenticated user holding only query-level access to the transparent-codec resource to overwrite a product's codec provider and configuration via POST /device/transparent-codec/{productId}, because that save handler is missing the @SaveAction authorization annotation the hsweb-based framework uses to gate write operations. Successful abuse hands the attacker control over how transparent (raw pass-through) messages are decoded and encoded for every device belonging to the targeted product, an integrity-only impact with no confidentiality or availability loss (CVSS 4.0 7.1 High, PR:L). Exploitation requires a valid low-privilege account on the affected deployment, the flaw is network-reachable with low complexity, and no public exploit code has been identified at time of analysis with no CISA KEV listing.

Missing authorization in MateCloud through 5.0.8 lets any authenticated remote user call /api/v1/admin/storage endpoints in StorageController without an administrative role and supply arbitrary bucket and objectName values, enabling low-privilege or self-registered accounts to list files, obtain pre-signed download URLs for other users' objects, delete objects, and upload at chosen keys. The CVSS 4.0 vector confirms network reachability with low privileges (PR:L) and no user interaction, while the independent assessment limits practical risk to the configured object-storage backend and notes that open self-registration lowers the barrier to entry. No public exploit code or confirmed active exploitation is identified in the supplied intelligence, and the independent assessment treats this as a genuine prioritization concern rather than an inflated high-CVSS artifact.

TOTP-based second-factor authentication in Ikaros 1.2.0 through 1.2.5 can be bypassed, letting an attacker who already knows a valid account password obtain a fully authenticated session - including the master administrator account - without ever supplying a TOTP code. The temporary login token issued by the jwt/apply endpoint can be replayed as a bearer JWT, refreshed into a session token, or exchanged through HTTP Basic login, collapsing a two-factor login into single-factor authentication. This is not a pre-authentication bypass: valid first-factor credentials and an account that relies on TOTP are both required, and the resulting impact is bounded by the privileges of the compromised account (rated 8.6 under CVSS v4.0; assessor's v3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N); no public exploit identified at time of analysis, although a public technical writeup documents the temp-token reuse technique.

PreDelete and PostDelete hook creation in Argo CD (2.10.0 through the releases preceding 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2) bypasses AppProject destination and resource authorization checks, so a low-privileged attacker with write access to an Application's Git repository can commit a delete hook that pins a forbidden namespace, cluster server, group, kind, or resource name and have the application-controller create that resource with the destination cluster's credentials when the Application is deleted. The scope change in the assessed vector reflects that the controller acts outside the user's AppProject boundary, so impact can include cluster-scoped resources, disallowed namespaces, persistent hook objects, and secondary objects spawned by a hook Job, all bounded by the application-controller's own cluster RBAC. No public exploit code has been identified at time of analysis, and the flaw is only meaningful where AppProject destination and resource allow/deny lists are relied upon as a security boundary, which is typical of multi-tenant deployments.

RClone Manager versions prior to 0.2.7 start their bundled local rclone rcd engine on 127.0.0.1:51900 without authentication and with a wildcard CORS origin, so any web page the user visits while the daemon is running can issue cross-origin requests to that local API using the user's operating-system privileges. An attacker who convinces a user to open a malicious or compromised page can therefore read configured storage credentials and potentially access, modify, upload, or exfiltrate locally stored files and files reachable through the user's configured remotes; the advisory's possible command-execution impact is unconfirmed. Exploitation requires the local engine to be actively running and the user to load attacker-controlled content (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6); there is no public exploit identified at time of analysis, and the vendor-released patch is 0.2.7.

Missing authentication for a critical function in Ivanti Xtraction before version 2026.4 allows remote unauthenticated attackers to create or modify trusted site configurations. This vulnerability, tracked as CVE-2026-106043 with a CVSS score of 7.5, has a high integrity impact (I:H) but no confidentiality or availability impact (C:N/A:N) per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. No public exploit identified at time of analysis; however, successful exploitation requires network reachability to the Xtraction web interface, and instances restricted to internal networks face reduced risk.

Unauthenticated access to administrative API endpoints in Esri Portal for ArcGIS can let remote attackers reach /portaladmin/local functionality that should require authentication, potentially exposing portal administration with high confidentiality, integrity, and availability impact. Exploitation is conditional - the independent assessment rates CVSS 3.1 as AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning high impact but dependent on unspecified portal configuration conditions, while the vendor input vector is 9.8 with AC:L - and no public exploit has been identified at time of analysis. Affected product is Portal for ArcGIS, tracked by CPE cpe:2.3:a:esri:portal_for_arcgis:*:*:*:*:*:*:*:*; consult Esri's September 2026 bulletin for exact affected versions and fixes.

MongoDB Server sharded clusters running versions 9.0 before 9.0.4 or 8.3.0 before 8.3.13 allow an authenticated user with write privileges on a regular collection to bypass authorization checks for internal system namespaces by submitting a bulk write operation through the mongos router. This incorrect authorization (CWE-863) can result in unauthorized writes to system namespaces, with an impact ranging from low integrity to high availability depending on the namespace targeted. No public exploit identified at time of analysis; vendor patches are available in MongoDB Server 9.0.4 and 8.3.13.

Remote unauthenticated attackers can bypass authentication by spoofing in Ivanti Connect Secure versions before 25.1.3.0 and execute arbitrary commands with full system compromise. This vulnerability is confirmed actively exploited (CISA KEV) and publicly available exploit code exists. Ivanti Connect Secure 22.7R2.14 and prior are explicitly not affected, and the vendor-released patch is version 25.1.3.0 or later.

Improper authentication in IBM MCP Context Forge prior to 1.0.2 allows remote, unauthenticated attackers to forge HS256-signed JWTs using a JWT_SECRET_KEY shipped in mcpgateway/config.py and .env.example, gaining full platform-administrator access without a database account. The attack requires two conditions to hold simultaneously: the gateway must still use the known shipped signing key, and the platform-admin bootstrap must be active (REQUIRE_USER_IN_DB=false with the token subject set to PLATFORM_ADMIN_EMAIL); because the documented production default for REQUIRE_USER_IN_DB is true, strictly default production deployments are protected, as are operators who rotated the secret before upgrading. Where both conditions are met, forged administrator tokens survive password rotation, account deletion, and session revocation, enabling administrative disclosure, modification, and service disruption; no public exploit code has been identified at time of analysis and the issue is fixed in 1.0.2.

Missing authentication on a command-execution path in Commvault CVFS (the file-system component used in Commvault Cloud and Grid HSX deployments) allows an attacker who already sits on the same network segment as the node to execute commands without supplying credentials or relying on any user action. The attack surface is deliberately narrow: successful exploitation requires adjacent-network reachability (AV:A) plus an additional attack precondition that is outside the attacker's direct control (AT:P), which is why the overall severity lands at 7.7 rather than critical despite high confidentiality, integrity, and availability impact on the affected host. Commvault has published a maintenance release that resolves the condition, and no public exploit code has been identified at the time of analysis; defenders should prioritise network segmentation of backup and storage subnets alongside the upgrade.

Unauthenticated modification of the embedded webserver password on Rockwell Automation 1732E ArmorBlock I/O modules allows any network-reachable attacker to seize the administrative account and alter device configuration. The flaw is rated 8.8 (CVSS 4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VI:H/VA:H, no confidentiality impact), matching an authentication-bypass class (CWE-294) and confirmed by the independent assessment as CVSS:3.1 AV:N/AC:L/PR:N/UI:N with C:N/I:H/A:H. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and real-world exposure depends on whether the module's webserver is reachable from untrusted networks rather than being contained by OT segmentation.

Improper authentication in the CSIv2 inbound propagation handler of IBM WebSphere Application Server 8.5 and 9.0 lets remote, unauthenticated attackers bypass authentication and have forged identity data accepted into the server-side security context, with high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Exploitation is not trivial - it requires network reachability to the CSIv2/IIOP inbound path and a deployment that actually relies on CSIv2 inbound identity propagation, which is what the AC:H metric reflects - and no public exploit identified at time of analysis. IBM has published a vendor fix, so this is best treated as a genuine high-priority issue rather than a drop-everything emergency, with prioritization going to internet- or partner-exposed CSIv2 listeners.

Authorization bypass in IBM WebSphere Application Server 8.5 and 9.0 lets an authenticated, low-privileged user who can reach the cell's management/communication network impersonate an administrator across the entire cell. Because exploitation requires both valid credentials (CVSS PR:L, authenticated) and adjacent-network positioning (CVSS AV:A) rather than open-internet reach, this is a credible mid-to-high priority issue rather than an emergency, although a successful attack yields high confidentiality, integrity, and availability impact. No public exploit code has been identified at time of analysis, and a vendor patch is available per IBM's advisory.

Arbitrary file overwrite in Wazuh Manager (3.9.0 through versions prior to 4.14.8) lets an attacker who already controls an enrolled cluster worker node corrupt protected master-side files - including ossec.conf and agent.conf - by abusing a trailing-slash basename path-validation bypass and the lack of extra_valid enforcement in MasterHandler.process_files_from_worker. Because the manager runs as root and pushes configuration out to its fleet, the overwritten files escalate into root-level remote code execution on the manager and on every connected agent, which is why the vulnerability carries a CVSS 4.0 base score of 9.4 (independent CVSS 3.1 assessment: AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). The PR:H prerequisite is the key limiter: the attacker must already control a worker node that is enrolled and syncing with the master, so this is not anonymously reachable from the internet, standalone (non-clustered) managers do not expose the vulnerable path, and no public exploit code had been identified at time of analysis.

Remote code execution in Wazuh agents 4.3.0 through 4.14.7 (not including 4.14.8) allows an attacker who already holds manager-level control over a Wazuh deployment to run arbitrary SCA policy command checks as root on every enrolled agent. The root cause is that the SCA subsystem decides whether a policy is trusted by its file path rather than by its configuration source or signature, so an unsigned policy file planted in var/incoming through the agent upgrade channel is honored and its checks execute with root privileges. The vendor CVSS 4.0 base score is 8.6 (High) - network vector, low complexity, no user interaction (PR:H), with high confidentiality, integrity and availability impact on the agent - and represents a fleet-wide escalation that only applies after a manager has already been compromised. No public exploit code and no confirmed active exploitation were identified at time of analysis; the vendor released a fix in Wazuh v4.14.8.

An authentication bypass in the Wazuh Manager API (versions 4.6.0 through 4.14.7) lets an account that already holds delegated user-administration rights take full control of the reserved wazuh superuser account by submitting an empty password to the user-update endpoint, after which the attacker can authenticate as that superuser with a blank credential. The flaw is a logic error in the security.update_user handling: the reserved-user guard and the password-policy check sit inside a truthiness test, so an empty string evaluates as falsy and both protections are skipped entirely, yielding a complete confidentiality, integrity, and availability impact on the manager (CVSS 8.6 under CVSS 4.0; our independent assessment scores CVSS 3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation is not unauthenticated and cannot be triggered by a low-privilege user - it requires a pre-existing privileged (PR:H) role capable of calling the user-update RBAC endpoint - so risk is concentrated in multi-tenant, MSSP, or role-delegated deployments and in post-compromise privilege escalation; confirmed actively exploited status is not present (no CISA KEV listing) and no public exploit code was identified at time of analysis. A vendor patch is available in Wazuh v4.14.8.

Arbitrary file read as root in Wazuh Manager 4.1.0 through 4.14.7 allows an enrolled agent to inject an upgrade_custom message over the agent-to-manager channel with an attacker-controlled file_path that the wm_agent_upgrade module processes without an origin check, disclosing sensitive files such as /etc/shadow and client.keys. Exploitation requires a valid enrolled agent identity (compromised or rogue agent, or stolen client.keys), so despite the vendor's CVSS 4.0 rating of 8.7 with PR:N, this is realistically not an anonymous internet-wide attack - our independent assessment scores it CVSS 3.1 8.7-to-moderate AV:N/AC:L/PR:L/UI:N with high confidentiality impact only. No public exploit code and no CISA KEV active-exploitation entry were identified at time of analysis, and a vendor patch is available in Wazuh 4.14.8.

Unauthenticated remote attackers can tamper with token state and disrupt service availability in NVIDIA AIStore for Linux by sending crafted token-revocation lists to a token-revocation endpoint that performs no authentication check (CVSS 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H). Because the vector shows PR:N and UI:N, no credentials, privileges, or user interaction are needed - any network-reachable deployment of the affected endpoint is directly exploitable, with the only practical limiting factor being firewall or segmentation controls around the AIStore management/control interface. There is no confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis, but the missing authentication control (CWE-306) is the defect itself, so the issue should be treated as a genuine high-priority exposure rather than an inflated score.

Missing authorization in the NVIDIA AIStore ETL management API lets remote, unauthenticated attackers read ETL job information and issue start or stop operations against existing extract-transform-load pipelines by sending crafted GET or POST requests to an AIStore proxy (CVE-2026-65172, CVSS 8.6, CWE-862). Per the assessed vector (AV:N/AC:L/PR:N/UI:N, C:H/I:L/A:L), no credentials or user interaction are required; the practical constraint is network reachability to a proxy that exposes the ETL management API in Linux or Kubernetes deployments. No public exploit code and no confirmed active exploitation were identified at time of analysis, so the immediate risk is driven by exposure of the proxy API rather than by observed attack activity.

Privilege escalation in the Xen hypervisor's XPTI (Xen Page Table Isolation) implementation can let an attacker who already controls a 64-bit PV guest on a sufficiently large-memory host break isolation between that guest and the hypervisor. The flaw lies in the page-table shadowing logic: XPTI copies guest root page-table entries via the directmap, but a PV guest's directmap does not necessarily cover all physical memory, so hosts with RAM extending past the 5 TiB boundary (3.5 TiB with CONFIG_BIGMEM=y) can cause the hypervisor to operate on entries it cannot correctly read, resulting in scope-changed high confidentiality, integrity and availability impact. Exploitation is local (AV:L/PR:L), requires PV mode rather than the default HVM/PVH guest types, and XPTI must be active; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and EPSS is low at 0.16% (5th percentile).

Firefox ESR builds prior to 153.5 contain a mitigation bypass in the browser's File Handling component, allowing attacker-controlled content to defeat a protection mechanism and, once triggered, to affect resources beyond the vulnerable component (scope change) with high confidentiality and integrity impact. Exploitation requires the attacker to persuade a user to open or handle crafted content (UI:R) and no authentication is required (PR:N), while the high attack complexity (AC:H) indicates an additional condition outside the attacker's direct control must also be satisfied - the exact trigger is not described in the available sources. No public exploit code has been identified at time of analysis and EPSS sits at 0.20% (9th percentile), which is consistent with a browser flaw gated by user interaction and a complexity precondition rather than mass scanning activity.

Firefox DevTools does not correctly enforce the same-origin policy before version 158, allowing a remote attacker to cross origin boundaries and read as well as alter data belonging to other origins (C:H/I:H, no availability impact). All Firefox builds prior to 158 are in scope per the vendor CPE, and Mozilla rates the flaw 9.1 with a network-reachable, no-privilege vector; no public exploit code has been identified at time of analysis and EPSS is low at 0.16% (4th percentile), but the vuln.today decision label is act_now, so treat patching as urgent despite the quiet exploitation signal. Note the vector discrepancy: Mozilla's published vector asserts UI:N while the independent assessment scores UI:R, consistent with a victim having to load attacker-controlled content - the exact trigger is not described in the available sources.

Enterprise Policies mitigation bypass in Mozilla Firefox allows an attacker-influenced page to circumvent administrator-enforced policies in managed browser deployments, resulting in high confidentiality and integrity impact (CVSS 8.1, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N). Only fleets where Firefox is managed through the Enterprise Policies feature are meaningfully exposed - on a default, unmanaged installation there is no enforced policy to bypass - and the vector requires the victim to interact with attacker-controlled or attacker-influenced content, with no attacker authentication required. The issue is fixed in Firefox 158 and Firefox ESR 153.5; EPSS is low at 0.20% (9th percentile) and no public exploit code or confirmed active exploitation was identified at time of analysis, though the affected enterprise-managed population makes timely patching worthwhile.

Protection-mechanism bypass in Mozilla Firefox's HTTP networking component lets remote, unauthenticated attackers defeat a built-in browser security mitigation when a victim loads attacker-controlled HTTP content, with high confidentiality and integrity impact (CVSS 8.1, C:H/I:H/A:N) but no availability impact. Exploitation requires user interaction (UI:R) and works only through drive-by or social-engineering delivery against an actively browsing user; the payoff depends on chaining the bypass to the very attack the mitigation was meant to stop. It is fixed in Firefox 158 and Firefox ESR 153.5, has no public exploit code or CISA KEV entry at time of analysis, and carries a low EPSS of 0.20% (9th percentile).

Mozilla Firefox before 158 contains a site-isolation weakness in the DOM Web Authentication component that can let attacker-controlled web content bypass intended authorization boundaries, with high confidentiality and integrity impact. Exploitation requires the victim to interact with malicious or compromised web content (UI:R); the attacker needs no authentication, and no public exploit code was identified at time of analysis, with EPSS at 0.22% (12th percentile). Mozilla fixed the issue in Firefox 158, and the referenced advisories should be used to confirm update paths.

Mozilla Firefox prior to 158 contains a mitigation bypass in the DOM: Security component that lets remote attackers defeat a built-in browser protection, potentially enabling follow-on attacks the defense was designed to stop. The issue is rated CVSS 7.3 with low confidentiality, integrity, and availability impact; it is a defense-in-depth failure rather than direct code execution, and practical harm generally requires chaining with another vulnerability. Exploitation requires the victim to open attacker-controlled web content in an affected build, and no public exploit identified at time of analysis, with no CISA KEV activity and EPSS 0.20% (percentile 9%).

Mitigation bypass in Mozilla Firefox's Enterprise Policies component allows remote attackers who can get a victim to interact with crafted content to defeat policy-enforced security controls in managed deployments; the issue is fixed in Firefox 158 and Firefox ESR 153.5. Per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) no attacker privileges are needed but user interaction is required, and successful exploitation yields high confidentiality and integrity impact with no availability impact. No public exploit code has been identified at time of analysis and EPSS is low at 0.17% (6th percentile), so real-world exposure is concentrated in enterprise environments where Enterprise Policies are actually configured rather than in default consumer installs.

Authenticated attackers with minimal privileges can disconnect active sessions of other users, including administrators, in Siemens RUGGEDCOM CROSSBOW versions prior to V6.0 due to missing authorization checks on device-disconnection requests, causing a denial of service. The flaw is network-reachable, requires low privileges (PR:L) and no user interaction, and affects only availability (VA:H) with no confidentiality or integrity impact. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.

Siemens SIMATIC IPC devices (BX-21A, RW-543A, IPC227G/277G/277G PRO/327G/377G) contain a BIOS vendor test key in the UEFI Secure Boot key database, enabling an attacker with local physical or administrative access to boot an OS or UEFI application signed with that key and completely bypass Secure Boot protections. Exploitation is access-gated - requiring hands-on device access or existing administrative privilege - and no public exploit code or confirmed active exploitation has been identified at time of analysis, but successful compromise results in full loss of confidentiality, integrity, and availability of the device.

Authenticated, privileged remote attackers on affected Siemens Industrial Edge Device Kit installations (arm64 and x86-64, versions 1.5 through 1.28) and the listed SIMATIC/SIPLUS HMI Unified Comfort panels can reach internal APIs and file paths that the software fails to restrict, exposing sensitive internal information and - per the vendor's description - potentially enabling further unauthorized system access or deletion of data. Siemens rates this CVSS 4.0 8.9 High (AV:N/AC:L/AT:P/PR:H/UI:N with full VC/VI/VA:H on the vulnerable system plus SC/SI/SA:H on subsequent systems); our independent assessment concurs with the high impact rating but emphasizes that the score is driven by impact breadth rather than ease of access, because exploitation requires a valid privileged session and an additional attack precondition is signalled by the AT:P metric. No publicly available exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis.

Unauthenticated network attackers may be able to reach and invoke critical functionality of 'tbc' releases prior to version 1.0 without supplying any credentials, a failure mode classified as missing authentication for a critical function (CWE-306); the unconstrained CVSS 4.0 score of 10.0 and our assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) both indicate complete loss of confidentiality, integrity and availability with a changed security scope. The practical caveat is significant: the CVE description is a placeholder that names no endpoint, protocol, or deployment configuration, so the exact preconditions remain unverifiable and our independent assessment explicitly records that the available signals conflict sharply. Exploitation pressure currently looks low - EPSS is just 0.14% (3rd percentile) and no public exploit has been identified at time of analysis - yet a vendor patch exists and ENISA/EUVD lists every release from 0 up to (but excluding) 1.0 as affected.

Unauthorized SCIM API access in Perforce Helix Authentication Service (HAS) versions 2022.1 through 2025.2 arises from a shipped default bearer token that the installer and configuration script fail to rotate, enabling remote, unauthenticated attackers who know the token to perform user and group provisioning operations. Chaining this with CVE-2026-61834 in the scim-patch dependency allows server-side prototype pollution and, under Node.js 24/Express with specific gadget chains, remote code execution. The underlying defect is removed in HAS 2026.1; no public exploit code has been identified at time of analysis.

An authenticated user holding only the Developer role can run CI/CD pipelines on protected branches in GitLab CE/EE without authorization, because the downstream (multi-project/child) pipeline creation service failed to enforce proper permission checks (CWE-863). All versions from 18.7 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 are affected, and exploitation is conditional: it requires a valid Developer account plus projects that combine downstream pipelines with protected-branch restrictions, which is why the independent assessment raises attack complexity to High even though the vendor rates the issue 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N). Publicly available exploit code exists in the form of a HackerOne report, but the provided data contains no confirmation of active exploitation and no KEV listing. Integrity impact is the dominant risk: unauthorized pipeline execution on a protected branch can inject or alter build, test, and deployment artifacts that the branch protection model was designed to shield.

Improper cleanup of scheduled pipeline execution policy records in GitLab Enterprise Edition lets an authenticated user execute arbitrary CI/CD pipelines in a transferred project using the destination group's privileges. Affected releases are all EE versions from 18.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. Exploitation is conditional - the attacker needs a valid account, a project that has a configured scheduled pipeline execution policy, the project-transfer workflow, and user interaction (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N, 7.7) - but publicly available exploit code exists per the referenced HackerOne report, and no CISA KEV entry has been recorded, so this is a moderate, conditional privilege-escalation risk rather than a mass-exploitation emergency.

Unauthenticated read, modification, and permanent deletion of stored credential records in Rapid7 Metasploit Framework through 6.5.4 is possible whenever the optional msf-ws REST API is running and network-reachable, because the PUT update_credential and DELETE delete_credentials handlers for /api/v1/credentials omit the warden.authenticate! call that every other route in Msf::WebServices::CredentialServlet performs before processing. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) is consistent with this: the two affected routes are reachable by unauthenticated remote attackers and allow full compromise of confidentiality and integrity of the credential store, which holds passwords, hashes, and private keys captured during shared team engagements. The practical limiting factor is deployment mode rather than the flaw itself - msf-ws is an optional component that must be explicitly started and exposed (default listener 0.0.0.0:8080), so Metasploit installations that never run the web service are not exposed; there is no public exploit identified at time of analysis and no confirmed active exploitation (not listed in CISA KEV).

An authorization bypass in SAP ABAP Platform lets a low-privileged, authenticated user open the session manager in single transaction mode - including through the Fiori Launchpad (FLP) - and then send crafted requests that defeat restrictions the platform had previously enforced correctly. The weakness is a regression: an underlying SAP API change reintroduced a flaw that had already been fixed, so only ABAP Platform deployments carrying that regressed API (and not yet covered by SAP Note 3626303) are exposed. Impact is rated 7.1 with high integrity and low confidentiality consequences and no availability impact (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N); valid low-privilege credentials are mandatory, so this is an authenticated privilege-escalation-style issue rather than a pre-auth intrusion path, and no public exploit identified at time of analysis.

SAP MII's administrative account-provisioning function fails to enforce proper authorization boundaries, enabling an attacker who already holds MII administrator privileges to craft a request that provisions an account with elevated privileges on the underlying Java application server. This can extend compromise beyond MII to the host, with high confidentiality, integrity, and availability impact, and is reflected in a CVSS 3.1 score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H). No public exploit code or confirmed active exploitation was identified at time of analysis.

Authenticated low-privileged users on IBM Planning Analytics 2.0 and 2.1 can delete folders and applications belonging to other users because the platform enforces access control at the wrong functional level. The flaw carries a CVSS v3.1 score of 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H), with the risk driven almost entirely by the high availability impact of destroyed workspaces rather than by any data disclosure. No public exploit code has been identified at time of analysis, and exploitation requires a valid account on a network-reachable instance, making this most realistically an insider or compromised-credential threat.

Improper authentication in IBM Planning Analytics 2.0 and 2.1 allows an attacker who already holds valid low-privilege credentials to escalate to unauthorized administrative access over the network, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 8.8, CWE-288). Because the vector carries PR:L, the flaw is not reachable by a fully unauthenticated outsider: the attacker must first obtain ordinary authenticated access to the deployment, after which the alternate-path authentication weakness grants administrative control. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but IBM has published a vendor patch, so the primary risk is unpatched, internet- or partner-reachable Planning Analytics installations where low-privilege accounts are widely distributed.

Authentication bypass and privilege escalation in IBM Planning Analytics 2.0 and 2.1 allow an unauthenticated remote attacker to reach functionality that should require credentials by abusing improperly validated sub-requests (CWE-288). Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, exploitation needs only network reachability to the Planning Analytics application interface - no authentication, no user interaction, and no documented non-default configuration - yielding high confidentiality, integrity, and availability impact, which is why the score is 9.8. Signals conflict and must be weighed carefully: despite the severity and total technical impact under SSVC, EPSS is only 0.36% (28th percentile), CISA SSVC records Exploitation: none, and no public exploit code has been identified at time of analysis, so this should be treated as a serious but not yet observed threat. The vendor has released a fix, so exposure is concentrated in unpatched, internet- or partner-reachable deployments.

Frappe ERPNext before 15.118.0 and 16.x before 16.27.0 allows authenticated low-privilege users to read financial data beyond their assigned role because certain endpoints do not enforce proper authorization checks (CWE-862). The vulnerability is remote and requires valid ERPNext credentials (PR:L) with no user interaction, but impact is limited to high confidentiality read exposure with no write or availability effect; no public exploit identified at time of analysis. This is a genuine but moderate-priority issue rather than a top-tier emergency, with practical risk highest in broad-user-base or multi-tenant deployments where many low-privilege or portal accounts can reach the affected endpoints.

Frappe ERPNext fails to enforce permission checks on certain inventory-record endpoints, letting any authenticated user - regardless of assigned role - modify stock and inventory data they should not be able to touch. The flaw affects releases before 15.110.0 and 16.x before 16.21.0, requires a valid ERPNext session (CVSS PR:L, not anonymous), and impacts data integrity only: there is no disclosure of records and no denial of service. It is a moderate-priority authorization defect rather than a critical emergency, and no public exploit code has been identified at time of analysis; vendor fixes are available in 15.110.0 and 16.21.0. EPSS and CISA KEV data were not provided, so active exploitation is not confirmed.

Frappe ERPNext instances running versions before 15.116.0, or 16.x before 16.27.0, expose financial data to any user who can authenticate, because specific endpoints omit the role-based authorization checks that should gate them. An attacker holding a valid but low-privileged account can query those endpoints directly and read financial records that their role does not permit, resulting in high confidentiality impact with no integrity or availability effect. Exploitation requires authentication (CVSS PR:L) and no user interaction, so the realistic threat is a malicious or compromised insider, portal user, or leaked low-privilege credential rather than an anonymous internet drive-by; no public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited.

Missing authorization checks in Frappe ERPNext before 15.112.0 and 16.x before 16.23.0 let an authenticated, low-privileged user reach specific endpoints that modify production records and change data beyond the scope of their assigned role. Because the flaw is an integrity-only problem (CVSS:4.0 7.1; VI:H, VC:N, VA:N), attackers cannot read protected data or disrupt availability - they can only tamper with production/manufacturing records they should not be able to touch. Exploitation requires a valid low-privileged account and knowledge of the affected endpoint paths (PR:L per the assessed CVSS:3.1 vector); no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, making this a genuine but moderate-priority issue rather than a critical emergency.

Missing authorization checks in Frappe ERPNext 15.x before 15.113.0 and 16.x before 16.24.0 allow any authenticated user to call affected endpoints that omit role validation and read financial records their assigned permissions do not cover. Exploitation requires a valid ERPNext session (CVSS PR:L), so the practical threat is a low-privilege insider, malicious employee, or compromised portal account rather than an anonymous internet attacker, and the outcome is limited to data disclosure with no modification or service disruption. No public exploit code has been identified at time of analysis, and the issue is assessed as a moderate-priority confidentiality exposure rather than a critical emergency.

Authenticated users of Frappe ERPNext before 15.115.0 and 16.x before 16.26.0 can read data, including personal information, beyond their assigned role permissions due to missing authorization checks on certain endpoints. The flaw requires a valid low-privilege account (PR:L) and network access but no user interaction or elevated privileges. No public exploit code has been identified at time of analysis, and this is best treated as a moderate-priority authenticated data-confidentiality exposure.

Missing authorization checks in Frappe ERPNext let authenticated users with low-privilege accounts read item master data outside their permitted role. The flaw affects all releases before 15.118.2 on the 15.x line and 16.x versions before 16.30.0, and is rooted in endpoints that skip server-side role enforcement (CWE-862). Exploitation requires valid credentials (PR:L per the assessed CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so it is not reachable by fully unauthenticated attackers, and impact is confined to information disclosure with no write or availability effect; no public exploit identified at time of analysis, and vendor patches are available.

ERPNext instances before 15.115.0 (15.x) and before 16.26.0 (16.x) allow authenticated low-privileged users to modify inventory records through endpoints that omit role-based authorization checks (CWE-862), carrying a CVSS 4.0 base score of 7.1 (High) and an assessed CVSS 3.1 integrity-only impact. Exploitation requires a valid low-privilege ERPNext account and network access, with no confidentiality or availability impact per the vector; no public exploit identified at time of analysis. Vendor-released fixes are 15.115.0 and 16.26.0, and instances at or above those versions are not affected.

Missing authorization checks in certain Frappe ERPNext endpoints let authenticated low-privileged users read personal data beyond what their assigned role permits, affecting releases before 15.112.0 and the 16.x branch before 16.23.0. Because exploitation requires a valid low-privileged account (CVSS PR:L) rather than unauthenticated access, the practical risk is highest in deployments that expose portals or large numbers of low-trust accounts, such as customer/vendor portals, sizable employee bases, or multi-tenant hosting. The flaw is a confidentiality-only issue (CWE-862) with no integrity or availability impact, no public exploit code identified at time of analysis, and no confirmed active exploitation (CISA KEV); the CVSS 4.0 base score is 7.1 while our independent assessment rates it 7.5 under CVSS 3.1, reflecting its genuine but moderate-priority access-control nature.

Missing authorization checks in Frappe ERPNext allow an authenticated user to create and modify records beyond what their assigned role permits, giving high integrity impact with no confidentiality or availability effect. Exploitation requires a valid ERPNext login with at least low privileges (CVSS PR:L), so fully unauthenticated outsiders cannot abuse it, and only deployments running versions before 15.119.0 or 16.x before 16.31.0 are affected. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited, making this a moderate-priority integrity and access-control problem whose realistic risk is concentrated among insiders or anyone holding standard user credentials.

Authenticated low-privileged users in Frappe ERPNext (all versions before 15.119.0, and 16.x before 16.31.0) can read valuation and stock-costing data beyond what their assigned role permits, because specific endpoints fail to enforce authorization checks. Exploitation requires a valid low-privileged account (PR:L per the CVSS 4.0 vector) and network access to the application; the assessed impact is confidentiality-only (CVSS:3.1 C:H/I:N/A:N), so this is primarily an insider or compromised-account risk in multi-user or multi-tenant deployments rather than an unauthenticated intrusion path. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), though a vendor security advisory and a third-party (VulnCheck) advisory are available.

Missing authorization checks in project-related endpoints of Frappe ERPNext allow any authenticated low-privilege user (CVSS v3.1 PR:L, remote, no user interaction) to read project data that their assigned role should not permit, resulting in a high-confidentiality, read-only disclosure with no integrity or availability impact. Affected deployments are ERPNext versions before 15.111.0 and 16.x before 16.22.0, with vendor patches available at 15.111.0 and 16.22.0; there is no public exploit identified at time of analysis, and the flaw is not confirmed actively exploited (CISA KEV). The practical risk is highest in multi-user or multi-tenant installations where semi-trusted or low-privileged accounts exist, since exploitation only requires a valid account and direct knowledge of the affected endpoint calls.

Authenticated users can modify records in Frappe ERPNext before 16.22.0 by invoking endpoints that omit proper authorization checks, allowing operations beyond their permitted role and resulting in unauthorized data modification. This missing authorization flaw (CWE-862) requires a valid low-privilege account and network access to the ERPNext web application, but no victim interaction; the assessed CVSS:3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) confirms integrity impact only. No public exploit code or confirmed active exploitation was identified at time of analysis.

Missing authorization checks in Frappe ERPNext versions before 16.14.0 allow authenticated users to modify master data records that lie outside their assigned role, giving them write access they were never granted. The CVSS v4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N, VI:H) confirms the issue is network-reachable but requires at least a low-privileged account; only data integrity is affected, with no confidentiality or availability impact. Per our assessment this is a legitimate but moderate-priority access-control gap rather than a critical emergency, and no public exploit code or confirmed active exploitation has been identified at time of analysis. Upgrading to 16.14.0 removes the condition entirely.

Missing authorization in Frappe ERPNext before 15.115.0 and 16.x before 16.26.0 allows authenticated low-privileged attackers to read financial data beyond their permitted role. The vulnerability is network-reachable with low attack complexity and requires only a valid low-privileged account, resulting in high confidentiality impact but no integrity or availability impact. No public exploit code or active exploitation has been identified at time of analysis, and the CVSS 4.0 score is 7.1 (High).

Missing authorization checks in Frappe ERPNext before 15.121.0 and 16.x before 16.33.0 allow authenticated users with low privileges to call certain endpoints directly and read data beyond what their assigned role permits. The flaw is confidentiality-only (CWE-862, missing authorization): the CVSS v4.0 vector (AV:N/AC:L/PR:L/UI:N/VC:H/VI:N/VA:N) and the independent assessment (CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 7.1) agree that no data modification or denial of service is possible and that network access plus a valid low-privilege ERPNext account is required, with no user interaction. There is no public exploit identified at time of analysis, though the realistic threat population is insiders, compromised credentials, or environments that issue low-trust/portal logins, so the practical risk is moderate-priority exposure of sensitive ERP records rather than unauthenticated compromise.

Missing authorization checks in Frappe ERPNext allow an authenticated low-privileged user to invoke status-modification endpoints that omit proper role enforcement, altering record status and business data beyond the attacker's assigned role. Affected versions are ERPNext before 15.121.0 and 16.x before 16.34.0; exploitation requires a valid ERPNext account with at least low privileges (CVSS PR:L) and is reachable over the network, but carries no confidentiality or availability impact, making it primarily an integrity-focused insider or post-account-compromise escalation path. No public exploit code has been identified and the issue is not confirmed as actively exploited (no CISA KEV listing); EPSS data was not available in the provided intelligence. Vendor-released fixes are available in 15.121.0 and 16.34.0.

Missing authorization checks in Frappe ERPNext before 15.120.0 and 16.x before 16.33.0 allow an authenticated user holding only a low-privileged role to bypass role-based access control and read financial data by issuing direct requests to specific endpoints. The affected vector is network-reachable with low complexity but requires a valid account (PR:L), and the impact is limited to read-only confidentiality loss - no data modification or denial of service is possible. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so it is a moderate-priority broken access control flaw rather than an emergency; patched instances and deployments restricted to trusted users carry substantially reduced practical risk.

Missing role-based authorization enforcement in Frappe ERPNext before 15.121.3 and 16.x before 16.35.0 lets any authenticated user read financial data that their assigned role should not permit. Because the vulnerable endpoints can be requested directly over the network with any valid low-privilege account and require no user interaction or non-default configuration, the practical risk is malicious insiders or attackers operating with stolen, shared, or weak credentials rather than anonymous outsiders. Impact is confidentiality-only (no data modification or availability loss), and no public exploit code or confirmed active exploitation was identified at time of analysis; the vendor has released fixed versions 15.121.3 and 16.35.0.

Missing authorization enforcement in Frappe ERPNext endpoints lets authenticated low-privileged users read personal data beyond the scope their assigned role permits, affecting releases before 15.120.0 and 16.x before 16.33.0. The flaw is network-reachable and requires only a valid session for a minimal role, as reflected in the assessed CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N with confidentiality-only impact (C:H, I:N, A:N) and a CVSS 4.0 base score of 7.1; unauthenticated attackers cannot exploit it. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), so this is a moderate-priority access-control defect rather than a critical remote-code compromise, with the main risk being unauthorized disclosure of employee, customer, or contact records held in the ERP.

Frappe ERPNext instances running releases before 15.120.0, or 16.x releases before 16.23.0, contain an authorization bypass that allows any authenticated user - including a low-privilege account - to read party records outside the scope of their assigned role. The affected endpoint honours a caller-supplied flag that is meant to disable its own permission enforcement, so simply setting that flag in the request causes the server to skip the role check entirely; the result is a read-only confidentiality exposure with no write, modification, or availability impact. No public exploit code has been identified at time of analysis, but exploitation requires only a valid session and is most consequential on multi-user or multi-tenant deployments where party data is meant to be segregated by role, making this a legitimate but moderate-priority issue rather than a top-tier emergency.

Authenticated low-privileged users can create documents beyond their permitted roles in Frappe ERPNext before 15.121.0 and 16.x before 16.34.0, because certain document-creation endpoints omit the role-based authorization checks the Frappe permission model normally enforces. The flaw is a CWE-862 missing authorization issue scored CVSS 4.0 7.1 (an independent CVSS 3.1 assessment also returns 7.1), with high integrity impact and low confidentiality impact, requiring only a valid low-privilege account (PR:L) and no user interaction. No public exploit code or confirmed active exploitation was identified at time of analysis, but deployments that permit self-registration or issue portal/customer accounts widen the realistic attacker pool.

Missing authorization checks in Frappe ERPNext before 15.121.3 and in 16.x before 16.35.0 allow any authenticated user - including a low-privilege or self-registered account - to send requests to certain endpoints and modify data beyond what their assigned role permits. Authentication is mandatory (PR:L in the assessed vector), so anonymous remote exploitation is not possible; risk is concentrated in deployments with many distinct user roles, untrusted or self-registered users, or exposure to credential compromise. There is no public exploit identified at time of analysis and no CISA KEV entry, and the vendor has released fixed versions in the 15.x and 16.x lines.

Missing authorization in Frappe ERPNext document-creation endpoints (all versions before 15.121.0, and 16.x before 16.34.0) lets any authenticated low-privileged user - a portal, employee, or customer self-service account - create documents against records beyond their permitted role, bypassing role-based access controls. Impact is confined to integrity: the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N) and our independent CVSS 3.1 assessment of 7.1 (I:H, C:N, A:N) both show unauthorized document creation with no data disclosure or service disruption. No public exploit code has been identified at time of analysis and no CISA KEV listing is present, while vendor-released fixes exist in ERPNext 15.121.0 and 16.34.0.

Missing authorization checks in Frappe ERPNext before 16.34.0 allow any authenticated user to read financial records - accounting, ledger and invoice data - that their assigned role should not permit, resulting in a confidentiality-only breach. Exploitation requires only a valid low-privileged account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, score 7.1) and network reachability to the instance; no admin rights, user interaction, or special configuration are needed, which scopes the practical risk toward insiders or attackers holding stolen or self-registered low-trust accounts. No public exploit code has been identified at time of analysis, and CVE-2026-109614 is not confirmed actively exploited (CISA KEV); it is assessed as a credible but moderate-priority issue rather than a critical emergency.

Missing authorization checks in Frappe ERPNext document-status modification endpoints allow authenticated low-privileged users to alter records beyond their assigned roles, with the primary impact being high integrity loss and limited availability impact (CVSS 4.0 7.1; assessed CVSS 3.1 AV:N/AC:L/PR:L/UI:N/C:N/I:H/A:L). Only instances running the 15.x branch below 15.121.0 or the 16.x branch below 16.34.0 are affected, and exploitation requires a valid low-privilege account plus reachability and knowledge of the relevant status endpoints - no administrative access or anonymous path exists, and confidentiality is unaffected. This is a genuine but moderate-priority issue rather than a critical emergency; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation.

Authenticated low-privileged users can modify documents and data beyond their assigned role permissions in Frappe ERPNext before 15.119.1 and in 16.x before 16.32.0, because certain endpoints fail to enforce proper permission checks (CWE-862, Missing Authorization). The issue is rated CVSS 4.0 7.1 (CVSS:3.1 7.1, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) - integrity-only impact with no confidentiality or availability effect - and exploitation requires a valid ERPNext session for a low-privileged account plus knowledge of the specific unguarded endpoints, so it is not reachable by anonymous or unauthenticated attackers. There is no CISA KEV listing and no public exploit identified at time of analysis; realistic risk is confined to malicious insiders or attackers who already hold low-privilege credentials, and vendor-released fixes are available in 15.119.1 and 16.32.0.

Authenticated low-privilege users of Open WebUI versions 0.8.6 up to but not including 0.11.4 can escalate privileges through the terminal proxy endpoint /api/v1/terminals/{server_id}/{path}, which forwards requests to the backend Terminals administrator API with the shared key attached; by targeting admin paths directly, an attacker can enumerate and stop other users' terminals, modify terminal policies, and inject environment variables into other users' sessions. The flaw is a missing-authorization (CWE-862) path-confusion issue reachable by any account with PR:L and no user interaction, and it only matters where the terminals feature is enabled against configured terminal servers in a multi-user deployment. No public exploit code has been identified at time of analysis and the issue is not tied to any confirmed active exploitation, but the vendor has shipped a fix and the independent assessment rates this as a genuine, moderate-priority risk rather than an emergency.

Nginx UI versions prior to 2.4.1 let an authenticated, OTP-enabled user holding only an ordinary JWT - without the X-Secure-Session-ID step-up header - create or modify Nginx configuration and trigger reload behavior by calling the nginx_config_add and nginx_config_modify tools through the /mcp and /mcp_message endpoints, which were protected by ordinary authentication alone. The equivalent HTTP configuration mutation routes correctly enforced the RequireSecureSession middleware, so the MCP channel constituted an alternate path around that control (CWE-288). Per the CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H, impact is limited to integrity and availability with high severity driven by unconstrained config writes; exploitation requires an existing low-privilege authenticated session on a pre-2.4.1 instance, and no public exploit code or confirmed active exploitation was identified at time of analysis. The issue is fixed in version 2.4.1, and the upstream commit additionally hardened backup-related routes with RequireSecureSession.

Configuration validation bypass in Nginx UI (nginx-ui) prior to 2.4.1 lets an authenticated user with configuration-write privileges inject restricted Nginx directives by placing a benign directive first on a single line and appending a semicolon-separated restricted directive such as load_module, js_import, perl, or user root, because ValidateConfigDirectives only inspects the first token of each newline-split line. The flaw affects the REST, nginx_config_modify, site, and stream write paths and can escalate to arbitrary code execution in the Nginx worker context when a loadable Nginx module is already present on the host, a precondition that limits practical impact. No public exploit code was identified at the time of analysis, and the vendor released patch version 2.4.1.

Nginx UI installations before 2.4.1 expose two account-security endpoints, POST /api/otp_enroll and POST /api/finish_passkey_register, that let an attacker holding a stolen, valid JWT bind an attacker-controlled TOTP secret or register an attacker-controlled passkey against the victim's account, producing persistent access that survives a password change. The CVSS vector (AV:N/AC:L/PR:L/UI:N) confirms exploitation requires an authenticated session rather than being unauthenticated, and no public exploit code has been identified at time of analysis. The TOTP path only succeeds if the victim has not already enabled TOTP, because it relies on an existing-enrollment guard, whereas the passkey registration path has no equivalent guard and is exploitable regardless of prior enrollment.

Unintended outbound network egress in IBM Maximo Application Suite's optional Location Service for Esri Component (versions 9.0, 9.1, and 9.2) stems from a misconfigured Kubernetes NetworkPolicy that fails to restrict pod egress, allowing traffic to reach destinations the deployment intended to block. Rated CVSS 3.1 base 7.7, the score is driven mostly by the Scope change (S:C) and High confidentiality impact (C:H) rather than ease of attack; the vector (AV:N/AC:L/PR:L/UI:N) indicates remote exploitation at low complexity but with the attacker already holding a low-privileged foothold inside the environment, and no user interaction is needed. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV not listed), so this is best treated as a moderate-priority network-segmentation and data-exposure issue affecting clusters that rely on the shipped NetworkPolicy for egress control.

Broken object-level authorization in Shaark 1.2.13 through 1.2.44 lets any authenticated non-admin user overwrite or delete other users' links, stories, chests, and albums by sending PUT or DELETE requests to /api/{link,story,chest,album}/{id} with sequential numeric IDs, because the API controllers load records with findOrFail() and never verify that the underlying post belongs to the calling user. Integrity impact is high (content can be modified or destroyed, including private items) while confidentiality is not affected and availability impact is limited; exploitation requires a valid low-privilege account on a multi-user instance, and the attacker must be able to obtain one via open registration or an existing tenant. This is a genuine but moderate-priority IDOR-class flaw (CWE-639); no public exploit code or confirmed in-the-wild activity was identified at time of analysis, and single-user or self-only deployments have no victim content to target.

Unauthenticated remote attackers can seize global super-admin control of Rapyd Admin installations running versions 9.0.0 through 9.19.x, because the framework's setup installer seeds a hard-coded administrator account (admin@laravel, password 'admin') that grants the highest privilege level in the application. The account is silently re-created on every execution of the `rpd:make` artisan command, so an operator who previously changed the password or removed the account can have the known credential restored without warning, and a successful login bypasses per-record authorization checks and multi-tenant scoping entirely. VulnCheck disclosed the issue with full source references, no public exploit code was identified at time of analysis, and no evidence of confirmed active exploitation (CISA KEV) is present; the vendor shipped the fix in v9.20.0, which creates the first admin once with a random password and never re-seeds it.