Privilege Escalation
Monthly
Local privilege escalation in Google Android 14, 15, 16, 16-qpr2, and 17 lets a low-privilege app bypass permission checks through a confused-deputy flaw in the dialInternal code path, allowing the app to perform permission-protected actions it should not be able to perform. Exploitation requires a local foothold - the attacker must already be running code as a low-privilege app (PR:L) - but needs no user interaction (UI:N) and offers no remote attack surface (AV:L), making this a credible but not emergency-priority risk. There is no CISA KEV entry and no public exploit identified at time of analysis; patched builds from the October 2026 Android Security Bulletin are not vulnerable.
Local privilege escalation in Google Android 16, 16-qpr2, and 17 arises from improper input validation in the Bluetooth snoop logger's FilterCapturedPacket routine (snoop_logger.cc), which can corrupt memory when malformed packet data is processed. Exploitation requires a low-privileged local app or process already running on the device (CVSS vector shows AV:L/PR:L/UI:N), meaning an attacker must first obtain a foothold but needs no user interaction and no additional execution privileges to escalate to full confidentiality, integrity, and availability impact. There is no public exploit code and no confirmed active exploitation (CISA SSVC exploitation value: none; not in KEV, no POC identified), but a fix is available through the Android Security Bulletin dated 2026-10-01, so this should be treated as a genuine, second-tier patch-priority issue rather than an emergency.
Local privilege escalation in Google Android 14, 15, 16, 16 QPR2 and 17 is possible through an out-of-bounds write in the qsort routine of libufdt_sysdeps_vendor.c, which occurs when the device-tree (ufdt) parsing path is driven into resource exhaustion with attacker-influenced input. An attacker who already holds a local, low-privileged foothold on the device - for example a malicious installed app or a process that can feed data into the ufdt parsing path (PR:L) - can trigger the flaw with no user interaction and no additional execution privileges, achieving high confidentiality, integrity and availability impact within the platform (CVSS 7.8). No public exploit identified at time of analysis, and the issue is addressed through the October 2026 Android Security Bulletin.
Local privilege escalation on Android 14, 15, 16, 16-qpr2, and 17 stems from an out-of-bounds read in MessageQueueBase.h caused by an incorrect bounds check, allowing an attacker with low-privilege local code execution to gain elevated privileges with high impact to confidentiality, integrity, and availability (CVSS 7.8). Exploitation requires a locally installed malicious or compromised app and no user interaction, and no public exploit has been identified at the time of analysis.
Local privilege escalation in Android's Bluetooth stack lets an app running with ordinary privileges corrupt control flow in the privileged Bluetooth process and inherit its elevated rights. The root cause is an uninitialized-pointer dereference (CWE-824) in handle_le_monitor_device_event of msft.cc, the Microsoft HCI vendor-extension handler, affecting Android 16, Android 16-qpr2 and Android 17 per EUVD. This is a second-stage escalation rather than a remote entry point: the attacker must already have local code execution and be able to reach the Bluetooth LE monitoring path (CVSS AV:L, PR:L, UI:N), and no public exploit code has been identified at time of analysis; Google addresses the issue in its October 2026 Android Security Bulletin.
Local privilege escalation in Google Android 14 through 17 (including 16 QPR2) lets a low-privilege local actor trigger an integer overflow inside the NFC Type 4 Tag read/write path (rw_t4t_update_file in rw_t4t.cc) that produces an out-of-bounds write, yielding code execution in a higher-privileged context. Per the assessed vector (AV:L/AC:L/PR:L/UI:N), the attacker must already have local code execution or app presence on the device but needs no user interaction, and exploitation requires attacker-controlled NFC Type 4 Tag data to reach the reader/writer code path on an unpatched build. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); the CVSS score is 7.8 and the practical constraint is the local-only attack vector, making this a genuine fleet-patching priority rather than an emergency.
An out-of-bounds write in Android's NFC Execution Environment (NFCEE) action handling code (nfa_nfcee_act.cc) lets a locally installed low-privilege application corrupt memory in the NFC stack and escalate to system-level privileges. Per the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, the attacker must already be able to run code on the device as a low-privilege app (PR:L) and the flaw is not reachable over the network (AV:L), with no user interaction required; devices running unpatched Android 16, 16-qpr2, or 17 builds are affected, while those with the October 2026 security patch are not. Exploitation is not observed in the field - SSVC records Exploitation:none and there is no KEV listing or public exploit code identified at time of analysis - and EPSS is low at 0.11% (1st percentile), so this presents as a genuine but non-urgent local privilege-escalation issue rather than a remotely exploitable emergency.
Local privilege escalation in Google Android 17 lets a locally installed, low-privileged application escape its sandbox and obtain system-level privileges by reaching the isSystem() routine in WifiPermissionsUtil.java, which fails to perform the required permission check (CWE-862). The flaw is rated CVSS 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), reflecting a changed-scope impact in which a compromised app in the application sandbox compromises the platform itself, with high confidentiality, integrity and availability effects and no user interaction required. An attacker must already have achieved local code execution on the device (for example through a malicious or trojanized app), and only Android 17 is listed as affected, so devices on other releases or on the October 2026 patch level are not exposed; no public exploit identified at time of analysis, and the issue is addressed through the Android Security Bulletin dated 2026-10-01.
Authenticated members of a Plane project - including users holding only the lowest GUEST role - can demote project Administrators and Members through the ProjectMemberViewSet.partial_update endpoint, stripping them of project control. The pre-1.3.0 authorization check only blocked assigning a role higher than the requester's own, so it silently allowed assigning a lower or equal role; the attacker cannot elevate themselves, but can degrade other members' access. The issue is fixed in Plane 1.3.0, and no public exploit code or confirmed active exploitation was identified at time of analysis (CVSS 8.1, EPSS not provided).
Plaintext logging of API keys in Plane (makeplane/plane) prior to 1.4.0 lets an authenticated low-privilege user who can read application logs harvest other users' long-lived API tokens and use them to escalate privileges, potentially including to administrative accounts. The vulnerable behavior is inherent to affected versions - the APITokenLogMiddleware component writes API keys into request/application logs in cleartext - and exploitation requires both a valid low-privilege account (CVSS PR:L) and visibility into the resulting log output; if logs are restricted to admins or shipped to a protected external sink, the realistic exposure narrows to insiders or anyone who can reach the log store. No public exploit code or confirmed active exploitation has been identified at time of analysis and no EPSS signal was supplied; overall this is a credible, moderately-high-priority issue rather than a drop-everything emergency, and it is fixed in Plane 1.4.0.
Privilege escalation in Progress Telerik Fiddler Classic for Windows (versions prior to v6.0.20262.10021) lets a local low-privileged attacker replace one of the application's external helper executables with a different, validly signed binary that passes the product's weak publisher-name allow-list check, causing Fiddler to launch attacker-chosen code - including elevated (Administrator) execution for the helper tools that request elevation. Exploitation is local and authenticated (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 7.9), requires write access to the installed helper binaries, and is gated on a user launching the affected tool and approving the elevation prompt without noticing the executable name changed; it is not remotely or unauthenticated exploitable, and there is no public exploit identified at time of analysis. The authoritative assessment rates this a moderate, locally-exploitable privilege-escalation flaw rather than a drop-everything priority, with the UI:R requirement and the need for a pre-existing local foothold being the main limits on real-world abuse.
Out-of-bounds kernel memory writes in the NXP GAU ADC driver (drivers/adc/adc_mcux_gau_adc.c) of Zephyr RTOS let a local user-mode thread that has already been granted the ADC device object corrupt memory beyond an undersized buffer it supplies to the adc_read()/adc_read_async() syscalls. Exploitation of the privilege boundary requires a Zephyr build with CONFIG_USERSPACE=y running on an NXP RW61x SoC with the GAU ADC devicetree node enabled; the attack vector is localized (CVSS 3.1 8.4, AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H) and the caller must already hold a device-object grant, but the scope change (S:C) and high integrity/availability impact reflect a genuine userspace-to-kernel privilege escalation path capable of kernel memory corruption or a crash. No public exploit code and no confirmed active exploitation were identified at time of analysis; builds without CONFIG_USERSPACE or on SoCs other than RW61x with the GAU ADC node enabled are not exposed to the privilege boundary and only suffer a silent overflow when the application itself passes an undersized buffer.
Out-of-bounds write in MediaTek's 'vdec' hardware video-decoder path allows remote escalation of privilege on a broad set of affected MediaTek SoCs - including MT6768, MT6833, MT8186, MT8195 and MT6877 - when a victim opens or plays attacker-controlled media that reaches the vulnerable decode routine. Exploitation requires no additional execution privileges or authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) but does require user interaction, since the crafted stream must actually be rendered by the decoder; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the risk is best characterised as a credible, above-average-priority mobile vulnerability rather than an emergency. MediaTek has assigned patch ID ALPS11383899 (issue MSV-9614) and published guidance in its October 2026 product security bulletin.
Local privilege escalation in the MediaTek APU (AI Processing Unit) driver allows an attacker with existing code execution on affected devices to trigger a use-after-free, achieving full compromise of confidentiality, integrity, and availability (CVSS 8.4). The flaw affects MediaTek chipsets MT8781, MT6993, MT6899, MT8668, MT8910, and MT8793, and requires no additional privileges or user interaction once local access is obtained. No public exploit code or active exploitation is confirmed at time of analysis.
An out-of-bounds write in MediaTek modem (baseband) firmware allows an attacker operating a rogue base station to escalate privileges on a wide range of MediaTek chipsets (e.g., MT6853, MT6980, MT6991, MT8798, MT6895) once the victim's device connects to that base station; no authentication is required, but exploitation is high-complexity and requires user interaction per the assessed vector. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the risk is bounded by the need for RF proximity to a malicious base station rather than being a mass-exploitable remote flaw.
Local privilege escalation in MediaTek's APU (AI Processing Unit) allows a locally-executing attacker to corrupt memory via malformed input, potentially achieving kernel-level code execution on devices with affected chipsets (MT6899, MT8781, MT8910, MT8793, MT6993, MT8668). The vulnerability is rated CVSS 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and requires the attacker to already run code on the device, such as a malicious Android app, with no additional privileges or user interaction needed. No public exploit identified at time of analysis, and the flaw is fixed by MediaTek patch ALPS11249004.
Local privilege escalation in MediaTek NeuroPilot on affected chipsets (MT8781, MT8189, MT6993, MT8793, MT8910, MT8668, MT8188, MT6881, MT8875) allows an attacker with local code execution to trigger an out-of-bounds write in the APU/AI driver, potentially gaining high-integrity code execution with no user interaction, though no additional privileges are needed once that local app context exists. Vendor patch ALPS11249062 is available; no public exploit identified at time of analysis. It is a high-priority patch target for affected MediaTek-based devices but is not remotely reachable, limiting its scope to privilege escalation rather than initial compromise.
Local privilege escalation in MediaTek's NeuroPilot component allows an attacker with an existing foothold on a device to corrupt memory and elevate privileges via an out-of-bounds write caused by a missing bounds check (CWE-787), rated CVSS 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Affected platforms are devices built on MediaTek chipsets MT8668, MT8875, MT8781, MT8910, MT6881, MT8188, MT8189 and MT6993 that ship an unpatched NeuroPilot build. The flaw is not remotely reachable and requires local code execution (typically a running or installed Android app with no special privileges); no user interaction or elevated permissions are needed once that foothold exists, and no public exploit code was identified at time of analysis.
Local privilege escalation in MediaTek's Video HAL lets an unprivileged app already running on an affected device corrupt a fixed-size stack buffer via crafted input to the video hardware abstraction layer, yielding code execution in the HAL context with high impact to confidentiality, integrity and availability (CVSS 8.4, AV:L/PR:N/UI:N). The flaw stems from a missing bounds check (CWE-121, stack-based buffer overflow) and affects roughly four dozen MediaTek chipsets spanning the MT6xxx, MT8xxx and MT2718 families used in Android phones, tablets, Chromebooks and automotive platforms. No user interaction and no additional execution privileges are required once local code execution exists, but the attack vector is local only - remote exploitation is not indicated and no public exploit code has been identified at time of analysis. MediaTek has assigned patch ID ALPS11375674 (issue MSV-9571), delivered to OEMs through its October 2026 product security bulletin.
Memory corruption in the MediaTek cellular modem baseband (an out-of-bounds write from a missing bounds check) allows an attacker who operates a rogue base station within radio range to escalate privileges on the target device without authentication and without any user interaction. Exploitation is not reachable over the internet: the CVSS vector AV:A/AC:H/PR:N/UI:N with C:H/I:H/A:H reflects that the attacker must be in adjacent radio proximity and must successfully induce the victim's UE to attach to the malicious base station, and CISA's SSVC assessment records Exploitation: none and Automatable: no, so this is a conditionally gated baseband flaw rather than a mass-exploitation emergency. No public exploit code has been identified at time of analysis; MediaTek has released a fix under Patch ID MOLY01778988 (Issue ID MSV-8897) in its October 2026 product security bulletin.
An out-of-bounds write in MediaTek modem firmware (CWE-787) allows a nearby attacker operating a rogue base station to escalate privileges on affected devices once the user equipment attaches to the attacker-controlled cell. The flaw has a CVSS 3.1 base score of 7.5 (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) and affects dozens of MediaTek chipsets, including MT6833, MT6877, MT6983, MT6985, and MT6989, when they run unpatched modem firmware. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records no observed exploitation and marks the issue as not automatable, and MediaTek has published a fix under Patch ID MOLY01778993 in its October 2026 product security bulletin.
Improper privilege management in LaraDashboard before 1.4.8 lets an authenticated Admin-tier user who holds the role.edit permission escalate to Superadmin by renaming or editing roles, or by granting themselves user.login_as rights, which then exposes account takeover and the core-upgrade and module-installation functions needed for code execution. The pre-patch guard in RoleController only refused Superadmin role tampering when the application ran with demo_mode enabled and the role name was literally 'Superadmin', so ordinary production deployments are exposed to any role-management holder by default. Exploitation is access-gated rather than anonymous: it requires a pre-existing Admin account with role.edit, no user interaction is needed, and no public exploit has been identified at time of analysis; the vendor has released the 1.4.8 patch.
Privilege escalation in the Ultimate Member WordPress plugin affects all versions through 2.13.1, allowing an authenticated attacker to manipulate a user-controlled key that the plugin fails to bind to the requester's own account or privileges, thereby elevating a low-privilege account to a higher role such as administrator. The flaw requires an authenticated account (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base score 8.8), but because Ultimate Member supplies front-end user registration, an attacker can typically self-register on sites with open registration enabled - the common deployment mode - lowering the practical barrier to entry; sites that disable open registration require a pre-existing credential. Exploitation status at time of analysis: no public exploit identified at time of analysis, and the vulnerability is not confirmed actively exploited (CISA KEV), though the low attack complexity and high confidentiality, integrity, and availability impact make rapid patching a priority, with no EPSS score supplied in the available intelligence.
Privilege escalation in the Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress versions up to and including 4.9 allows an authenticated Sales Representative-level user who holds both the add_contacts and send_emails capabilities to rebind a contact record to an Administrator's WordPress user ID, then use the v4 email-test endpoint to mint an {auto_login_url} key and obtain a fully authenticated Administrator session. This is a genuine high-priority issue rather than a CVSS-inflated one, but the practical risk is contingent on a site having delegated those non-administrator Groundhogg roles to the attacker; no public exploit identified at time of analysis, and the vendor has released a fix in version 4.9.1.
Workflow-supplied container options in Gitea act_runner (versions before 3.0.0) are merged straight into the Docker HostConfig of the job container, letting a workflow author request host PID/IPC namespaces, CapAdd=ALL and unconfined seccomp/apparmor and then escape to the runner host as root. The twist is that the flaw is exploitable precisely when runner privileged mode is disabled: that code path forces only Privileged=false while preserving namespace, capability, device and security-profile flags from workflow YAML, so the control administrators rely on does not contain the attack. Only the Docker job-container backend is affected, and exploitation requires the ability to submit or trigger a workflow on a repository served by that runner (authenticated, push or pull-request privileges per the PR:L vector), with impact changing scope to the underlying host; no public exploit identified at time of analysis, and EPSS is low at 0.20% (9th percentile), though real-world risk is severe for shared runners open to untrusted workflow authors.
Unauthenticated WebSocket endpoints in the Monta EV charging platform (monta.app, all versions) allow any network-reachable attacker to impersonate a charging station and thereby read sensitive backend data or perform unauthorized actions on the platform. The weakness is a missing-authentication flaw (CWE-306) rated 9.3 under CVSS 4.0 and mapped by the independent assessment to CVSS 3.1 AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact and low availability impact, meaning unauthenticated remote attackers need no credentials, user interaction, or non-default configuration - network reachability to the charging-station WebSocket service is the only practical prerequisite. There is no public exploit identified at time of analysis and no KEV listing, but ICS-CERT has published an advisory covering all versions, and the absence of a version-based mitigation makes exposure reduction the primary interim control.
Local privilege escalation leading to code execution in Nx (Nrwl Nx) affects versions 14.6.0 through 22.7.8 and 23.1.x before 23.1.2 on macOS and Linux, where daemon and isolated plugin-worker Unix domain sockets are created in shared temporary locations such as /tmp/.nx without owner-only 0700 directory or socket permissions. Because the socket transport performs no authentication and relies entirely on filesystem containment, a second unprivileged local account on the same shared build server, developer host, or multi-user container can connect and invoke handlers - notably PROCESS_IN_BACKGROUND, which accepts a module path and invokes its default export as the account running Nx - and can also read workspace file contents, project graphs, and task hashes. The flaw is rated CVSS 4.0 8.5 (AV:L/AC:L/PR:L, CWE-269); no public exploit code was identified at time of analysis, single-user machines with no other local account are not exposed, and disabling the daemon alone does not remove the still-vulnerable plugin-worker sockets - only upgrading to 22.7.9 or 23.1.2, or enforcing owner-only socket and directory permissions, closes the exposure.
Unauthenticated privilege escalation in the Divi Membership plugin for WordPress (versions up to and including 2.2.0) lets any site visitor create a brand-new account with the administrator role and, by also submitting auto_login=on, be logged in as that administrator within the same request - resulting in complete site takeover. The flaw (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) sits in dmem_form_submit_handler(), which derives the new user's role by iterating every WordPress role and calling password_verify() against an attacker-supplied bcrypt hash in the form_id POST parameter, with no whitelist of permitted roles. The only prerequisite is a WordPress nonce, which is publicly emitted on any page that renders the Divi Membership registration form and is therefore readable by any unauthenticated visitor; no public exploit code has been identified at time of analysis.
Account takeover in the WordPress plugin Super Forms - Drag & Drop Form Builder affects every version through 6.3.316: any authenticated user with Subscriber-level access or above can overwrite the password and email address of an arbitrary account, including an administrator, and seize the site. The flaw sits in the Register & Login add-on, whose before_email_success_msg() routine trusts an attacker-supplied user_id in its register_login_action='update' flow and hands it directly to wp_update_user() without any ownership or capability check, while the super_save_form AJAX action that creates the malicious form is equally unprotected; the CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8) reflects that a low-privileged, self-registrable account is the only real prerequisite. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the low bar to entry plus the add-on requirement makes this a genuinely high-priority privilege-escalation flaw rather than an inflated score.
Privilege escalation in Wind River VxWorks 7 (all versions up to 26.09) allows an authenticated low-privilege shell user to bypass the per-user command privilege check and execute commands they are not authorized to run, impacting confidentiality, integrity, and availability (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not universal: it requires the command shell to be configured in the vulnerable per-user command-privilege-enforcement mode and requires the attacker to already hold a valid low-privilege shell account, so devices that do not use that mode or expose no low-privilege shell are not affected. No public exploit identified at time of analysis, and the vendor has released a patch in version 26.09.
Improper privilege management in Apache HTTP Server's mod_ssl (versions 2.4.0 through 2.4.68) causes SSLRequire access-control directives that use file-related expressions to be evaluated in a way that can grant or deny access contrary to the server operator's intent, giving a remote attacker a possible means to reach content that the SSLRequire check was meant to protect or, conversely, to disrupt intended authorization. The flaw is not reachable in a default configuration: exploitation requires mod_ssl to be loaded and the operator to have configured access control specifically through the SSLRequire directive using file-related expressions, a non-default, operator-chosen configuration, which is reflected in the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (high attack complexity, low confidentiality and integrity impact, no availability impact); authentication requirements for the attacker are not confirmed from available data. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided.
Authenticated subscriber-level attackers can escalate privileges on WordPress sites running ByteCoreStack - MCP Connector for AI Tools versions up to 1.2.2 due to an incorrect privilege assignment (CWE-266). The vulnerability is network-exploitable with low complexity and requires only a subscriber account (CVSS PR:L), with no user interaction, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8). No public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated privilege escalation in the Authorizer WordPress plugin (versions up to and including 3.15.3) allows remote attackers to gain elevated privileges, potentially administrator-level, on affected WordPress sites. The vulnerability carries a CVSS 3.1 base score of 9.8 (critical) and per the vector requires no authentication or user interaction. No public exploit code has been identified at the time of analysis, but the low deployment footprint of the plugin may limit widespread exploitation.
Broken access control in HCL iControl (CVSS 3.1 score 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) allows a low-privileged authenticated user to bypass authorization checks or manipulate object identifiers directly, resulting in privilege escalation and unauthorized modification or deletion of sensitive application data. Because the exploit requires a valid low-privilege account (PR:L), an unauthenticated external attacker cannot exploit this despite the 'Authentication Bypass' tag on the report, but any user with even minimal credentials can escalate to full confidentiality, integrity, and availability impact without user interaction. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; prioritization should focus on environments where low-privilege accounts are broadly provisioned or externally reachable.
Privilege escalation in Ghost CMS (versions 2.21.0 before 6.56.0) allows an authenticated low-privilege staff user to elevate their role to a higher-privilege staff position by exploiting missing authorization checks in the notifications system. Exploitation requires an existing staff account and passive interaction from a higher-privileged user (CVSS 4.0 PR:L/UI:P), so multi-author or multi-staff deployments are primarily at risk; single-author sites have negligible exposure. A vendor patch is available in Ghost 6.56.0, and no public exploit code has been identified at time of analysis.
Privilege escalation in JetBrains YouTrack lets an authenticated holder of an already-high-privilege (non-admin) account raise their effective permissions by abusing the user group links functionality, where a required authorization check is missing (CWE-862). All YouTrack releases before 2026.2.19422 are affected, and the issue is scored CVSS 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact once triggered, requiring no user interaction. The PR:H prerequisite meaningfully bounds exposure - anonymous or fully unprivileged users cannot exploit it - and there is no public exploit identified at time of analysis, making this a real but gated finding rather than an urgent fire-drill.
Authenticated privilege escalation in WPC Shop as a Customer for WooCommerce (versions up to and including 2.0.0) enables any logged-in user to take over an Administrator account by supplying the Administrator's user ID to the wpcsa_login endpoint, receiving a full Administrator session cookie without the Administrator's password. The flaw stems from missing role validation (CWE-269) before issuing a session, and WordPress user IDs are trivially enumerable. No public exploit code is identified at time of analysis, but the vendor-released patch 2.0.1 is available and this is assessed as a genuine high-priority vulnerability.
Authenticated attackers holding Subscriber-level (or higher) WordPress accounts can escalate themselves to Administrator on any site running the ByteCoreStack - MCP Connector for AI Tools plugin through version 1.2.3, because the plugin's `wp_update_user_meta` MCP tool protects only `user_pass`, `user_activation_key`, and `session_tokens` while leaving `wp_capabilities` and `wp_user_level` writable. A single JSON-RPC call to the plugin's OAuth-gated MCP endpoint, targeting the attacker's own user ID with `key=wp_capabilities` and a role array such as `{"administrator": true}`, changes the account's role on the next request; no user interaction is required and the CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the low privilege prerequisite makes this high-priority wherever self-registration is open.
Unauthenticated attackers can create WordPress administrator accounts on any site running the Super Forms - Drag & Drop Form Builder plugin up to and including version 6.3.316 whenever the Register & Login add-on is active and a registration form using register_login_action='register' is published, because the add-on accepts a client-supplied 'role' parameter and passes it straight into wp_insert_user(). With a CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) the flaw yields full site takeover, but exposure is conditional: the required public registration form must exist, and sites using Super Forms only for contact or other non-registration forms are not affected. No public exploit code has been identified at time of analysis, and an upstream fix is available via GitHub pull request #205, though a released patched version is not independently confirmed in the available data.
Improper privilege management in Genian SSL PNS (the Frodo-Core and Watchcat-UI components) lets an authenticated administrator who can run CSV bulk user registration escalate to super administrator and then force the creation of an operating-system-level account by manipulating the permission column of the uploaded CSV. The issue is classified as CWE-269 and scored 7.5 by the reporting CNA under CVSS 4.0 (AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L), which shows the attack is network-reachable but requires a pre-existing high-privileged account and a non-default attack precondition (AT:P) tied to deployments that actually expose the bulk-registration import workflow. No public exploit code has been identified at time of analysis and there is no evidence of active exploitation; the vendor has published an advisory (GHSA-8mjh-295r-5hf2) covering both affected components.
Local privilege escalation in Kiteworks Core lets an attacker who already holds code execution as an unprivileged backend service account invoke a privileged routine that mishandles attacker-influenced input, running arbitrary OS commands as root. The flaw requires a prior local foothold on the appliance - the CVSS vector (AV:L, PR:L, UI:N) confirms it cannot be reached directly over the network and demands an existing initial compromise or misconfiguration to obtain the service account. No public exploit code or active exploitation is identified at time of analysis, and the realistic risk is bounded by how easily that initial service-account access can be obtained on a given deployment; the vendor's advisory is GHSA-658c-86vw-g9hf.
Local privilege escalation in Kiteworks Core lets an attacker who already has code execution as an unprivileged backend service account on the appliance obtain root. A privileged, root-owned routine consumes a filesystem path that the lower-privileged service account can influence, so the attacker can steer that root operation into executing arbitrary commands with full privileges (CWE-59 link-following / unsafe path handling). The attack is local-only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and is a second-stage primitive requiring an existing foothold; no public exploit was identified at time of analysis and the CVE is not reported as confirmed actively exploited (CISA KEV), though the 7.8 severity and availability of a vendor advisory make prompt patching advisable.
Local privilege escalation in Kiteworks Core allows an attacker who already holds a shell under a low-privileged service account to elevate to root on the appliance, gaining complete control of the system and the sensitive content it brokers. The weakness is a link-following issue (CWE-59) in a root-privileged operation, reachable with local access as the service account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), no user interaction, and no non-default configuration, making it a realistic second-stage escalation after a separate initial-access compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the CVE is not associated with a KEV listing; the primary limiting factor is the prerequisite service-account foothold, while the primary risk is full root compromise of the appliance.
Command injection in Kiteworks Core's internal cluster-management function allows an attacker who already has code execution on one node of a clustered deployment to run operating system commands with elevated privileges on other nodes in the same cluster. The vulnerable function is not reachable from outside the cluster, so the attack path is confined to the internal cluster network and requires a pre-existing foothold on a cluster member; single-node deployments are not exposed. Rated CVSS 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) with scope change reflecting cross-node impact, and no public exploit identified at time of analysis.
Improper privilege management in Kiteworks Core before 9.5.0 allows an authenticated administrative user who holds only limited, non-Sysadmin role-management permissions to grant another account full system-administrator (Sysadmin) rights that the grantor was never authorized to confer. The flaw sits in the role-assignment logic, which fails to constrain grantable privileges to the subset the granting administrator actually possesses, so a single delegated-admin session is enough to escalate a chosen account to the highest privilege level. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2) the attack is network-reachable with no user interaction but requires an already-authenticated high-privilege session; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV). This is best characterized as a genuine but access-gated integrity risk whose real-world exposure depends on how many delegated administrators exist in a deployment and how tightly their role scopes are managed.
Local privilege escalation on Reachy Mini Wireless robots running OS images built from pollen-robotics/reachy-mini-os prior to v0.2.4, where a sudoers entry granted the low-privileged pollen daemon user (uid 1000) passwordless root access to /usr/bin/systemctl with no subcommand or argument restriction. Any code already executing as pollen - for example through a compromised reachy daemon - can escalate to full root (uid 0) without user interaction or a TTY, because systemctl can be pointed at an attacker-supplied unit file whose ExecStart runs as root. Rated CVSS 3.1 7.8 HIGH (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), confirmed by the vendor advisory GHSA-7rhg-9v48-x3h2 and closed by release v0.2.4; no public exploit code or CISA KEV entry was identified at time of analysis, and exploitation requires an existing foothold as the pollen user on an unpatched image.
Local privilege escalation in Zammad lets an attacker who already controls the unprivileged 'zammad' service account elevate to root on the host, affecting every release from 1.5.0 up to but not including 7.1.0-alpha (including the then-current alpha). The vendor labels this critical with a CVSS 4.0 score of 9.4 and a network/unauthenticated-looking vector (AV:N/PR:N, E:A), but the description confines the attacker to an already-present local/service-account context; our independent assessment therefore re-scores it as CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, i.e. a high-impact but post-foothold escalation rather than a pre-auth remote compromise. No public exploit code has been identified at time of analysis, and CVE-2026-102490 does not appear in CISA KEV, so the vendor vector's E:A exploit-maturity metric cannot be corroborated here.
Privilege escalation in Internet2 Grouper before 7.5.1 allows authenticated users with delegated rule creation or editing permissions in the User Interface to elevate their privileges, but only in certain configurations. This flaw (CWE-266) requires a non-default configuration and pre-existing authorization, moderating the headline critical severity; the attack is of high complexity per our independent assessment, and no public exploit identified at time of analysis. Upgrading to version 7.5.1 resolves the issue.
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
Privilege escalation in the SureCart WordPress plugin through version 4.7.2 allows an authenticated user who holds the limited 'Shop Worker' store-staff role to elevate to full administrator-level control of the WordPress site. The flaw is a case of incorrect privilege assignment (CWE-266) inside a SureCart operation, and because the assessed vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, no user interaction or special conditions are needed once the Shop Worker role is held - making it a straightforward path for a malicious insider or anyone who has compromised a shop-staff credential. Anonymous or self-registering visitors cannot reach the flaw; there is no public exploit identified at time of analysis.
Privilege escalation in the Vitepos WordPress point-of-sale plugin through version 3.5.0 lets an authenticated account that already holds a custom or elevated Vitepos role - such as POS staff or manager - raise its own privileges to a higher level on the affected site, rated CVSS 7.2 (High). Exploitation is remote and low-complexity with no user interaction required once such an account exists, but the high-privilege prerequisite (PR:H) means anonymous visitors and ordinary subscriber-level users cannot trigger it, and only WordPress sites with the Vitepos plugin installed and active are exposed. No public exploit code has been identified at time of analysis, and the issue is reported by Patchstack as an improper privilege assignment (CWE-266) defect in the plugin's custom role handling.
Privilege escalation in the Estatik WordPress plugin (versions through 4.3.5) allows an authenticated Subscriber-level account to elevate its privileges to higher roles, potentially achieving full site compromise. Although the published CVSS 3.1 vector lists PR:N (score 9.8), the independent assessment and the 'Subscriber Privilege Escalation' description confirm that a Subscriber account is required; such an account is trivially obtainable when open user registration is enabled, common on real-estate or listing sites. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Privilege escalation in the WordPress plugin Import and Export Users and Customers (Javier Carazo) at versions up to and including 2.5.2 lets an authenticated low-privileged account - specifically a Subscriber - reach higher-privileged roles, giving full compromise of the site's confidentiality, integrity, and availability (CVSS 3.1 base 7.5, High). The advisory-supplied vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H means the attack is network-reachable and needs no victim interaction, but the High Attack Complexity rating reflects a non-trivial precondition (a specific plugin state, ordering, or crafted import payload) that limits how reliably it can be pulled off; it does require the attacker to already hold a Subscriber account, which is trivial on sites with open registration enabled. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so exploitation is currently assessed as a targeted-risk rather than a mass-scanning risk; no EPSS probability was supplied with this record.
Privilege escalation in MISP before 2.5.48 allows an authenticated user who holds the tag editor permission (perm_tag_editor) to smuggle sibling User and Organisation records into tag collection create or edit requests, which the affected controller then persists alongside the intended tag collection - letting the attacker create or modify accounts and escalate to site administrator. Exploitation requires network access to the instance and a delegated tag-editor role; no user interaction or administrative rights are needed, and the accompanying source fix (commit 96f735e7b) shipped in MISP 2.5.48. No public exploit code was identified at time of analysis, and instances that never delegate perm_tag_editor to non-administrative accounts are not exposed to an unprivileged external actor.
Privilege escalation in the WP User Frontend WordPress plugin before 4.3.12 lets unauthenticated visitors tamper with the role value submitted by the plugin's front-end registration form and create an account with elevated privileges such as Editor (the administrator role cannot be obtained this way). The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms unauthenticated remote exploitation with no user interaction, but the AC:H reflects a narrow environmental precondition: the site must run on a PHP build where the sodium (libsodium) extension is unavailable, and a public registration page must be configured through the plugin. No public exploit code has been identified at time of analysis, and the SSVC assessment records Exploitation: none; impact is scored High for confidentiality and integrity with no availability effect.
Local privilege escalation to root in Pexip Infinity (versions before 38.2, plus 39.0, 39.1, and 40.0) allows an attacker who already holds a foothold on a node to break out of a low-privileged local context and obtain full root control. Per the CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8), the flaw is local-only, requires low privileges, and is not remotely exploitable on its own: the attacker must first run arbitrary code on the node, either by chaining a separate remote code execution vulnerability or by already possessing administrative access to the node's operating system. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); the practical risk is that this bug turns any successful initial compromise of a Pexip Infinity host into a complete root compromise, so it should be treated as a meaningful post-exploitation escalation rather than a standalone remote threat.
Sandbox escape in Google Chrome on Windows prior to 154.0.8037.92 allows a local attacker to execute arbitrary code outside the browser sandbox through improper privilege management in the Mojo IPC layer. Exploitation requires local access to a Windows host and some user interaction (UI:R) but no authentication (PR:N), and it functions as a second-stage capability: an attacker who already holds a sandboxed foothold, such as a compromised renderer, can leverage the flaw to reach the full privileges of the browser process, yielding high confidentiality, integrity, and availability impact with a scope change. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the EPSS-style risk signal is low; non-Windows Chrome builds are unaffected because the defect is Windows-specific. A vendor patch is available in Chrome 154.0.8037.92.
Local privilege escalation in the npm package adm-zip through version 0.6.0: when an application extracts an archive with the non-default keepOriginalPermission=true option, the library copies the Unix permission bits recorded in each zip entry's external file attributes straight to disk via fs.chmodSync() without stripping the setuid (0o4000), setgid (0o2000) or sticky (0o1000) bits. An attacker who can supply a zip - no special access needed to craft one - can therefore plant a 04755 root-owned binary whenever the extraction runs as root (the common Docker-build, CI-runner and privileged-install posture where this flag is used), and the attacker's code executes as root once a lower-privileged user later runs that file. The issue is correctly rated Medium despite a 7.1 CVSS score because it is highly conditional (flag enabled, root extraction, setuid file preserved and executed by another user); confirmed actively exploited: no - not in CISA KEV - but a working proof-of-concept (a Python-crafted zip with external_attr 0o4755 << 16) is documented in the vendor advisory. Default usage with the flag off, or extraction as a non-root user, is not exploitable.
User-mode-to-kernel privilege escalation in Eclipse ThreadX lets a loaded, memory-protected TXM module register an arbitrary function pointer as the global trace-full callback, which privileged kernel code then invokes directly with no pointer validation and no privilege-dropping trampoline when the trace buffer wraps. Affected builds are those compiled with the non-default TX_ENABLE_EVENT_TRACE option and running modules in TXM_MODULE_USER_MODE with TXM_MODULE_MEMORY_PROTECTION; an invalid pointer crashes the kernel (denial of service), while a pointer into the module's own code has been observed executing with kernel privilege (CONTROL.nPRIV = 0), producing a scope-crossing compromise of the RTOS kernel by a local, low-privileged attacker. Exploitation requires the attacker to already control executing code inside a loaded module plus the non-default trace build flag, and no public exploit code has been identified at time of analysis.
Privilege escalation in the Electron framework lets a <webview> guest grant itself Node.js integration inside its Web Workers even when the embedding (embedder) application has Node integration turned off, so untrusted guest content can obtain a more privileged JavaScript execution context than the host application intended to allow. Affected releases are npm/electron before 41.10.6, 42.x before 42.9.2, 43.x before 43.4.1, and 44.0.0-alpha.x before 44.0.0-beta.5 (CPE cpe:2.3:a:electron:electron). Exploitation is not automatic: the independent assessment requires a non-default deployment where the app enables the <webview> tag, runs the embedder unsandboxed with nodeIntegration disabled, and loads attacker-controllable content into the guest - applications that never enable <webview>, keep the embedder sandboxed, or only load trusted first-party content are unaffected. There is no public exploit identified at time of analysis (CISA SSVC: Exploitation none, Automatable no, Technical Impact total) and EPSS is low at 0.45% (37th percentile), although the underlying privilege boundary is a total-compromise class issue where it applies; the NVD-style vector scores 9.8, while our independent assessment reflects the higher attack complexity and changed scope (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) imposed by those preconditions.
Local privilege escalation in TeamViewer Full Client and Host for Windows (versions prior to 15.82) lets an authenticated low-privileged local user escalate to NT AUTHORITY\SYSTEM by winning a time-of-check-to-time-of-use race against the elevated installer's rollback routine. The attacker must already hold a low-privileged account on the host and must wait for a specific runtime event - a rollback actually occurring during a TeamViewer installation or update - after which they overwrite rollback backup files staged in a user-writable temporary directory before the elevated installer restores them; the assessed attack complexity is High (CVSS:3.1/AV:L/AC:H/PR:L/UI:R), so success is probabilistic and depends on precise timing rather than being guaranteed on a single attempt. This is a legitimate but conditional local privilege escalation: it cannot be triggered remotely, it requires a local account plus an installer/update action (UI:R), and no public exploit code or confirmed active exploitation has been identified at time of analysis. The vendor-released fix is TeamViewer Full Client and Host 15.82.
Local privilege escalation in TeamViewer Full Client and Host on Windows, Linux, and macOS (all versions prior to 15.82) allows an authenticated low-privileged local user to write arbitrary files with SYSTEM/root privileges by sending crafted IPC commands to the locally running privileged TeamViewer service daemon. Successful exploitation yields full compromise of confidentiality, integrity, and availability on the host (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and because the flaw is deterministic rather than a race condition it is reliably triggerable once local access exists. No public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); however, the requirement of only low-privileged local access makes it a valuable post-compromise escalation primitive.
Privilege escalation in Mozilla Firefox's Places component lets a remote attacker reach elevated, normally chrome-restricted functionality inside the browser when a victim opens attacker-controlled web content in an affected build. Affected releases are Firefox versions before 157 and Firefox ESR versions before 153.4, rated 8.8 under CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, which means no attacker-side authentication or privileges are required but the victim must be induced to interact with a crafted page, after which confidentiality, integrity and availability impact is total within the affected security scope (CWE-269 improper privilege management). There is no public exploit identified at time of analysis and no CISA KEV entry; CISA SSVC rates exploitation as "none" and the attack as not automatable, so this is a serious browser flaw rather than a current worm or mass-exploitation emergency, and it is fully resolved by updating to Firefox 157 or Firefox ESR 153.4.
Privilege escalation in the Mozilla Firefox Address Bar component lets a remote, unauthenticated attacker gain elevated privileges within the browser by persuading a victim to load and interact with attacker-controlled web content. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) confirms no credentials are needed but the attack cannot succeed without the targeted user interacting with the malicious page, and CISA's SSVC assessment marks the issue as not automatable with no observed exploitation. No public exploit code or confirmed active exploitation has been identified at time of analysis; the flaw is remediated in Firefox 157, Firefox ESR 153.4, and Firefox ESR 140.17, so only unpatched installations prior to those builds remain exposed.
Privilege escalation in Mozilla Firefox's DOM: Service Workers component allows a remote, unauthenticated attacker (CVSS vector PR:N) to elevate privileges inside the browser after convincing a victim to visit an attacker-controlled or compromised page (UI:R), affecting Firefox builds before 157 and ESR branches before 153.4 and 140.17. The 8.8 score derives from high confidentiality, integrity, and availability impact with low attack complexity, but scope is unchanged (S:U), meaning the impact stays confined to the browser's own privilege boundary rather than escaping to the host operating system. There is no public exploit identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no, so practical exposure is driven by how quickly the supplied ESR/rapid-release fixes are deployed rather than by observed attack activity.
Privilege escalation in the DLL Services component of Mozilla Firefox allows an attacker to achieve elevated code execution - with high confidentiality, integrity, and availability impact - when a victim renders attacker-controlled web content, reflected in a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No authentication is required (PR:N) and attack complexity is low, but the vector mandates user interaction (UI:R), meaning a target must be induced to load a crafted page rather than being compromised by a service-side drive-by. The issue is fixed in Firefox 157, Firefox ESR 153.4, and Firefox ESR 140.17, so unpatched pre-157 and pre-ESR builds are the exposed population; there is no public exploit code and no observed exploitation at time of analysis, and SSVC classifies the flaw as non-automatable.
Use-after-free in Mozilla Firefox's Graphics: WebRender compositor lets remote, unauthenticated attackers corrupt memory and escalate privileges inside the browser when a victim loads attacker-controlled web content - no authentication is required (PR:N), but the attack is not server-side passive and depends on the target visiting or interacting with a malicious or compromised page (UI:R). The flaw rates CVSS 3.1 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and was fixed in Firefox 157 and in Firefox ESR 153.4, ESR 140.17, and ESR 115.42; no public exploit code has been identified and CISA's SSVC assessment records exploitation as none, so this is a genuine but not urgent priority. Modern Firefox content-process sandboxing further limits post-corruption impact unless the attacker chains a separate sandbox escape, and WebRender is enabled by default, so no unusual configuration is needed to reach the vulnerable path.
Boundary-condition errors in Mozilla Firefox's Graphics component allow an unauthenticated remote attacker to trigger memory corruption and achieve privilege escalation on the affected platform, provided the victim loads attacker-controlled content that reaches the vulnerable rendering code path. Only builds below Firefox 157, Firefox ESR 153.4, Firefox ESR 140.17, and Firefox ESR 115.42 are affected - updating to any of those versions fully remediates the issue. Although the CVSS base score is 8.8 with high confidentiality, integrity, and availability impact, no public exploit code has been identified at time of analysis, CISA's SSVC assessment rates exploitation as 'none' and the flaw as not automatable, and the mandatory user-interaction requirement (UI:R) prevents automated or wormable spread, making this a genuine but not top-priority issue.
Privilege escalation in Mozilla Firefox versions prior to 157 arises from incorrect boundary conditions in the Graphics: WebGPU component, a CWE-119 buffer-bounds flaw that a remote, unauthenticated attacker can trigger when a victim loads attacker-controlled web content. Exploitation depends on user interaction (UI:R) - typically visiting a malicious or compromised page - and is rated CVSS 8.8 with high confidentiality, integrity and availability impact, though scope is unchanged (S:U) so the effect is confined to Firefox's content process rather than the host operating system. No public exploit code was identified and CISA's SSVC assessment records Exploitation: none, so this is a mid-to-high priority browser patch rather than an emergency; the issue is fixed in Firefox 157.
A use-after-free in Mozilla Firefox's Graphics: WebGPU component (CWE-416) lets a remote attacker who gets a victim to render attacker-controlled web content corrupt memory and potentially achieve code execution in the browser's process, earning a High-severity CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). All Firefox builds prior to 157 are affected, and Mozilla fixed the issue in Firefox 157 (advisory mfsa2026-97, Bugzilla 2059020). No public exploit code or confirmed active exploitation has been identified at time of analysis, and because the vector requires user interaction, mass automated exploitation is unlikely, though per-target heap grooming is needed for reliable execution.
Local privilege escalation in Ghostscript for Windows (all versions prior to 10.08.0) allows any authenticated local user to plant a malicious PostScript resource file in the predictable C:\gs\ path, which Ghostscript then auto-loads with the privileges of whichever principal next invokes it. The hijack requires no special Ghostscript configuration because it abuses Windows default ACLs that let authenticated users create directories at the root of C:\, and it succeeds only while C:\gs\ is unpopulated - the default state on Windows installations; execution is passive and fires when a user or service subsequently runs Ghostscript, with the payload's privilege gain bounded by that invoking principal (assessed as scope-changed impact). No public exploit code has been identified at time of analysis, and the issue, reported by CERT-PL, is fixed in 10.08.0.
Privilege escalation in FastAdmin (versions 1.6.1.20250430 and 1.6.5.20260602) lets an attacker who already holds an authenticated administrator session manipulate the Database Management component via application/database.php so that code runs with privileges beyond those intended, resulting in full compromise of confidentiality, integrity, and availability of the affected instance. Exploitation is network-reachable but heavily gated: the assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:R, score 7.1) requires high privileges and user interaction, so an unauthenticated attacker against a default install cannot trigger it directly. Publicly available exploit code exists and is referenced in a public GitHub issue, though there is no KEV confirmation of active exploitation; the EPSS-style exploit maturity flag in the CVSS 4.0 vector (E:P) reinforces that a working proof of concept is circulating.
Improper privilege management in RaspAP WebGUI through 3.5.5 lets an authenticated low-privilege web-UI user escalate to root by manipulating how the plugin installer writes sudo configuration entries through PluginInstaller::addSudoers (src/RaspAP/Plugins/PluginInstaller.php). Exploitation is remote and unauthenticated attempts are not possible - the attacker must already hold a valid RaspAP panel session (CVSS 4.0 PR:L, independently assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N, C:H/I:H/A:H) - but no user interaction or unusual complexity is required beyond that. Publicly available exploit code exists (a GitHub gist demonstration was published alongside the VulDB entry), and the vendor was contacted but did not respond, so no vendor-released patch has been identified at time of analysis; this is a genuine high-impact issue but not an emergency, with exposure concentrated on panels reachable from untrusted networks or protected only by default credentials.
Privilege escalation in SUSE Rancher Fleet (0.14.x before 0.14.11, 0.15.x before 0.15.7, and 0.16.x before 0.16.2) lets a low-privileged tenant - an authenticated user able to push a Fleet Bundle or GitRepo - have resources written to a shared downstream cluster under the Fleet agent's own cluster-admin credentials rather than the ServiceAccount pinned to the deployment, allowing that tenant to overwrite configuration owned by other tenants. Exploitation is gated by topology: it only matters in multi-tenant Fleet deployments where privileged and untrusted teams share the same downstream cluster, since single-tenant or per-tenant-isolated clusters have no crossed trust boundary. Rated 8.8 by the vendor (the independent assessment scores it higher, 9.9, because the trust boundary crossing changes scope); no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis.
Local privilege escalation in Extegrity Exam4 on macOS lets any unprivileged local user escalate to full root by abusing command injection in the root-running com.extegrity.LogTool privileged helper, which is reachable over XPC. An attacker with a low-privileged local session (PR:L, AV:L, no user interaction required, UI:N) can send crafted XPC messages that reach [ConsoleLogHelper copyConsoleIntoFileFromStartDate:], where attacker-controlled parameters are passed into a syslog command without sanitization and executed with root privileges via LaunchSynchronous, yielding complete confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, HIGH). Exploitation requires the helper to be installed, registered, and reachable on the host; remote exploitation is not possible, and no public exploit code was identified at time of analysis.
Authenticated privilege escalation in Nezha Dashboard before 2.3.5 lets any account holding the nezha:service:write scope escalate into privileged Agent operations by creating or updating a service monitor whose Task.Type is set to a command or configuration task value, since the service API never validated that the submitted type belonged to the supported probe set. Because service monitors and privileged operations share the same protobuf Task.Type integer namespace, the crafted task is accepted and dispatched to Agents within the attacker's existing authorization scope, resulting in command execution or Agent reconfiguration (CWE-269). The independent assessment rates this as a genuine but authentication-gated privilege-escalation issue whose urgency is moderate and whose blast radius scales with how broadly service:write is delegated; the vendor has released a fix in 2.3.5 (commit 38824dbc11a63964c5b9296ae4c68e62b34fa04b) and no public exploit has been identified at time of analysis.
Privilege escalation in Elastic Kibana's Agent Builder feature lets an authenticated non-administrative user who can edit a shared agent cause privileged operations to run under the identity of a higher-privileged user who later interacts with that agent (CWE-441 confused deputy). Rated CVSS 7.3 High (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N), the flaw requires the Agent Builder feature to be enabled with at least one shared agent, the attacker to hold edit privileges on it, and a privileged victim to interact with the tampered agent; if the attacker can also author workflows, escalation to full Kibana and Elasticsearch cluster administrative control is possible. No public exploit identified at time of analysis, and vendor patches are available in Kibana 9.4.7 and 9.5.0.
Privilege escalation in the WordPress plugin Groups - Memberships and Access Control (itthinx) affects all versions up to and including 4.6.0, allowing any authenticated Subscriber-level user to self-enroll in arbitrary groups - including privileged admin groups - and ultimately mint a group that grants every registered WordPress capability, reaching Administrator. The root cause is an authorization check in groups_join() that reads the ambient post's author capabilities ($post->post_author) instead of the acting user's, while the same response hands the caller a valid join hash and nonce; an attacker only needs valid low-privilege credentials and the post ID of any Administrator-authored post, supplied via the post_ID parameter of the authenticated wp_ajax_parse_media_shortcode AJAX handler, with no victim interaction. Per available intelligence there is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, though our independent assessment rates this a genuine high-priority issue rather than a high-CVSS-but-low-real-risk case, given the low bar of Subscriber self-registration on many sites.
Froxlor through 2.3.10 fails to enforce the mail.allow_external_domains policy in the EmailSender.add API command, letting an authenticated customer with API access register an arbitrary external sender address for their mailbox even when the administrator has explicitly disabled external allowed-sender domains. The bypass only matters when the administrator has enabled the allowed-sender feature (mail.enable_allow_sender=1) while disabling external domains (mail.allow_external_domains=0), and the sender-spoofing impact materializes only if the generated mail configuration consumes the allowed-sender table; there is no public exploit identified at time of analysis, and exploitation requires valid low-privilege API credentials rather than being unauthenticated. A vendor-released patch is available in Froxlor 2.3.12, and our independent assessment rates this as a genuine but modest-severity authorization/policy-enforcement flaw rather than a high-urgency one.
Privilege escalation in Kyverno before 1.19.1 allows an authenticated Kubernetes namespace tenant with Policy/apiCall authoring rights to escape namespace isolation and create objects as Kyverno's admission-controller ServiceAccount. The attacker supplies percent-encoded directory-traversal sequences in the Policy apiCall urlPath to bypass the per-namespace clamp, enabling creation of cluster-wide MutatingWebhookConfiguration objects or PolicyException objects in the kyverno namespace, with a path to cluster-admin escalation. No public exploit identified at time of analysis; vendor patch available in 1.19.1.
Authenticated privilege escalation in Budibase Server before 3.45.0 lets a low-privileged 'builder' account grant itself administrative roles in other workspaces. The flaw resides in the POST /api/global/groups/:groupId/apps endpoint, which fails to validate per-app authorization, allowing a builder who only has rights in one workspace to rewrite user-group role mappings for applications outside their own tenant boundary. Because the CVSS vector requires PR:L and no user interaction, exploitation is limited to authenticated builders, and a single-workspace or single-tenant instance offers no cross-boundary target; the raw 8.6 score therefore overstates the immediate threat even though the underlying authorization defect and its escalation impact are genuine. There is no evidence of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, though a vendor patch is available in 3.45.0.
Privilege escalation in Grav CMS 2.0.14 through 2.0.24 allows an authenticated backend operator who already holds the admin.users permission - but not admin.super - to grant super-admin rights to their own account or to a group they belong to via the flex accounts backend. The bypass works because the security guard is resolved against a field's exact blueprint path, so a crafted flat dot-notation key such as access.admin.super evades the rule match and is later reconstructed into a genuine nested value when the object is saved. No public exploit code has been identified at time of analysis, and because the attacker must already possess privileged but non-super backend access, this is an insider or post-compromise escalation vector rather than a remote unauthenticated one - but the resulting super-admin control over configuration, plugin and theme installation, the file manager, and all accounts makes it a genuine, high-value escalation rather than a high-CVSS-but-low-real-risk issue.
Privilege escalation in Capgo (capgo.app) before 12.267.1 allows a principal holding the apikey_manager role to rotate a higher-privileged same-owner sibling API key - such as an org_super_admin key - via the API key rotation PUT endpoint and retrieve the replacement plaintext secret, giving the attacker the credentials of the stronger principal. Exploitation is authenticated: the attacker must already possess or have compromised an apikey_manager key, and a more privileged sibling key under the same owner must exist, which limits exposure to organizations that delegate key-management duties to lower-trust roles. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; a vendor fix is available in 12.267.1.
Vertical privilege escalation and account takeover in Capgo (capgo.app) through 12.261.0: an authenticated attacker who already holds the org_admin tier permission org.update_settings can rewrite the provider_id column of a public.sso_providers row over PostgREST and point the organization's email-domain trust anchor at an identity provider they control, after which the server-side SSO merge routine binds the attacker's identity to the legitimate org owner account, nulls that account's password, and deletes its other identities and sessions. The impact is full owner/super_admin takeover plus lockout of the real owner, although exploitation is gated on the target organization having an active SSO provider configured and on the attacker already possessing org_admin in that organization; no public exploit code was identified at time of analysis and there is no CISA KEV entry. The incomplete nature of the fix (a BEFORE UPDATE guard that freezes dns_verified_at, domain, status and enforce_sso but leaves provider_id, metadata_url and attribute_mapping writable under a table-wide ALL grant with only row-scoped RLS) makes this a durable privilege-escalation path rather than a one-off misconfiguration.
Privilege escalation in the Capgo capgo.app backend (versions ≤ 12.261.0) lets an authenticated user who holds only the apikey_manager organization role mint API keys bound to higher-privileged deploy roles (app_developer, app_uploader, channel_developer, channel_uploader). Those keys can in turn be used to push arbitrary over-the-air JavaScript updates to every end user of the organization's apps, giving an insider or delegated-role holder unauthorized write access to production app content. Exploitation requires a valid JWT session and the apikey_manager role (authenticated, no user interaction), no public exploit code was identified at time of analysis, and the issue is not listed in CISA KEV; at advisory publication no patched version was available.
OpenClaw Codex before 2026.7.1 fails to properly enforce owner authorization for native conversation bindings, allowing a non-owner channel sender who already holds command access to bind to the Codex runtime and execute host-capable turns with access to files, tools, and processes. This privilege escalation (CWE-269) has a CVSS 4.0 score of 8.7 (High) and is network-reachable with low complexity and low privileges, but it requires the attacker to already have command access on a channel-a fully external attacker cannot trigger it. No public exploit code or active exploitation was identified at time of analysis.
OpenClaw Gateway before 2026.7.1 fails to restrict owner-only infrastructure tools exposed through the chat.send endpoint, allowing an authenticated write-scoped non-owner caller to cause the agent to invoke owner-only configuration or scheduling operations, including persistent state changes. This privilege escalation (CWE-269) affects Gateway deployments using authentication modes that honor caller identity and narrower operator scopes, and where agent tool policies include the `gateway` and `cron` tools; shared-secret token and password callers are treated as fully trusted and are out of scope. No public exploit code identified at time of analysis; the vendor CVSS 4.0 score is 7.2 with integrity impact dominant.
Privilege escalation and privilege retention in InvoicePlane prior to 1.7.2 allow a previously-authenticated administrator whose account was downgraded or deactivated by another administrator to keep operating with administrative rights through a stale session. Because Admin_Controller trusts the user_type value cached in the session at login rather than re-reading ip_users.user_type, the downgraded user's live session continues to authorize admin requests, and the attacker can then call Users::form() to write user_type back to 1, making the restored admin role persistent in the database. Exploitation is limited to multi-administrator deployments where a role change occurs while the target session stays alive; it requires prior high-privilege access and is not reachable by an unauthenticated or ordinary low-privilege user, and no public exploit code or active exploitation has been identified at time of analysis. The vendor-released fix is InvoicePlane 1.7.2.
Improper privilege management in Zammad helpdesk/customer support systems allows an attacker holding a valid but deliberately restricted API token to create new administrator accounts, inheriting the latent authorization authority of the token's parent account instead of honoring the token's granular scope. This affects all Zammad releases prior to 7.0.2 and 7.1.0, and exploitation is authenticated (CVSS PR:L) since a scoped token must already be held, though no user interaction is required and the vector is network-reachable; success grants full access to tickets, customers, and configuration and effectively hands the attacker complete control of the instance. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but the independent assessment rates it a genuine high-priority privilege-escalation flaw rather than a high-CVSS-but-low-risk case, and EPSS-style risk is elevated by the trivial post-exploitation payoff.
Privilege escalation in the Seclore FileSecure Desktop Client affects Windows hosts running any client version before 3.25.1.0, where an authenticated local user can abuse an improper access control weakness in the product's kernel-mode driver to obtain NT AUTHORITY\SYSTEM. The flaw is rated CVSS 3.1 7.8 HIGH (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-269) and is strictly a post-authentication escalation - it cannot be used for initial access or network exploitation and requires an existing low-privileged session on the vulnerable host. There is no public exploit identified at time of analysis and no CISA KEV listing; SSVC records Exploitation: none, so the operational risk is concentrated in insider-threat and post-compromise scenarios rather than mass exploitation. A vendor-released patch is available in version 3.25.1.0.
Local privilege escalation in Google Android 14, 15, 16, 16-qpr2, and 17 lets a low-privilege app bypass permission checks through a confused-deputy flaw in the dialInternal code path, allowing the app to perform permission-protected actions it should not be able to perform. Exploitation requires a local foothold - the attacker must already be running code as a low-privilege app (PR:L) - but needs no user interaction (UI:N) and offers no remote attack surface (AV:L), making this a credible but not emergency-priority risk. There is no CISA KEV entry and no public exploit identified at time of analysis; patched builds from the October 2026 Android Security Bulletin are not vulnerable.
Local privilege escalation in Google Android 16, 16-qpr2, and 17 arises from improper input validation in the Bluetooth snoop logger's FilterCapturedPacket routine (snoop_logger.cc), which can corrupt memory when malformed packet data is processed. Exploitation requires a low-privileged local app or process already running on the device (CVSS vector shows AV:L/PR:L/UI:N), meaning an attacker must first obtain a foothold but needs no user interaction and no additional execution privileges to escalate to full confidentiality, integrity, and availability impact. There is no public exploit code and no confirmed active exploitation (CISA SSVC exploitation value: none; not in KEV, no POC identified), but a fix is available through the Android Security Bulletin dated 2026-10-01, so this should be treated as a genuine, second-tier patch-priority issue rather than an emergency.
Local privilege escalation in Google Android 14, 15, 16, 16 QPR2 and 17 is possible through an out-of-bounds write in the qsort routine of libufdt_sysdeps_vendor.c, which occurs when the device-tree (ufdt) parsing path is driven into resource exhaustion with attacker-influenced input. An attacker who already holds a local, low-privileged foothold on the device - for example a malicious installed app or a process that can feed data into the ufdt parsing path (PR:L) - can trigger the flaw with no user interaction and no additional execution privileges, achieving high confidentiality, integrity and availability impact within the platform (CVSS 7.8). No public exploit identified at time of analysis, and the issue is addressed through the October 2026 Android Security Bulletin.
Local privilege escalation on Android 14, 15, 16, 16-qpr2, and 17 stems from an out-of-bounds read in MessageQueueBase.h caused by an incorrect bounds check, allowing an attacker with low-privilege local code execution to gain elevated privileges with high impact to confidentiality, integrity, and availability (CVSS 7.8). Exploitation requires a locally installed malicious or compromised app and no user interaction, and no public exploit has been identified at the time of analysis.
Local privilege escalation in Android's Bluetooth stack lets an app running with ordinary privileges corrupt control flow in the privileged Bluetooth process and inherit its elevated rights. The root cause is an uninitialized-pointer dereference (CWE-824) in handle_le_monitor_device_event of msft.cc, the Microsoft HCI vendor-extension handler, affecting Android 16, Android 16-qpr2 and Android 17 per EUVD. This is a second-stage escalation rather than a remote entry point: the attacker must already have local code execution and be able to reach the Bluetooth LE monitoring path (CVSS AV:L, PR:L, UI:N), and no public exploit code has been identified at time of analysis; Google addresses the issue in its October 2026 Android Security Bulletin.
Local privilege escalation in Google Android 14 through 17 (including 16 QPR2) lets a low-privilege local actor trigger an integer overflow inside the NFC Type 4 Tag read/write path (rw_t4t_update_file in rw_t4t.cc) that produces an out-of-bounds write, yielding code execution in a higher-privileged context. Per the assessed vector (AV:L/AC:L/PR:L/UI:N), the attacker must already have local code execution or app presence on the device but needs no user interaction, and exploitation requires attacker-controlled NFC Type 4 Tag data to reach the reader/writer code path on an unpatched build. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); the CVSS score is 7.8 and the practical constraint is the local-only attack vector, making this a genuine fleet-patching priority rather than an emergency.
An out-of-bounds write in Android's NFC Execution Environment (NFCEE) action handling code (nfa_nfcee_act.cc) lets a locally installed low-privilege application corrupt memory in the NFC stack and escalate to system-level privileges. Per the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, the attacker must already be able to run code on the device as a low-privilege app (PR:L) and the flaw is not reachable over the network (AV:L), with no user interaction required; devices running unpatched Android 16, 16-qpr2, or 17 builds are affected, while those with the October 2026 security patch are not. Exploitation is not observed in the field - SSVC records Exploitation:none and there is no KEV listing or public exploit code identified at time of analysis - and EPSS is low at 0.11% (1st percentile), so this presents as a genuine but non-urgent local privilege-escalation issue rather than a remotely exploitable emergency.
Local privilege escalation in Google Android 17 lets a locally installed, low-privileged application escape its sandbox and obtain system-level privileges by reaching the isSystem() routine in WifiPermissionsUtil.java, which fails to perform the required permission check (CWE-862). The flaw is rated CVSS 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), reflecting a changed-scope impact in which a compromised app in the application sandbox compromises the platform itself, with high confidentiality, integrity and availability effects and no user interaction required. An attacker must already have achieved local code execution on the device (for example through a malicious or trojanized app), and only Android 17 is listed as affected, so devices on other releases or on the October 2026 patch level are not exposed; no public exploit identified at time of analysis, and the issue is addressed through the Android Security Bulletin dated 2026-10-01.
Authenticated members of a Plane project - including users holding only the lowest GUEST role - can demote project Administrators and Members through the ProjectMemberViewSet.partial_update endpoint, stripping them of project control. The pre-1.3.0 authorization check only blocked assigning a role higher than the requester's own, so it silently allowed assigning a lower or equal role; the attacker cannot elevate themselves, but can degrade other members' access. The issue is fixed in Plane 1.3.0, and no public exploit code or confirmed active exploitation was identified at time of analysis (CVSS 8.1, EPSS not provided).
Plaintext logging of API keys in Plane (makeplane/plane) prior to 1.4.0 lets an authenticated low-privilege user who can read application logs harvest other users' long-lived API tokens and use them to escalate privileges, potentially including to administrative accounts. The vulnerable behavior is inherent to affected versions - the APITokenLogMiddleware component writes API keys into request/application logs in cleartext - and exploitation requires both a valid low-privilege account (CVSS PR:L) and visibility into the resulting log output; if logs are restricted to admins or shipped to a protected external sink, the realistic exposure narrows to insiders or anyone who can reach the log store. No public exploit code or confirmed active exploitation has been identified at time of analysis and no EPSS signal was supplied; overall this is a credible, moderately-high-priority issue rather than a drop-everything emergency, and it is fixed in Plane 1.4.0.
Privilege escalation in Progress Telerik Fiddler Classic for Windows (versions prior to v6.0.20262.10021) lets a local low-privileged attacker replace one of the application's external helper executables with a different, validly signed binary that passes the product's weak publisher-name allow-list check, causing Fiddler to launch attacker-chosen code - including elevated (Administrator) execution for the helper tools that request elevation. Exploitation is local and authenticated (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 7.9), requires write access to the installed helper binaries, and is gated on a user launching the affected tool and approving the elevation prompt without noticing the executable name changed; it is not remotely or unauthenticated exploitable, and there is no public exploit identified at time of analysis. The authoritative assessment rates this a moderate, locally-exploitable privilege-escalation flaw rather than a drop-everything priority, with the UI:R requirement and the need for a pre-existing local foothold being the main limits on real-world abuse.
Out-of-bounds kernel memory writes in the NXP GAU ADC driver (drivers/adc/adc_mcux_gau_adc.c) of Zephyr RTOS let a local user-mode thread that has already been granted the ADC device object corrupt memory beyond an undersized buffer it supplies to the adc_read()/adc_read_async() syscalls. Exploitation of the privilege boundary requires a Zephyr build with CONFIG_USERSPACE=y running on an NXP RW61x SoC with the GAU ADC devicetree node enabled; the attack vector is localized (CVSS 3.1 8.4, AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H) and the caller must already hold a device-object grant, but the scope change (S:C) and high integrity/availability impact reflect a genuine userspace-to-kernel privilege escalation path capable of kernel memory corruption or a crash. No public exploit code and no confirmed active exploitation were identified at time of analysis; builds without CONFIG_USERSPACE or on SoCs other than RW61x with the GAU ADC node enabled are not exposed to the privilege boundary and only suffer a silent overflow when the application itself passes an undersized buffer.
Out-of-bounds write in MediaTek's 'vdec' hardware video-decoder path allows remote escalation of privilege on a broad set of affected MediaTek SoCs - including MT6768, MT6833, MT8186, MT8195 and MT6877 - when a victim opens or plays attacker-controlled media that reaches the vulnerable decode routine. Exploitation requires no additional execution privileges or authentication (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) but does require user interaction, since the crafted stream must actually be rendered by the decoder; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the risk is best characterised as a credible, above-average-priority mobile vulnerability rather than an emergency. MediaTek has assigned patch ID ALPS11383899 (issue MSV-9614) and published guidance in its October 2026 product security bulletin.
Local privilege escalation in the MediaTek APU (AI Processing Unit) driver allows an attacker with existing code execution on affected devices to trigger a use-after-free, achieving full compromise of confidentiality, integrity, and availability (CVSS 8.4). The flaw affects MediaTek chipsets MT8781, MT6993, MT6899, MT8668, MT8910, and MT8793, and requires no additional privileges or user interaction once local access is obtained. No public exploit code or active exploitation is confirmed at time of analysis.
An out-of-bounds write in MediaTek modem (baseband) firmware allows an attacker operating a rogue base station to escalate privileges on a wide range of MediaTek chipsets (e.g., MT6853, MT6980, MT6991, MT8798, MT6895) once the victim's device connects to that base station; no authentication is required, but exploitation is high-complexity and requires user interaction per the assessed vector. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the risk is bounded by the need for RF proximity to a malicious base station rather than being a mass-exploitable remote flaw.
Local privilege escalation in MediaTek's APU (AI Processing Unit) allows a locally-executing attacker to corrupt memory via malformed input, potentially achieving kernel-level code execution on devices with affected chipsets (MT6899, MT8781, MT8910, MT8793, MT6993, MT8668). The vulnerability is rated CVSS 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and requires the attacker to already run code on the device, such as a malicious Android app, with no additional privileges or user interaction needed. No public exploit identified at time of analysis, and the flaw is fixed by MediaTek patch ALPS11249004.
Local privilege escalation in MediaTek NeuroPilot on affected chipsets (MT8781, MT8189, MT6993, MT8793, MT8910, MT8668, MT8188, MT6881, MT8875) allows an attacker with local code execution to trigger an out-of-bounds write in the APU/AI driver, potentially gaining high-integrity code execution with no user interaction, though no additional privileges are needed once that local app context exists. Vendor patch ALPS11249062 is available; no public exploit identified at time of analysis. It is a high-priority patch target for affected MediaTek-based devices but is not remotely reachable, limiting its scope to privilege escalation rather than initial compromise.
Local privilege escalation in MediaTek's NeuroPilot component allows an attacker with an existing foothold on a device to corrupt memory and elevate privileges via an out-of-bounds write caused by a missing bounds check (CWE-787), rated CVSS 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Affected platforms are devices built on MediaTek chipsets MT8668, MT8875, MT8781, MT8910, MT6881, MT8188, MT8189 and MT6993 that ship an unpatched NeuroPilot build. The flaw is not remotely reachable and requires local code execution (typically a running or installed Android app with no special privileges); no user interaction or elevated permissions are needed once that foothold exists, and no public exploit code was identified at time of analysis.
Local privilege escalation in MediaTek's Video HAL lets an unprivileged app already running on an affected device corrupt a fixed-size stack buffer via crafted input to the video hardware abstraction layer, yielding code execution in the HAL context with high impact to confidentiality, integrity and availability (CVSS 8.4, AV:L/PR:N/UI:N). The flaw stems from a missing bounds check (CWE-121, stack-based buffer overflow) and affects roughly four dozen MediaTek chipsets spanning the MT6xxx, MT8xxx and MT2718 families used in Android phones, tablets, Chromebooks and automotive platforms. No user interaction and no additional execution privileges are required once local code execution exists, but the attack vector is local only - remote exploitation is not indicated and no public exploit code has been identified at time of analysis. MediaTek has assigned patch ID ALPS11375674 (issue MSV-9571), delivered to OEMs through its October 2026 product security bulletin.
Memory corruption in the MediaTek cellular modem baseband (an out-of-bounds write from a missing bounds check) allows an attacker who operates a rogue base station within radio range to escalate privileges on the target device without authentication and without any user interaction. Exploitation is not reachable over the internet: the CVSS vector AV:A/AC:H/PR:N/UI:N with C:H/I:H/A:H reflects that the attacker must be in adjacent radio proximity and must successfully induce the victim's UE to attach to the malicious base station, and CISA's SSVC assessment records Exploitation: none and Automatable: no, so this is a conditionally gated baseband flaw rather than a mass-exploitation emergency. No public exploit code has been identified at time of analysis; MediaTek has released a fix under Patch ID MOLY01778988 (Issue ID MSV-8897) in its October 2026 product security bulletin.
An out-of-bounds write in MediaTek modem firmware (CWE-787) allows a nearby attacker operating a rogue base station to escalate privileges on affected devices once the user equipment attaches to the attacker-controlled cell. The flaw has a CVSS 3.1 base score of 7.5 (AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) and affects dozens of MediaTek chipsets, including MT6833, MT6877, MT6983, MT6985, and MT6989, when they run unpatched modem firmware. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records no observed exploitation and marks the issue as not automatable, and MediaTek has published a fix under Patch ID MOLY01778993 in its October 2026 product security bulletin.
Improper privilege management in LaraDashboard before 1.4.8 lets an authenticated Admin-tier user who holds the role.edit permission escalate to Superadmin by renaming or editing roles, or by granting themselves user.login_as rights, which then exposes account takeover and the core-upgrade and module-installation functions needed for code execution. The pre-patch guard in RoleController only refused Superadmin role tampering when the application ran with demo_mode enabled and the role name was literally 'Superadmin', so ordinary production deployments are exposed to any role-management holder by default. Exploitation is access-gated rather than anonymous: it requires a pre-existing Admin account with role.edit, no user interaction is needed, and no public exploit has been identified at time of analysis; the vendor has released the 1.4.8 patch.
Privilege escalation in the Ultimate Member WordPress plugin affects all versions through 2.13.1, allowing an authenticated attacker to manipulate a user-controlled key that the plugin fails to bind to the requester's own account or privileges, thereby elevating a low-privilege account to a higher role such as administrator. The flaw requires an authenticated account (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base score 8.8), but because Ultimate Member supplies front-end user registration, an attacker can typically self-register on sites with open registration enabled - the common deployment mode - lowering the practical barrier to entry; sites that disable open registration require a pre-existing credential. Exploitation status at time of analysis: no public exploit identified at time of analysis, and the vulnerability is not confirmed actively exploited (CISA KEV), though the low attack complexity and high confidentiality, integrity, and availability impact make rapid patching a priority, with no EPSS score supplied in the available intelligence.
Privilege escalation in the Groundhogg - CRM, Newsletters, and Marketing Automation plugin for WordPress versions up to and including 4.9 allows an authenticated Sales Representative-level user who holds both the add_contacts and send_emails capabilities to rebind a contact record to an Administrator's WordPress user ID, then use the v4 email-test endpoint to mint an {auto_login_url} key and obtain a fully authenticated Administrator session. This is a genuine high-priority issue rather than a CVSS-inflated one, but the practical risk is contingent on a site having delegated those non-administrator Groundhogg roles to the attacker; no public exploit identified at time of analysis, and the vendor has released a fix in version 4.9.1.
Workflow-supplied container options in Gitea act_runner (versions before 3.0.0) are merged straight into the Docker HostConfig of the job container, letting a workflow author request host PID/IPC namespaces, CapAdd=ALL and unconfined seccomp/apparmor and then escape to the runner host as root. The twist is that the flaw is exploitable precisely when runner privileged mode is disabled: that code path forces only Privileged=false while preserving namespace, capability, device and security-profile flags from workflow YAML, so the control administrators rely on does not contain the attack. Only the Docker job-container backend is affected, and exploitation requires the ability to submit or trigger a workflow on a repository served by that runner (authenticated, push or pull-request privileges per the PR:L vector), with impact changing scope to the underlying host; no public exploit identified at time of analysis, and EPSS is low at 0.20% (9th percentile), though real-world risk is severe for shared runners open to untrusted workflow authors.
Unauthenticated WebSocket endpoints in the Monta EV charging platform (monta.app, all versions) allow any network-reachable attacker to impersonate a charging station and thereby read sensitive backend data or perform unauthorized actions on the platform. The weakness is a missing-authentication flaw (CWE-306) rated 9.3 under CVSS 4.0 and mapped by the independent assessment to CVSS 3.1 AV:N/AC:L/PR:N/UI:N with high confidentiality and integrity impact and low availability impact, meaning unauthenticated remote attackers need no credentials, user interaction, or non-default configuration - network reachability to the charging-station WebSocket service is the only practical prerequisite. There is no public exploit identified at time of analysis and no KEV listing, but ICS-CERT has published an advisory covering all versions, and the absence of a version-based mitigation makes exposure reduction the primary interim control.
Local privilege escalation leading to code execution in Nx (Nrwl Nx) affects versions 14.6.0 through 22.7.8 and 23.1.x before 23.1.2 on macOS and Linux, where daemon and isolated plugin-worker Unix domain sockets are created in shared temporary locations such as /tmp/.nx without owner-only 0700 directory or socket permissions. Because the socket transport performs no authentication and relies entirely on filesystem containment, a second unprivileged local account on the same shared build server, developer host, or multi-user container can connect and invoke handlers - notably PROCESS_IN_BACKGROUND, which accepts a module path and invokes its default export as the account running Nx - and can also read workspace file contents, project graphs, and task hashes. The flaw is rated CVSS 4.0 8.5 (AV:L/AC:L/PR:L, CWE-269); no public exploit code was identified at time of analysis, single-user machines with no other local account are not exposed, and disabling the daemon alone does not remove the still-vulnerable plugin-worker sockets - only upgrading to 22.7.9 or 23.1.2, or enforcing owner-only socket and directory permissions, closes the exposure.
Unauthenticated privilege escalation in the Divi Membership plugin for WordPress (versions up to and including 2.2.0) lets any site visitor create a brand-new account with the administrator role and, by also submitting auto_login=on, be logged in as that administrator within the same request - resulting in complete site takeover. The flaw (CVSS 3.1 base 9.8, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) sits in dmem_form_submit_handler(), which derives the new user's role by iterating every WordPress role and calling password_verify() against an attacker-supplied bcrypt hash in the form_id POST parameter, with no whitelist of permitted roles. The only prerequisite is a WordPress nonce, which is publicly emitted on any page that renders the Divi Membership registration form and is therefore readable by any unauthenticated visitor; no public exploit code has been identified at time of analysis.
Account takeover in the WordPress plugin Super Forms - Drag & Drop Form Builder affects every version through 6.3.316: any authenticated user with Subscriber-level access or above can overwrite the password and email address of an arbitrary account, including an administrator, and seize the site. The flaw sits in the Register & Login add-on, whose before_email_success_msg() routine trusts an attacker-supplied user_id in its register_login_action='update' flow and hands it directly to wp_update_user() without any ownership or capability check, while the super_save_form AJAX action that creates the malicious form is equally unprotected; the CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8) reflects that a low-privileged, self-registrable account is the only real prerequisite. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the low bar to entry plus the add-on requirement makes this a genuinely high-priority privilege-escalation flaw rather than an inflated score.
Privilege escalation in Wind River VxWorks 7 (all versions up to 26.09) allows an authenticated low-privilege shell user to bypass the per-user command privilege check and execute commands they are not authorized to run, impacting confidentiality, integrity, and availability (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not universal: it requires the command shell to be configured in the vulnerable per-user command-privilege-enforcement mode and requires the attacker to already hold a valid low-privilege shell account, so devices that do not use that mode or expose no low-privilege shell are not affected. No public exploit identified at time of analysis, and the vendor has released a patch in version 26.09.
Improper privilege management in Apache HTTP Server's mod_ssl (versions 2.4.0 through 2.4.68) causes SSLRequire access-control directives that use file-related expressions to be evaluated in a way that can grant or deny access contrary to the server operator's intent, giving a remote attacker a possible means to reach content that the SSLRequire check was meant to protect or, conversely, to disrupt intended authorization. The flaw is not reachable in a default configuration: exploitation requires mod_ssl to be loaded and the operator to have configured access control specifically through the SSLRequire directive using file-related expressions, a non-default, operator-chosen configuration, which is reflected in the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N (high attack complexity, low confidentiality and integrity impact, no availability impact); authentication requirements for the attacker are not confirmed from available data. There is no CISA KEV listing and no public exploit code identified at time of analysis, and no EPSS score was provided.
Authenticated subscriber-level attackers can escalate privileges on WordPress sites running ByteCoreStack - MCP Connector for AI Tools versions up to 1.2.2 due to an incorrect privilege assignment (CWE-266). The vulnerability is network-exploitable with low complexity and requires only a subscriber account (CVSS PR:L), with no user interaction, resulting in high confidentiality, integrity, and availability impact (CVSS 8.8). No public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated privilege escalation in the Authorizer WordPress plugin (versions up to and including 3.15.3) allows remote attackers to gain elevated privileges, potentially administrator-level, on affected WordPress sites. The vulnerability carries a CVSS 3.1 base score of 9.8 (critical) and per the vector requires no authentication or user interaction. No public exploit code has been identified at the time of analysis, but the low deployment footprint of the plugin may limit widespread exploitation.
Broken access control in HCL iControl (CVSS 3.1 score 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) allows a low-privileged authenticated user to bypass authorization checks or manipulate object identifiers directly, resulting in privilege escalation and unauthorized modification or deletion of sensitive application data. Because the exploit requires a valid low-privilege account (PR:L), an unauthenticated external attacker cannot exploit this despite the 'Authentication Bypass' tag on the report, but any user with even minimal credentials can escalate to full confidentiality, integrity, and availability impact without user interaction. No confirmed active exploitation (not in CISA KEV) and no public exploit code identified at time of analysis; prioritization should focus on environments where low-privilege accounts are broadly provisioned or externally reachable.
Privilege escalation in Ghost CMS (versions 2.21.0 before 6.56.0) allows an authenticated low-privilege staff user to elevate their role to a higher-privilege staff position by exploiting missing authorization checks in the notifications system. Exploitation requires an existing staff account and passive interaction from a higher-privileged user (CVSS 4.0 PR:L/UI:P), so multi-author or multi-staff deployments are primarily at risk; single-author sites have negligible exposure. A vendor patch is available in Ghost 6.56.0, and no public exploit code has been identified at time of analysis.
Privilege escalation in JetBrains YouTrack lets an authenticated holder of an already-high-privilege (non-admin) account raise their effective permissions by abusing the user group links functionality, where a required authorization check is missing (CWE-862). All YouTrack releases before 2026.2.19422 are affected, and the issue is scored CVSS 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity, and availability impact once triggered, requiring no user interaction. The PR:H prerequisite meaningfully bounds exposure - anonymous or fully unprivileged users cannot exploit it - and there is no public exploit identified at time of analysis, making this a real but gated finding rather than an urgent fire-drill.
Authenticated privilege escalation in WPC Shop as a Customer for WooCommerce (versions up to and including 2.0.0) enables any logged-in user to take over an Administrator account by supplying the Administrator's user ID to the wpcsa_login endpoint, receiving a full Administrator session cookie without the Administrator's password. The flaw stems from missing role validation (CWE-269) before issuing a session, and WordPress user IDs are trivially enumerable. No public exploit code is identified at time of analysis, but the vendor-released patch 2.0.1 is available and this is assessed as a genuine high-priority vulnerability.
Authenticated attackers holding Subscriber-level (or higher) WordPress accounts can escalate themselves to Administrator on any site running the ByteCoreStack - MCP Connector for AI Tools plugin through version 1.2.3, because the plugin's `wp_update_user_meta` MCP tool protects only `user_pass`, `user_activation_key`, and `session_tokens` while leaving `wp_capabilities` and `wp_user_level` writable. A single JSON-RPC call to the plugin's OAuth-gated MCP endpoint, targeting the attacker's own user ID with `key=wp_capabilities` and a role array such as `{"administrator": true}`, changes the account's role on the next request; no user interaction is required and the CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8). No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, but the low privilege prerequisite makes this high-priority wherever self-registration is open.
Unauthenticated attackers can create WordPress administrator accounts on any site running the Super Forms - Drag & Drop Form Builder plugin up to and including version 6.3.316 whenever the Register & Login add-on is active and a registration form using register_login_action='register' is published, because the add-on accepts a client-supplied 'role' parameter and passes it straight into wp_insert_user(). With a CVSS of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) the flaw yields full site takeover, but exposure is conditional: the required public registration form must exist, and sites using Super Forms only for contact or other non-registration forms are not affected. No public exploit code has been identified at time of analysis, and an upstream fix is available via GitHub pull request #205, though a released patched version is not independently confirmed in the available data.
Improper privilege management in Genian SSL PNS (the Frodo-Core and Watchcat-UI components) lets an authenticated administrator who can run CSV bulk user registration escalate to super administrator and then force the creation of an operating-system-level account by manipulating the permission column of the uploaded CSV. The issue is classified as CWE-269 and scored 7.5 by the reporting CNA under CVSS 4.0 (AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L), which shows the attack is network-reachable but requires a pre-existing high-privileged account and a non-default attack precondition (AT:P) tied to deployments that actually expose the bulk-registration import workflow. No public exploit code has been identified at time of analysis and there is no evidence of active exploitation; the vendor has published an advisory (GHSA-8mjh-295r-5hf2) covering both affected components.
Local privilege escalation in Kiteworks Core lets an attacker who already holds code execution as an unprivileged backend service account invoke a privileged routine that mishandles attacker-influenced input, running arbitrary OS commands as root. The flaw requires a prior local foothold on the appliance - the CVSS vector (AV:L, PR:L, UI:N) confirms it cannot be reached directly over the network and demands an existing initial compromise or misconfiguration to obtain the service account. No public exploit code or active exploitation is identified at time of analysis, and the realistic risk is bounded by how easily that initial service-account access can be obtained on a given deployment; the vendor's advisory is GHSA-658c-86vw-g9hf.
Local privilege escalation in Kiteworks Core lets an attacker who already has code execution as an unprivileged backend service account on the appliance obtain root. A privileged, root-owned routine consumes a filesystem path that the lower-privileged service account can influence, so the attacker can steer that root operation into executing arbitrary commands with full privileges (CWE-59 link-following / unsafe path handling). The attack is local-only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and is a second-stage primitive requiring an existing foothold; no public exploit was identified at time of analysis and the CVE is not reported as confirmed actively exploited (CISA KEV), though the 7.8 severity and availability of a vendor advisory make prompt patching advisable.
Local privilege escalation in Kiteworks Core allows an attacker who already holds a shell under a low-privileged service account to elevate to root on the appliance, gaining complete control of the system and the sensitive content it brokers. The weakness is a link-following issue (CWE-59) in a root-privileged operation, reachable with local access as the service account (CVSS:3.1/AV:L/AC:L/PR:L/UI:N), no user interaction, and no non-default configuration, making it a realistic second-stage escalation after a separate initial-access compromise. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the CVE is not associated with a KEV listing; the primary limiting factor is the prerequisite service-account foothold, while the primary risk is full root compromise of the appliance.
Command injection in Kiteworks Core's internal cluster-management function allows an attacker who already has code execution on one node of a clustered deployment to run operating system commands with elevated privileges on other nodes in the same cluster. The vulnerable function is not reachable from outside the cluster, so the attack path is confined to the internal cluster network and requires a pre-existing foothold on a cluster member; single-node deployments are not exposed. Rated CVSS 8.8 (AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) with scope change reflecting cross-node impact, and no public exploit identified at time of analysis.
Improper privilege management in Kiteworks Core before 9.5.0 allows an authenticated administrative user who holds only limited, non-Sysadmin role-management permissions to grant another account full system-administrator (Sysadmin) rights that the grantor was never authorized to confer. The flaw sits in the role-assignment logic, which fails to constrain grantable privileges to the subset the granting administrator actually possesses, so a single delegated-admin session is enough to escalate a chosen account to the highest privilege level. Per the assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, score 7.2) the attack is network-reachable with no user interaction but requires an already-authenticated high-privilege session; no public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV). This is best characterized as a genuine but access-gated integrity risk whose real-world exposure depends on how many delegated administrators exist in a deployment and how tightly their role scopes are managed.
Local privilege escalation on Reachy Mini Wireless robots running OS images built from pollen-robotics/reachy-mini-os prior to v0.2.4, where a sudoers entry granted the low-privileged pollen daemon user (uid 1000) passwordless root access to /usr/bin/systemctl with no subcommand or argument restriction. Any code already executing as pollen - for example through a compromised reachy daemon - can escalate to full root (uid 0) without user interaction or a TTY, because systemctl can be pointed at an attacker-supplied unit file whose ExecStart runs as root. Rated CVSS 3.1 7.8 HIGH (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), confirmed by the vendor advisory GHSA-7rhg-9v48-x3h2 and closed by release v0.2.4; no public exploit code or CISA KEV entry was identified at time of analysis, and exploitation requires an existing foothold as the pollen user on an unpatched image.
Local privilege escalation in Zammad lets an attacker who already controls the unprivileged 'zammad' service account elevate to root on the host, affecting every release from 1.5.0 up to but not including 7.1.0-alpha (including the then-current alpha). The vendor labels this critical with a CVSS 4.0 score of 9.4 and a network/unauthenticated-looking vector (AV:N/PR:N, E:A), but the description confines the attacker to an already-present local/service-account context; our independent assessment therefore re-scores it as CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, i.e. a high-impact but post-foothold escalation rather than a pre-auth remote compromise. No public exploit code has been identified at time of analysis, and CVE-2026-102490 does not appear in CISA KEV, so the vendor vector's E:A exploit-maturity metric cannot be corroborated here.
Privilege escalation in Internet2 Grouper before 7.5.1 allows authenticated users with delegated rule creation or editing permissions in the User Interface to elevate their privileges, but only in certain configurations. This flaw (CWE-266) requires a non-default configuration and pre-existing authorization, moderating the headline critical severity; the attack is of high complexity per our independent assessment, and no public exploit identified at time of analysis. Upgrading to version 7.5.1 resolves the issue.
Privilege escalation in NVIDIA's GPU Display Driver for Windows lets a local, low-privileged authenticated user bypass an authorization check in the driver's kernel-mode escape handling, gaining kernel-level capabilities that can lead to code execution, data tampering, information disclosure, or denial of service on the affected host. The issue is classified as CWE-863 (incorrect authorization) with a CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); it is strictly local with no remote or network attack surface. No public exploit code has been identified and the vulnerability is not listed on CISA KEV, so it should be treated as a genuine but access-gated privilege-escalation risk concentrated in multi-user, VDI, and cloud-GPU hosts where an untrusted tenant or guest driver instance can reach the driver's escape interface.
Privilege escalation in the SureCart WordPress plugin through version 4.7.2 allows an authenticated user who holds the limited 'Shop Worker' store-staff role to elevate to full administrator-level control of the WordPress site. The flaw is a case of incorrect privilege assignment (CWE-266) inside a SureCart operation, and because the assessed vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, no user interaction or special conditions are needed once the Shop Worker role is held - making it a straightforward path for a malicious insider or anyone who has compromised a shop-staff credential. Anonymous or self-registering visitors cannot reach the flaw; there is no public exploit identified at time of analysis.
Privilege escalation in the Vitepos WordPress point-of-sale plugin through version 3.5.0 lets an authenticated account that already holds a custom or elevated Vitepos role - such as POS staff or manager - raise its own privileges to a higher level on the affected site, rated CVSS 7.2 (High). Exploitation is remote and low-complexity with no user interaction required once such an account exists, but the high-privilege prerequisite (PR:H) means anonymous visitors and ordinary subscriber-level users cannot trigger it, and only WordPress sites with the Vitepos plugin installed and active are exposed. No public exploit code has been identified at time of analysis, and the issue is reported by Patchstack as an improper privilege assignment (CWE-266) defect in the plugin's custom role handling.
Privilege escalation in the Estatik WordPress plugin (versions through 4.3.5) allows an authenticated Subscriber-level account to elevate its privileges to higher roles, potentially achieving full site compromise. Although the published CVSS 3.1 vector lists PR:N (score 9.8), the independent assessment and the 'Subscriber Privilege Escalation' description confirm that a Subscriber account is required; such an account is trivially obtainable when open user registration is enabled, common on real-estate or listing sites. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
Privilege escalation in the WordPress plugin Import and Export Users and Customers (Javier Carazo) at versions up to and including 2.5.2 lets an authenticated low-privileged account - specifically a Subscriber - reach higher-privileged roles, giving full compromise of the site's confidentiality, integrity, and availability (CVSS 3.1 base 7.5, High). The advisory-supplied vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H means the attack is network-reachable and needs no victim interaction, but the High Attack Complexity rating reflects a non-trivial precondition (a specific plugin state, ordering, or crafted import payload) that limits how reliably it can be pulled off; it does require the attacker to already hold a Subscriber account, which is trivial on sites with open registration enabled. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV, so exploitation is currently assessed as a targeted-risk rather than a mass-scanning risk; no EPSS probability was supplied with this record.
Privilege escalation in MISP before 2.5.48 allows an authenticated user who holds the tag editor permission (perm_tag_editor) to smuggle sibling User and Organisation records into tag collection create or edit requests, which the affected controller then persists alongside the intended tag collection - letting the attacker create or modify accounts and escalate to site administrator. Exploitation requires network access to the instance and a delegated tag-editor role; no user interaction or administrative rights are needed, and the accompanying source fix (commit 96f735e7b) shipped in MISP 2.5.48. No public exploit code was identified at time of analysis, and instances that never delegate perm_tag_editor to non-administrative accounts are not exposed to an unprivileged external actor.
Privilege escalation in the WP User Frontend WordPress plugin before 4.3.12 lets unauthenticated visitors tamper with the role value submitted by the plugin's front-end registration form and create an account with elevated privileges such as Editor (the administrator role cannot be obtained this way). The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) confirms unauthenticated remote exploitation with no user interaction, but the AC:H reflects a narrow environmental precondition: the site must run on a PHP build where the sodium (libsodium) extension is unavailable, and a public registration page must be configured through the plugin. No public exploit code has been identified at time of analysis, and the SSVC assessment records Exploitation: none; impact is scored High for confidentiality and integrity with no availability effect.
Local privilege escalation to root in Pexip Infinity (versions before 38.2, plus 39.0, 39.1, and 40.0) allows an attacker who already holds a foothold on a node to break out of a low-privileged local context and obtain full root control. Per the CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8), the flaw is local-only, requires low privileges, and is not remotely exploitable on its own: the attacker must first run arbitrary code on the node, either by chaining a separate remote code execution vulnerability or by already possessing administrative access to the node's operating system. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); the practical risk is that this bug turns any successful initial compromise of a Pexip Infinity host into a complete root compromise, so it should be treated as a meaningful post-exploitation escalation rather than a standalone remote threat.
Sandbox escape in Google Chrome on Windows prior to 154.0.8037.92 allows a local attacker to execute arbitrary code outside the browser sandbox through improper privilege management in the Mojo IPC layer. Exploitation requires local access to a Windows host and some user interaction (UI:R) but no authentication (PR:N), and it functions as a second-stage capability: an attacker who already holds a sandboxed foothold, such as a compromised renderer, can leverage the flaw to reach the full privileges of the browser process, yielding high confidentiality, integrity, and availability impact with a scope change. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the EPSS-style risk signal is low; non-Windows Chrome builds are unaffected because the defect is Windows-specific. A vendor patch is available in Chrome 154.0.8037.92.
Local privilege escalation in the npm package adm-zip through version 0.6.0: when an application extracts an archive with the non-default keepOriginalPermission=true option, the library copies the Unix permission bits recorded in each zip entry's external file attributes straight to disk via fs.chmodSync() without stripping the setuid (0o4000), setgid (0o2000) or sticky (0o1000) bits. An attacker who can supply a zip - no special access needed to craft one - can therefore plant a 04755 root-owned binary whenever the extraction runs as root (the common Docker-build, CI-runner and privileged-install posture where this flag is used), and the attacker's code executes as root once a lower-privileged user later runs that file. The issue is correctly rated Medium despite a 7.1 CVSS score because it is highly conditional (flag enabled, root extraction, setuid file preserved and executed by another user); confirmed actively exploited: no - not in CISA KEV - but a working proof-of-concept (a Python-crafted zip with external_attr 0o4755 << 16) is documented in the vendor advisory. Default usage with the flag off, or extraction as a non-root user, is not exploitable.
User-mode-to-kernel privilege escalation in Eclipse ThreadX lets a loaded, memory-protected TXM module register an arbitrary function pointer as the global trace-full callback, which privileged kernel code then invokes directly with no pointer validation and no privilege-dropping trampoline when the trace buffer wraps. Affected builds are those compiled with the non-default TX_ENABLE_EVENT_TRACE option and running modules in TXM_MODULE_USER_MODE with TXM_MODULE_MEMORY_PROTECTION; an invalid pointer crashes the kernel (denial of service), while a pointer into the module's own code has been observed executing with kernel privilege (CONTROL.nPRIV = 0), producing a scope-crossing compromise of the RTOS kernel by a local, low-privileged attacker. Exploitation requires the attacker to already control executing code inside a loaded module plus the non-default trace build flag, and no public exploit code has been identified at time of analysis.
Privilege escalation in the Electron framework lets a <webview> guest grant itself Node.js integration inside its Web Workers even when the embedding (embedder) application has Node integration turned off, so untrusted guest content can obtain a more privileged JavaScript execution context than the host application intended to allow. Affected releases are npm/electron before 41.10.6, 42.x before 42.9.2, 43.x before 43.4.1, and 44.0.0-alpha.x before 44.0.0-beta.5 (CPE cpe:2.3:a:electron:electron). Exploitation is not automatic: the independent assessment requires a non-default deployment where the app enables the <webview> tag, runs the embedder unsandboxed with nodeIntegration disabled, and loads attacker-controllable content into the guest - applications that never enable <webview>, keep the embedder sandboxed, or only load trusted first-party content are unaffected. There is no public exploit identified at time of analysis (CISA SSVC: Exploitation none, Automatable no, Technical Impact total) and EPSS is low at 0.45% (37th percentile), although the underlying privilege boundary is a total-compromise class issue where it applies; the NVD-style vector scores 9.8, while our independent assessment reflects the higher attack complexity and changed scope (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) imposed by those preconditions.
Local privilege escalation in TeamViewer Full Client and Host for Windows (versions prior to 15.82) lets an authenticated low-privileged local user escalate to NT AUTHORITY\SYSTEM by winning a time-of-check-to-time-of-use race against the elevated installer's rollback routine. The attacker must already hold a low-privileged account on the host and must wait for a specific runtime event - a rollback actually occurring during a TeamViewer installation or update - after which they overwrite rollback backup files staged in a user-writable temporary directory before the elevated installer restores them; the assessed attack complexity is High (CVSS:3.1/AV:L/AC:H/PR:L/UI:R), so success is probabilistic and depends on precise timing rather than being guaranteed on a single attempt. This is a legitimate but conditional local privilege escalation: it cannot be triggered remotely, it requires a local account plus an installer/update action (UI:R), and no public exploit code or confirmed active exploitation has been identified at time of analysis. The vendor-released fix is TeamViewer Full Client and Host 15.82.
Local privilege escalation in TeamViewer Full Client and Host on Windows, Linux, and macOS (all versions prior to 15.82) allows an authenticated low-privileged local user to write arbitrary files with SYSTEM/root privileges by sending crafted IPC commands to the locally running privileged TeamViewer service daemon. Successful exploitation yields full compromise of confidentiality, integrity, and availability on the host (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), and because the flaw is deterministic rather than a race condition it is reliably triggerable once local access exists. No public exploit code has been identified at time of analysis, and the issue is not listed as confirmed actively exploited (CISA KEV); however, the requirement of only low-privileged local access makes it a valuable post-compromise escalation primitive.
Privilege escalation in Mozilla Firefox's Places component lets a remote attacker reach elevated, normally chrome-restricted functionality inside the browser when a victim opens attacker-controlled web content in an affected build. Affected releases are Firefox versions before 157 and Firefox ESR versions before 153.4, rated 8.8 under CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, which means no attacker-side authentication or privileges are required but the victim must be induced to interact with a crafted page, after which confidentiality, integrity and availability impact is total within the affected security scope (CWE-269 improper privilege management). There is no public exploit identified at time of analysis and no CISA KEV entry; CISA SSVC rates exploitation as "none" and the attack as not automatable, so this is a serious browser flaw rather than a current worm or mass-exploitation emergency, and it is fully resolved by updating to Firefox 157 or Firefox ESR 153.4.
Privilege escalation in the Mozilla Firefox Address Bar component lets a remote, unauthenticated attacker gain elevated privileges within the browser by persuading a victim to load and interact with attacker-controlled web content. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) confirms no credentials are needed but the attack cannot succeed without the targeted user interacting with the malicious page, and CISA's SSVC assessment marks the issue as not automatable with no observed exploitation. No public exploit code or confirmed active exploitation has been identified at time of analysis; the flaw is remediated in Firefox 157, Firefox ESR 153.4, and Firefox ESR 140.17, so only unpatched installations prior to those builds remain exposed.
Privilege escalation in Mozilla Firefox's DOM: Service Workers component allows a remote, unauthenticated attacker (CVSS vector PR:N) to elevate privileges inside the browser after convincing a victim to visit an attacker-controlled or compromised page (UI:R), affecting Firefox builds before 157 and ESR branches before 153.4 and 140.17. The 8.8 score derives from high confidentiality, integrity, and availability impact with low attack complexity, but scope is unchanged (S:U), meaning the impact stays confined to the browser's own privilege boundary rather than escaping to the host operating system. There is no public exploit identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no, so practical exposure is driven by how quickly the supplied ESR/rapid-release fixes are deployed rather than by observed attack activity.
Privilege escalation in the DLL Services component of Mozilla Firefox allows an attacker to achieve elevated code execution - with high confidentiality, integrity, and availability impact - when a victim renders attacker-controlled web content, reflected in a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). No authentication is required (PR:N) and attack complexity is low, but the vector mandates user interaction (UI:R), meaning a target must be induced to load a crafted page rather than being compromised by a service-side drive-by. The issue is fixed in Firefox 157, Firefox ESR 153.4, and Firefox ESR 140.17, so unpatched pre-157 and pre-ESR builds are the exposed population; there is no public exploit code and no observed exploitation at time of analysis, and SSVC classifies the flaw as non-automatable.
Use-after-free in Mozilla Firefox's Graphics: WebRender compositor lets remote, unauthenticated attackers corrupt memory and escalate privileges inside the browser when a victim loads attacker-controlled web content - no authentication is required (PR:N), but the attack is not server-side passive and depends on the target visiting or interacting with a malicious or compromised page (UI:R). The flaw rates CVSS 3.1 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and was fixed in Firefox 157 and in Firefox ESR 153.4, ESR 140.17, and ESR 115.42; no public exploit code has been identified and CISA's SSVC assessment records exploitation as none, so this is a genuine but not urgent priority. Modern Firefox content-process sandboxing further limits post-corruption impact unless the attacker chains a separate sandbox escape, and WebRender is enabled by default, so no unusual configuration is needed to reach the vulnerable path.
Boundary-condition errors in Mozilla Firefox's Graphics component allow an unauthenticated remote attacker to trigger memory corruption and achieve privilege escalation on the affected platform, provided the victim loads attacker-controlled content that reaches the vulnerable rendering code path. Only builds below Firefox 157, Firefox ESR 153.4, Firefox ESR 140.17, and Firefox ESR 115.42 are affected - updating to any of those versions fully remediates the issue. Although the CVSS base score is 8.8 with high confidentiality, integrity, and availability impact, no public exploit code has been identified at time of analysis, CISA's SSVC assessment rates exploitation as 'none' and the flaw as not automatable, and the mandatory user-interaction requirement (UI:R) prevents automated or wormable spread, making this a genuine but not top-priority issue.
Privilege escalation in Mozilla Firefox versions prior to 157 arises from incorrect boundary conditions in the Graphics: WebGPU component, a CWE-119 buffer-bounds flaw that a remote, unauthenticated attacker can trigger when a victim loads attacker-controlled web content. Exploitation depends on user interaction (UI:R) - typically visiting a malicious or compromised page - and is rated CVSS 8.8 with high confidentiality, integrity and availability impact, though scope is unchanged (S:U) so the effect is confined to Firefox's content process rather than the host operating system. No public exploit code was identified and CISA's SSVC assessment records Exploitation: none, so this is a mid-to-high priority browser patch rather than an emergency; the issue is fixed in Firefox 157.
A use-after-free in Mozilla Firefox's Graphics: WebGPU component (CWE-416) lets a remote attacker who gets a victim to render attacker-controlled web content corrupt memory and potentially achieve code execution in the browser's process, earning a High-severity CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). All Firefox builds prior to 157 are affected, and Mozilla fixed the issue in Firefox 157 (advisory mfsa2026-97, Bugzilla 2059020). No public exploit code or confirmed active exploitation has been identified at time of analysis, and because the vector requires user interaction, mass automated exploitation is unlikely, though per-target heap grooming is needed for reliable execution.
Local privilege escalation in Ghostscript for Windows (all versions prior to 10.08.0) allows any authenticated local user to plant a malicious PostScript resource file in the predictable C:\gs\ path, which Ghostscript then auto-loads with the privileges of whichever principal next invokes it. The hijack requires no special Ghostscript configuration because it abuses Windows default ACLs that let authenticated users create directories at the root of C:\, and it succeeds only while C:\gs\ is unpopulated - the default state on Windows installations; execution is passive and fires when a user or service subsequently runs Ghostscript, with the payload's privilege gain bounded by that invoking principal (assessed as scope-changed impact). No public exploit code has been identified at time of analysis, and the issue, reported by CERT-PL, is fixed in 10.08.0.
Privilege escalation in FastAdmin (versions 1.6.1.20250430 and 1.6.5.20260602) lets an attacker who already holds an authenticated administrator session manipulate the Database Management component via application/database.php so that code runs with privileges beyond those intended, resulting in full compromise of confidentiality, integrity, and availability of the affected instance. Exploitation is network-reachable but heavily gated: the assessed vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:R, score 7.1) requires high privileges and user interaction, so an unauthenticated attacker against a default install cannot trigger it directly. Publicly available exploit code exists and is referenced in a public GitHub issue, though there is no KEV confirmation of active exploitation; the EPSS-style exploit maturity flag in the CVSS 4.0 vector (E:P) reinforces that a working proof of concept is circulating.
Improper privilege management in RaspAP WebGUI through 3.5.5 lets an authenticated low-privilege web-UI user escalate to root by manipulating how the plugin installer writes sudo configuration entries through PluginInstaller::addSudoers (src/RaspAP/Plugins/PluginInstaller.php). Exploitation is remote and unauthenticated attempts are not possible - the attacker must already hold a valid RaspAP panel session (CVSS 4.0 PR:L, independently assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N, C:H/I:H/A:H) - but no user interaction or unusual complexity is required beyond that. Publicly available exploit code exists (a GitHub gist demonstration was published alongside the VulDB entry), and the vendor was contacted but did not respond, so no vendor-released patch has been identified at time of analysis; this is a genuine high-impact issue but not an emergency, with exposure concentrated on panels reachable from untrusted networks or protected only by default credentials.
Privilege escalation in SUSE Rancher Fleet (0.14.x before 0.14.11, 0.15.x before 0.15.7, and 0.16.x before 0.16.2) lets a low-privileged tenant - an authenticated user able to push a Fleet Bundle or GitRepo - have resources written to a shared downstream cluster under the Fleet agent's own cluster-admin credentials rather than the ServiceAccount pinned to the deployment, allowing that tenant to overwrite configuration owned by other tenants. Exploitation is gated by topology: it only matters in multi-tenant Fleet deployments where privileged and untrusted teams share the same downstream cluster, since single-tenant or per-tenant-isolated clusters have no crossed trust boundary. Rated 8.8 by the vendor (the independent assessment scores it higher, 9.9, because the trust boundary crossing changes scope); no confirmed active exploitation (CISA KEV) and no public exploit identified at time of analysis.
Local privilege escalation in Extegrity Exam4 on macOS lets any unprivileged local user escalate to full root by abusing command injection in the root-running com.extegrity.LogTool privileged helper, which is reachable over XPC. An attacker with a low-privileged local session (PR:L, AV:L, no user interaction required, UI:N) can send crafted XPC messages that reach [ConsoleLogHelper copyConsoleIntoFileFromStartDate:], where attacker-controlled parameters are passed into a syslog command without sanitization and executed with root privileges via LaunchSynchronous, yielding complete confidentiality, integrity, and availability impact (CVSS 3.1 base 7.8, HIGH). Exploitation requires the helper to be installed, registered, and reachable on the host; remote exploitation is not possible, and no public exploit code was identified at time of analysis.
Authenticated privilege escalation in Nezha Dashboard before 2.3.5 lets any account holding the nezha:service:write scope escalate into privileged Agent operations by creating or updating a service monitor whose Task.Type is set to a command or configuration task value, since the service API never validated that the submitted type belonged to the supported probe set. Because service monitors and privileged operations share the same protobuf Task.Type integer namespace, the crafted task is accepted and dispatched to Agents within the attacker's existing authorization scope, resulting in command execution or Agent reconfiguration (CWE-269). The independent assessment rates this as a genuine but authentication-gated privilege-escalation issue whose urgency is moderate and whose blast radius scales with how broadly service:write is delegated; the vendor has released a fix in 2.3.5 (commit 38824dbc11a63964c5b9296ae4c68e62b34fa04b) and no public exploit has been identified at time of analysis.
Privilege escalation in Elastic Kibana's Agent Builder feature lets an authenticated non-administrative user who can edit a shared agent cause privileged operations to run under the identity of a higher-privileged user who later interacts with that agent (CWE-441 confused deputy). Rated CVSS 7.3 High (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N), the flaw requires the Agent Builder feature to be enabled with at least one shared agent, the attacker to hold edit privileges on it, and a privileged victim to interact with the tampered agent; if the attacker can also author workflows, escalation to full Kibana and Elasticsearch cluster administrative control is possible. No public exploit identified at time of analysis, and vendor patches are available in Kibana 9.4.7 and 9.5.0.
Privilege escalation in the WordPress plugin Groups - Memberships and Access Control (itthinx) affects all versions up to and including 4.6.0, allowing any authenticated Subscriber-level user to self-enroll in arbitrary groups - including privileged admin groups - and ultimately mint a group that grants every registered WordPress capability, reaching Administrator. The root cause is an authorization check in groups_join() that reads the ambient post's author capabilities ($post->post_author) instead of the acting user's, while the same response hands the caller a valid join hash and nonce; an attacker only needs valid low-privilege credentials and the post ID of any Administrator-authored post, supplied via the post_ID parameter of the authenticated wp_ajax_parse_media_shortcode AJAX handler, with no victim interaction. Per available intelligence there is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, though our independent assessment rates this a genuine high-priority issue rather than a high-CVSS-but-low-real-risk case, given the low bar of Subscriber self-registration on many sites.
Froxlor through 2.3.10 fails to enforce the mail.allow_external_domains policy in the EmailSender.add API command, letting an authenticated customer with API access register an arbitrary external sender address for their mailbox even when the administrator has explicitly disabled external allowed-sender domains. The bypass only matters when the administrator has enabled the allowed-sender feature (mail.enable_allow_sender=1) while disabling external domains (mail.allow_external_domains=0), and the sender-spoofing impact materializes only if the generated mail configuration consumes the allowed-sender table; there is no public exploit identified at time of analysis, and exploitation requires valid low-privilege API credentials rather than being unauthenticated. A vendor-released patch is available in Froxlor 2.3.12, and our independent assessment rates this as a genuine but modest-severity authorization/policy-enforcement flaw rather than a high-urgency one.
Privilege escalation in Kyverno before 1.19.1 allows an authenticated Kubernetes namespace tenant with Policy/apiCall authoring rights to escape namespace isolation and create objects as Kyverno's admission-controller ServiceAccount. The attacker supplies percent-encoded directory-traversal sequences in the Policy apiCall urlPath to bypass the per-namespace clamp, enabling creation of cluster-wide MutatingWebhookConfiguration objects or PolicyException objects in the kyverno namespace, with a path to cluster-admin escalation. No public exploit identified at time of analysis; vendor patch available in 1.19.1.
Authenticated privilege escalation in Budibase Server before 3.45.0 lets a low-privileged 'builder' account grant itself administrative roles in other workspaces. The flaw resides in the POST /api/global/groups/:groupId/apps endpoint, which fails to validate per-app authorization, allowing a builder who only has rights in one workspace to rewrite user-group role mappings for applications outside their own tenant boundary. Because the CVSS vector requires PR:L and no user interaction, exploitation is limited to authenticated builders, and a single-workspace or single-tenant instance offers no cross-boundary target; the raw 8.6 score therefore overstates the immediate threat even though the underlying authorization defect and its escalation impact are genuine. There is no evidence of active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, though a vendor patch is available in 3.45.0.
Privilege escalation in Grav CMS 2.0.14 through 2.0.24 allows an authenticated backend operator who already holds the admin.users permission - but not admin.super - to grant super-admin rights to their own account or to a group they belong to via the flex accounts backend. The bypass works because the security guard is resolved against a field's exact blueprint path, so a crafted flat dot-notation key such as access.admin.super evades the rule match and is later reconstructed into a genuine nested value when the object is saved. No public exploit code has been identified at time of analysis, and because the attacker must already possess privileged but non-super backend access, this is an insider or post-compromise escalation vector rather than a remote unauthenticated one - but the resulting super-admin control over configuration, plugin and theme installation, the file manager, and all accounts makes it a genuine, high-value escalation rather than a high-CVSS-but-low-real-risk issue.
Privilege escalation in Capgo (capgo.app) before 12.267.1 allows a principal holding the apikey_manager role to rotate a higher-privileged same-owner sibling API key - such as an org_super_admin key - via the API key rotation PUT endpoint and retrieve the replacement plaintext secret, giving the attacker the credentials of the stronger principal. Exploitation is authenticated: the attacker must already possess or have compromised an apikey_manager key, and a more privileged sibling key under the same owner must exist, which limits exposure to organizations that delegate key-management duties to lower-trust roles. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis; a vendor fix is available in 12.267.1.
Vertical privilege escalation and account takeover in Capgo (capgo.app) through 12.261.0: an authenticated attacker who already holds the org_admin tier permission org.update_settings can rewrite the provider_id column of a public.sso_providers row over PostgREST and point the organization's email-domain trust anchor at an identity provider they control, after which the server-side SSO merge routine binds the attacker's identity to the legitimate org owner account, nulls that account's password, and deletes its other identities and sessions. The impact is full owner/super_admin takeover plus lockout of the real owner, although exploitation is gated on the target organization having an active SSO provider configured and on the attacker already possessing org_admin in that organization; no public exploit code was identified at time of analysis and there is no CISA KEV entry. The incomplete nature of the fix (a BEFORE UPDATE guard that freezes dns_verified_at, domain, status and enforce_sso but leaves provider_id, metadata_url and attribute_mapping writable under a table-wide ALL grant with only row-scoped RLS) makes this a durable privilege-escalation path rather than a one-off misconfiguration.
Privilege escalation in the Capgo capgo.app backend (versions ≤ 12.261.0) lets an authenticated user who holds only the apikey_manager organization role mint API keys bound to higher-privileged deploy roles (app_developer, app_uploader, channel_developer, channel_uploader). Those keys can in turn be used to push arbitrary over-the-air JavaScript updates to every end user of the organization's apps, giving an insider or delegated-role holder unauthorized write access to production app content. Exploitation requires a valid JWT session and the apikey_manager role (authenticated, no user interaction), no public exploit code was identified at time of analysis, and the issue is not listed in CISA KEV; at advisory publication no patched version was available.
OpenClaw Codex before 2026.7.1 fails to properly enforce owner authorization for native conversation bindings, allowing a non-owner channel sender who already holds command access to bind to the Codex runtime and execute host-capable turns with access to files, tools, and processes. This privilege escalation (CWE-269) has a CVSS 4.0 score of 8.7 (High) and is network-reachable with low complexity and low privileges, but it requires the attacker to already have command access on a channel-a fully external attacker cannot trigger it. No public exploit code or active exploitation was identified at time of analysis.
OpenClaw Gateway before 2026.7.1 fails to restrict owner-only infrastructure tools exposed through the chat.send endpoint, allowing an authenticated write-scoped non-owner caller to cause the agent to invoke owner-only configuration or scheduling operations, including persistent state changes. This privilege escalation (CWE-269) affects Gateway deployments using authentication modes that honor caller identity and narrower operator scopes, and where agent tool policies include the `gateway` and `cron` tools; shared-secret token and password callers are treated as fully trusted and are out of scope. No public exploit code identified at time of analysis; the vendor CVSS 4.0 score is 7.2 with integrity impact dominant.
Privilege escalation and privilege retention in InvoicePlane prior to 1.7.2 allow a previously-authenticated administrator whose account was downgraded or deactivated by another administrator to keep operating with administrative rights through a stale session. Because Admin_Controller trusts the user_type value cached in the session at login rather than re-reading ip_users.user_type, the downgraded user's live session continues to authorize admin requests, and the attacker can then call Users::form() to write user_type back to 1, making the restored admin role persistent in the database. Exploitation is limited to multi-administrator deployments where a role change occurs while the target session stays alive; it requires prior high-privilege access and is not reachable by an unauthenticated or ordinary low-privilege user, and no public exploit code or active exploitation has been identified at time of analysis. The vendor-released fix is InvoicePlane 1.7.2.
Improper privilege management in Zammad helpdesk/customer support systems allows an attacker holding a valid but deliberately restricted API token to create new administrator accounts, inheriting the latent authorization authority of the token's parent account instead of honoring the token's granular scope. This affects all Zammad releases prior to 7.0.2 and 7.1.0, and exploitation is authenticated (CVSS PR:L) since a scoped token must already be held, though no user interaction is required and the vector is network-reachable; success grants full access to tickets, customers, and configuration and effectively hands the attacker complete control of the instance. No public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV), but the independent assessment rates it a genuine high-priority privilege-escalation flaw rather than a high-CVSS-but-low-risk case, and EPSS-style risk is elevated by the trivial post-exploitation payoff.
Privilege escalation in the Seclore FileSecure Desktop Client affects Windows hosts running any client version before 3.25.1.0, where an authenticated local user can abuse an improper access control weakness in the product's kernel-mode driver to obtain NT AUTHORITY\SYSTEM. The flaw is rated CVSS 3.1 7.8 HIGH (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-269) and is strictly a post-authentication escalation - it cannot be used for initial access or network exploitation and requires an existing low-privileged session on the vulnerable host. There is no public exploit identified at time of analysis and no CISA KEV listing; SSVC records Exploitation: none, so the operational risk is concentrated in insider-threat and post-compromise scenarios rather than mass exploitation. A vendor-released patch is available in version 3.25.1.0.