Privilege Escalation

Privilege escalation in Mozilla Firefox's WebExtensions component allows an extension-level actor to gain capabilities beyond those it was granted, yielding high confidentiality and integrity impact; all Firefox builds prior to version 158 are affected, with the fix delivered in Firefox 158 via Mozilla security advisories mfsa2026-106 and mfsa2026-109. Exploitation requires a low-privileged foothold - in practice an already-installed malicious or compromised browser extension reaching the vulnerable privilege-management code path (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-269) - and no public exploit code has been identified at time of analysis. EPSS is low at 0.16% (4th percentile) and the flaw is not listed in CISA KEV; signals are mixed and point to a moderate, not emergency, priority, with the AV:N rating questionable for an extension-context escalation and worth verifying with Mozilla.

Privilege escalation and information disclosure in Mozilla's Process Sandboxing component let attacker-controlled web content break out of the Firefox content-process sandbox on unpatched installations - Firefox before 158 and Firefox ESR before 153.5 - with high confidentiality, integrity and availability impact (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is remote and requires no attacker authentication, but it is user-driven: the victim must actively load the malicious page, and CISA's SSVC assessment records Exploitation: none and Automatable: no, so this is a targeted client-side risk rather than a mass-exploitation candidate. There is no public exploit identified at time of analysis, and vendor-released fixes ship in Firefox 158 and Firefox ESR 153.5 (MFSA 2026-106 and MFSA 2026-108).

Privilege escalation in Mozilla Firefox's Application Update component allows a locally present, low-privileged attacker to elevate their privileges on the affected host, with the input CVSS 3.1 score of 8.8 (High) reflecting complete confidentiality, integrity, and availability impact. Exploitation requires only low privileges with no user interaction and is limited to unpatched builds prior to Firefox 158 and Firefox ESR 153.5; systems updated to those versions are not affected. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV) signal, with the EPSS score remaining low at 0.19% (8th percentile).

Authenticated, low-privilege users of Siemens RUGGEDCOM CROSSBOW running any version earlier than V6.0 can bypass access controls on sensitive configuration records and retrieve administrative credentials for various internal systems, yielding unauthorized information disclosure and follow-on privilege escalation. The defect is an authorization bypass through a user-controlled key (CWE-639) that is network-reachable with low attack complexity but requires a valid session, consistent with the CVSS 4.0 vector's PR:L and high confidentiality, integrity and availability impact confined to the CROSSBOW system itself. No public exploit code or confirmed active exploitation has been identified at time of analysis, and Siemens has released V6.0 to correct the condition.

Authenticated database users can escalate privileges and execute arbitrary operating-system commands on hosts running SIMATIC WinCC V7.5 (all versions), V8.0 before Update 11, and V8.1 before Update 7 because the application assigns excessive permissions to a database role (CWE-266). Exploitation requires a remote attacker to already hold valid database credentials and network reachability to the WinCC database service, but no user interaction is needed; no public exploit code has been identified at time of analysis. Siemens rates the issue 8.7, and while the impact is high, our independent assessment classifies it as a credible operational-technology priority rather than an emergency because the prerequisite of authenticated database access and network segmentation limits the realistic attack surface.

Local capability escalation in the macOS build of the DigiD app (Logius) lets an attacker who already holds user-level code execution on the same Mac inject an arbitrary dynamic library into the DigiD process and run code under the app's identity, reaching DigiD data and cryptographic operations the process would not normally expose - CVSS 7.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). The root cause is that the app binary is not signed with the Hardened Runtime flag, so the loader still honours DYLD_INSERT_LIBRARIES; this is a post-compromise escalation primitive, not a remote or initial-access bug, and it grants no privilege beyond the app's own context (S:U) and no availability impact. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV); a Hardened-Runtime-signed build blocks the injection path and is available per the vendor advisory pointing at the Mac App Store listing.

Privilege escalation in HTMLy 3.1.1 allows a remote attacker to elevate from a low-privileged account or session to administrative control by abusing the get_feed function in the admin.php component. The supplied CVSS 3.1 score is 9.8 with PR:N, but the independent assessment applies PR:L because CWE-269 privilege-escalation issues realistically require some existing access; no CISA KEV or confirmed active exploitation is provided, and no public exploit was identified at time of analysis. Exposure is limited to HTMLy 3.1.1 installations where the admin interface is reachable, and keeping admin.php off the public internet substantially reduces risk.

Privilege escalation in Frappe ERPNext lets any authenticated user - including one holding no operational role - create privileged records such as user accounts and role assignments, ultimately taking full control of the site. The flaw affects releases before 15.111.0 and 16.x before 16.22.0, and stems from a record-creation endpoint that derives the record type from the request and inserts it with permission checks disabled; the only prerequisite is a valid login (CVSS 4.0 vector PR:L, i.e. authenticated, no user interaction, no non-default configuration). Rated 8.7 with high confidentiality, integrity and availability impact across the vulnerable site, and no public exploit code has been identified at time of analysis.

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

Improper access control in the Location Service for Esri component of IBM Maximo Application Suite 9.0, 9.1, and 9.2 allows an attacker who already holds high privileges on the underlying Kubernetes/OpenShift platform to abuse a schema-less Custom Resource Definition (CRD) and escalate to full read and write control over affected resources, since the CRD enforces no input validation and the component applies insufficient authorization checks. Exploitation requires authenticated high-privilege access (CVSS vector PR:H), no user interaction, and the optional Esri Location Service add-on to be deployed, so the barrier to entry is significant; the assessed vector is AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H for a base score of 7.2. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), making this a moderate-priority, high-barrier issue rather than an urgent widespread threat - though successful abuse yields high confidentiality and integrity impact on the Maximo environment.

Improper privilege management in Rapyd Admin (the open-source Rapyd Admin scaffolding package for Laravel) versions 9.0.0 through 9.19.x lets an authenticated user who already holds the 'edit users' permission - the shipped 'operator' role is sufficient - promote their own account to the 'admin' role by submitting the admin role ID through the UsersEdit Livewire component, which prior to 9.20.0 synced browser-supplied roles without validating them against a server-side allow-list. Successful exploitation lifts tenant scoping, bypasses per-record authorization and enables impersonation of other users, including higher-privileged accounts, giving high confidentiality, integrity and availability impact within the affected installation. The flaw is fixed in v9.20.0, which computes assignable roles server-side and prevents a non-super-admin from granting a role to itself; no public exploit code and no confirmed active exploitation were identified at time of analysis, and the prerequisite of an already-delegated privileged account makes this an insider or compromised-account escalation rather than a default-configuration, unauthenticated issue.

Privilege escalation in containerd's CRI checkpoint-restore path allows an authenticated local attacker who can submit an attacker-controlled checkpoint archive via CRI CreateContainer to have the restored process run with restored credentials (including root), full capabilities, and restored no_new_privs and seccomp state, while CRI status continues to report the requested ContainerConfig. The flaw affects containerd 2.1.0 through 2.2.6 and 2.3.0 through 2.3.3, and only where CRI checkpoint restore via CreateContainer is actually used; systems that never use this experimental feature are not affected. Rated CVSS 7.8 (High) with a local, low-complexity, authenticated (PR:L) vector, and no public exploit identified at time of analysis. Fixed in 2.2.7 and 2.3.4, where the restore-via-CreateContainer behavior is additionally disabled by default.

Authenticated attackers with low privileges can escalate to elevated privileges on IBM i systems running Db2 Mirror for i 7.4, 7.5, or 7.6 by submitting a crafted request that bypasses additional authorization and input-validation checks, potentially allowing malicious code execution. This critical-severity (CVSS 9.9) privilege escalation affects standard deployments and requires a valid low-privilege account; no public exploit code or active exploitation has been identified at time of analysis, but a vendor patch is available.

Privilege escalation in IBM Db2 LUW (versions 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 on Linux, UNIX and Windows, including Db2 Connect Server) lets a locally authenticated low-privilege user elevate to higher privileges through improper privilege management, with high impact to confidentiality, integrity and availability and a scope change that can affect resources beyond the vulnerable component. Exploitation is constrained: the attacker must already hold a local foothold on the host and valid low-privilege credentials (CVSS vector AV:L/PR:L/UI:N), so this is not reachable by a remote unauthenticated adversary and realistically affects insiders or attackers who have breached another service on the same host. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; a vendor patch is available, making this a credible, actionable priority for exposed Db2 LUW estate rather than an emergency.

Privilege escalation in IBM Db2 11.5.0 through 11.5.9 and 12.1.0 through 12.1.5 allows a local low-privileged attacker to gain elevated privileges on the Db2 host when the db2locssh feature is enabled. The vulnerability is not remotely reachable and requires an existing local account, making it a post-foothold escalation vector rather than a remote entry point. No public exploit code has been identified at the time of analysis, and IBM has released patches; this is a credible operational priority for environments with db2locssh enabled, but not an emergency.

Privilege abuse in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 lets a remote attacker who already holds delegated database-administrator privileges run backup or restore operations against forests outside their authorized database scope, resulting in unauthorized read or modification of security-critical data. The flaw is rated CVSS 9.6 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N) under CWE-269 (Improper Privilege Management), and because exploitation requires the pre-existing delegated DB-admin role it is an authenticated privilege-abuse issue rather than an unauthenticated pre-auth bug. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; no EPSS data or proof-of-concept reference was supplied, so the realistic threat model is a malicious or compromised privileged tenant administrator.

Authenticated privilege escalation in Progress MarkLogic Server lets an attacker who already holds query-execution access invoke an XQuery evaluation function without the additional evaluation privilege that function requires, so the query is evaluated with elevated permissions and can lead to server-side code execution in the server's security context. Affected deployments are 12.x releases before 12.1.0 and 11.x releases before 11.3.7; the vulnerability is rated CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), with the scope change and full confidentiality, integrity, and availability impact reflecting what is possible once the missing privilege check is bypassed. Exploitation requires a pre-existing account with query-execution access rather than anonymous reachability, and no public exploit code has been identified at time of analysis; there is no confirmed active exploitation (CISA KEV) reported for this issue.

Privilege escalation in Progress MarkLogic Server 12.x before 12.1.0 and 11.x before 11.3.7 allows an attacker who can supply user-controlled values to certain higher-order XQuery functions to have those values evaluated in an elevated security context, potentially gaining permissions beyond those granted. The vendor's CVSS 3.1 vector (8.6 High, AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N) claims unauthenticated exploitation, but the independent assessment assesses PR:L and high confidentiality and integrity impact, consistent with the requirement for access to an XQuery-evaluating interface (a MarkLogic account with query/evaluation rights or an application that passes user input into such functions). No public exploit code or CISA KEV entry is present in the provided intelligence, and no EPSS score was supplied.

Local privilege escalation in Edgeless Systems Contrast 1.8.0 through 1.24.0 allows a low-privileged local user on a node to modify the world-writable containerd configuration and overwrite the runc runtime path, leading to high confidentiality, integrity, and availability impact on that node. This is a credible local privilege-escalation issue rather than a remotely wormable threat; the CVSS vector requires local access with low privileges (PR:L), and no public exploit identified at time of analysis.

Privilege escalation in the Grav API plugin (grav-plugin-api) before 1.0.36 allows an account that already holds the api.users.write capability - a delegated user manager rather than a super-admin - to obtain full super-admin API access. The attacker edits account access maps or pending invitations so that a positive scalar value is stored on an 'admin' or 'api' parent grant; the plugin's inheriting permission resolver then treats that grant as satisfying its requireSuper checks, exposing super-only API endpoints. Exploitation is authenticated and requires the high-privilege api.users.write capability (CVSS vectors show PR:H, scope unchanged), so the flaw matters mainly where user-management rights have been delegated below super-admin; no public exploit code or confirmed active exploitation was identified at time of analysis.

Privilege escalation in Progress MarkLogic Server affects 11.x releases before 11.3.7 and 12.x releases before 12.1.0, where an attacker who already holds an administrative account can reach authentication material belonging to higher-privileged users and use it to obtain unauthorized administrative access (CWE-269, CVSS 8.4 with scope change). Exploitation is gated by pre-existing admin privileges, so this is primarily an insider or post-compromise escalation risk rather than an externally reachable entry point; no public exploit has been identified at time of analysis and there is no CISA KEV association. No EPSS score was supplied in the available intelligence, so likelihood estimates should be treated as unquantified.

Authenticated XQuery injection in Progress MarkLogic Server 11.x before 11.3.7 and 12.x before 12.1.0 allows a remote attacker who already holds a manage-user-level account to escalate to persistent unauthorized administrative control of the database. The flaw resides in a deprecated Management API package path and carries a 9.9 CVSS score because exploitation crosses a security boundary (S:C) and fully compromises confidentiality, integrity, and availability. It is not a pre-authentication issue - a valid manage-user credential is mandatory - and no public exploit code has been identified at time of analysis, so risk is concentrated in environments where the Management API is network-exposed and manage-user grants are loosely administered.

An authenticated privilege-escalation flaw in Progress MarkLogic Server lets an attacker who already holds forest-management privileges create a persistent, unauthorized administrator account, resulting in complete administrative control of the server. Affected are 12.x releases before 12.1.0 and 11.x releases before 11.3.7; the vulnerability is reachable over the network (AV:N) with low privileges (PR:L) and no user interaction, and it is rated 9.9 because a successful escalation changes scope, giving the attacker high confidentiality, integrity and availability impact across the deployment. No public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (no CISA KEV listing); the practical risk is concentrated in deployments that delegate forest-management rights to non-super-admin or duty-separated roles, since an attacker must first possess that privilege to exploit the flaw.

Privilege escalation in GoatCounter through 2.7.0 lets an authenticated user - even one holding only read-only access - promote their own account to superuser by sending a form-encoded POST to /user/pref containing protected fields such as user.access[all]=* and user.email_verified=true, which the userPrefSave handler mass-assigns despite its readonly tags. Because the attacker must already hold a valid low-privilege account (PR:L in both the CVSS 4.0 vector and our assessed CVSS 3.1 vector), the realistic exposure is shared, hosted, or multi-tenant instances where registration or account provisioning is available to untrusted parties; fully anonymous exploitation is not possible. No public exploit code was identified at time of analysis and there is no confirmed vendor-released fix version, so operators should treat this as a credible, actionable escalation flaw rather than a mass-exploitation emergency.

Privilege escalation in the Crowdfundly WordPress plugin (versions through 2.2.2) allows an attacker who already holds one of the plugin's own low-privileged roles to grant themselves the WordPress administrator role or arbitrary capabilities, resulting in full site takeover. The flaw sits in AJAX actions that lack capability checks, so it is reachable remotely with no victim interaction, but the attacker must first obtain a legitimate low-privilege Crowdfundly account - trivial on sites that permit open self-registration of backers/campaigners, and a hard blocker on sites that restrict account creation. Publicly available exploit code exists (per the WPScan entry), while there is no confirmed active exploitation (CISA KEV); the independent assessment rates this as an authenticated privilege-escalation issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) rather than the higher-privilege PR:H rating shown in some feeds.

Unauthenticated attackers can update and delete arbitrary WordPress options through the AI Content Generator Marketing plugin (versions through 1.0.0), a capability that typically enables full site takeover by, for example, flipping the default new-user role to administrator and enabling open registration. The plugin's AJAX handlers perform neither a nonce check nor a capability check, and because the CVSS vector is AV:N/AC:L/PR:N/UI:N with C/I/A all High, no authentication, user interaction, or non-default configuration is required - only that the plugin be installed and active and its endpoints reachable. Publicly available exploit code exists (ratings from WPScan), making opportunistic mass scanning realistic; there is no CISA KEV confirmation of active exploitation and no EPSS score was supplied, so this should be treated as high-severity, readily exploitable, but not yet confirmed as exploited in the wild. All available signals point to genuinely high risk.

Envira Gallery WordPress plugin versions before 1.16.2 fail to verify the capability WordPress reserves for plugin installation when handling the setup-wizard plugin-installation request, letting an authenticated Multisite subsite Administrator install any WordPress.org-published plugin into the network-shared plugins directory - an action Multisite reserves for the network Super Admin. The issue is gated: it only crosses a privilege boundary on WordPress Multisite networks and requires the attacker to already hold subsite-Administrator credentials (CVSS 3.1 AV:N/AC:L/PR:H/UI:N, assessed with S:C/C:H/I:H/A:H, scored 7.2), and it is not exploitable on standard single-site WordPress where Administrators legitimately install plugins. Publicly available exploit code exists (WPScan-published), and the vendor has released a fixed version 1.16.2.

Privilege escalation in the Mobile Builder WordPress plugin (versions through 1.4.2) allows any authenticated low-privilege user - including a self-registered customer account - to grant themselves the administrator role by writing unrestricted user meta keys through one of the plugin's REST routes. The flaw requires only a valid low-privilege account (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 8.8) and no administrator interaction, and publicly available exploit code exists according to WPScan. Sites with open user self-registration enabled are the easiest to attack, but any existing low-privilege user can still exploit the vulnerable route; CISA's SSVC rates technical impact as total while noting no observed exploitation and no known automatable exploitation at this time.

Unauthenticated privilege escalation in the Tonda Membership plugin for WordPress (published by Select Themes) affects all versions up to and including 1.0.1, allowing a remote attacker with no credentials and no user interaction to obtain elevated privileges on an affected site. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) rates confidentiality, integrity and availability impact as High, so successful abuse can effectively hand over site-level control. The only practical precondition is that the vulnerable plugin be installed and active on a standard WordPress installation; no public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied. Patchstack is credited as the reporting source and its advisory is the single reference provided.

Privilege escalation in the AIWU WordPress plugin (ai-copilot-content-generator) through version 1.5.9 lets a low-privileged Subscriber account elevate itself to a higher role, up to administrator, by abusing incorrect privilege assignment (CWE-266) in the plugin. Sites are fully exposed when the WordPress 'Anyone can register' option is enabled, since an attacker can self-provision the required Subscriber account; where registration is closed, the attacker must already hold or be granted such an account. Our independent assessment scores this as CVSS 9.8 with PR:L (Subscriber required), which conflicts with the supplied PR:N vector, so the unauthenticated framing should be verified against the Patchstack advisory; no public exploit identified at time of analysis, and no confirmed active exploitation (no CISA KEV listing).

Privilege escalation in the miniOrange OTP Verification WordPress plugin through 5.5.7 allows an attacker to gain elevated privileges on affected sites; the supplied CVSS 3.1 vector scores it 9.8 Critical (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H), describing a remote, unauthenticated, low-complexity flaw, though the incorrect privilege assignment (CWE-266) may in practice require a low-privileged authenticated account and authentication requirements are not confirmed from available data. No public exploit code or active exploitation (CISA KEV) is identified in the provided intelligence.

Privilege escalation in the WPMU DEV Forminator WordPress plugin affects every release through 1.57.3 and lets an attacker abuse incorrect privilege assignment logic to obtain capabilities beyond those granted to their account, resulting in high integrity impact and some availability impact. Our independent assessment scores the issue using the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L, i.e. network-reachable, low complexity and no user interaction, but with PR:L rather than the vendor-reported PR:N, meaning a low-privileged account is the more likely precondition and any site offering low-privilege registration should treat this as high priority. There is confirmed actively exploited? No - no KEV listing, and no public exploit identified at time of analysis, so this should be prioritized on the basis of the privilege-escalation class and the wide install base of the plugin rather than on observed attacks.

Privilege escalation in WooCommerce 9.8.0 through 11.1.2 lets an attacker who already holds an authenticated high-privilege store account obtain capabilities beyond those legitimately assigned to that role, with full impact to store confidentiality, integrity and availability (CVSS 7.2). The underlying defect is an Incorrect Privilege Assignment (CWE-266) that is reachable over the network with low attack complexity and no user interaction, but the CVSS vector (PR:H) means anonymous internet attackers are excluded - a legitimate elevated account such as a shop manager or other non-administrator role is the prerequisite. No public exploit identified at time of analysis and the issue is not listed in CISA KEV; Patchstack is credited with the report and the realistic attack surface is largest on multi-vendor, multi-staff, or delegated-administration stores.

Account takeover in the SMS Alert WordPress plugin before 4.0.1 lets unauthenticated remote attackers set a new password on an arbitrary account - including an administrator - by completing the plugin's OTP password-reset flow with a phone number they control. Rated 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), the flaw requires no authentication and no victim interaction, but is only reachable where the plugin's SMS/OTP password-reset feature is enabled and the attacker knows or can guess a valid target account identifier, which is why attack complexity is assessed as high. No public exploit code or confirmed active exploitation was identified at time of analysis; a vendor patch is available in version 4.0.1.

Privilege escalation in the Groundhogg CRM, Newsletters & Marketing Automation plugin for WordPress (all versions through 4.8.3) lets an attacker-controlled account whose user_login is exactly 'groundhogg' and whose user_email matches one of the hardcoded support addresses be silently promoted to administrator when a legitimate admin invokes the plugin's support-access feature. Exploitation is a deliberate two-actor sequence: the attacker must first plant or self-register the matching account (possible when open registration or any other self-service account-creation path exists), after which an admin triggering the submit_ticket or process_send_support_access entry points causes create_support_user() to adopt and promote that account; on multisite the promotion reaches super admin level when the triggering administrator holds manage_network_options, resulting in full site takeover. No public exploit code and no confirmed actively exploited (CISA KEV) status were identified at time of analysis, and the assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R reflects both the low-privileged account the attacker must first obtain and the administrative interaction the flaw depends on.

Authenticated privilege escalation in the FooSales - Point of Sale (POS) for WooCommerce plugin for WordPress (all versions up to and including 1.43.0) allows any account with FooSales Cashier-level access or above to overwrite arbitrary users' email addresses - including an administrator's - and then abuse WordPress's standard password-reset workflow to take over those accounts. The flaw is a missing identity/ownership check (CWE-269) in the plugin's user-details update path, rated CVSS 8.8 with PR:L (authenticated, low privilege) and no user interaction required; the only real barrier is obtaining a Cashier-or-higher role, after which full site compromise is achievable provided email-based password reset is enabled. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied in the available data, but the low prerequisite privilege and high confidentiality/integrity/availability impact make this a genuinely high-priority flaw for any site running the affected plugin. Patch status per available data: upstream fix available (changeset/commit); released patched version not independently confirmed.

Privilege escalation in the Groundhogg CRM, Newsletters, and Marketing Automation WordPress plugin (all versions up to and including 4.9) lets any authenticated user holding the default sales_rep role - which carries edit_contacts, view_notes, and add_notes but not edit_users or promote_users - take over an administrator account. The vulnerable process_edit() handler in the contacts admin page accepts an attacker-supplied 'user' parameter without an ownership or capability check, so a contact can be relinked to an administrator's WordPress user ID; generating a note containing the {auto_login_link} replacement tag then produces a valid permissions-key auto-login URL for that contact, which the attacker reads back through view_notes and visits to authenticate as the administrator. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8), and the flaw requires an existing low-privileged account rather than anonymous access; no public exploit code or confirmed active exploitation was identified at time of analysis.

Privilege escalation in the LatePoint appointment booking plugin for WordPress (all versions up to and including 5.7.3) lets an authenticated LatePoint user who holds the settings__edit capability overwrite the default_wp_role_for_customer setting with 'administrator', so that any LatePoint customer account self-registered afterwards is created with full WordPress administrator rights. The flaw is entirely server-side - the role restriction exists only in the UI dropdown and is never validated when the setting is persisted - but it is gated by two real prerequisites: a WordPress administrator must first delegate settings__edit to an agent or custom role, and a new customer registration must occur after the malicious value is saved for the escalation to materialize. No public exploit code or confirmed active exploitation was identified at time of analysis, and the assessed vector (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) treats this as a genuine high-impact issue that nonetheless sits below its 8.8 headline score in practical priority.

Unauthenticated privilege escalation in the Blocksy Companion WordPress plugin (versions up to and including 2.1.58) allows remote attackers to register and be automatically logged into a Dokan 'seller' (vendor) account, gaining publishing capabilities beyond those of a normal customer - even on sites where Dokan vendor signup is explicitly disabled. The flaw lies in the plugin's implement_user_registration() AJAX handler, which disables Dokan's vendor-registration nonce check and trusts an attacker-supplied role parameter passed to WooCommerce's customer-creation functions, giving a CVSS 3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N). Exploitation requires the Dokan multivendor plugin and WooCommerce to be active alongside the vulnerable Blocksy Companion, and no public exploit code has been identified at time of analysis.

Privilege escalation in Vikunja 2.3.0 allows a user who holds a narrowly scoped API token (permissions {"oauth":["authorize"]}) to exchange that token for unrestricted session credentials, defeating the API-token permission boundary. The token holder calls POST /api/v1/oauth/authorize to obtain an OAuth authorization code and then POST /api/v1/oauth/token to trade it for a normal bearer JWT and refresh token that are not bound to the original token's scope - runtime validation showed the scoped token could not read GET /api/v1/user, while the minted token could reach both /api/v1/user and /api/v1/projects. The vulnerability requires an already-issued scoped token from the same user (CVSS 3.1 base 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, CWE-269), no public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV). Version 2.4.0 fixes the issue.

Privilege escalation in MariaDB Server affects releases from 10.6.1 up to (but not including) 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, where the view FRM parser fails to safely encode embedded newline characters in an account name. An authenticated attacker who already holds both CREATE USER and CREATE VIEW WITH GRANT OPTION (CVSS vector PR:H, so not an anonymous path) can create a username containing forged view metadata and then create a view, causing the parser to read part of the username as security fields such as definer_host and suid and thereby escalates database privileges. No public exploit code and no confirmed active exploitation have been identified at time of analysis; the 7.2 High base score reflects a conditional, insider-style privilege-boundary bypass rather than a remote unauthenticated attack, and environments that restrict these administrative grants to trusted administrators have substantially reduced exposure.

SmarterMail before build 9777 fails to revalidate the role claim embedded in JWT access and refresh tokens when a token is redeemed at POST /api/v1/auth/refresh-token, so an authenticated attacker (PR:L) who holds a refresh token issued before an administrator demotion can replay it to mint a new access token that still carries the higher-privilege role, such as DomainAdmin or SysAdmin. The exposure is bounded by the token's natural expiry and only matters in environments where privileged accounts are actually demoted or revoked, since the attacker must either be the demoted user or have captured their pre-demotion token. No public exploit code has been identified at time of analysis, there is no KEV listing, and the independent assessment rates this a credible mid-to-high priority issue rather than an emergency.

Any authenticated user of Apache Camel Karavan 4.0.0 up to (but not including) 4.22.1 - regardless of role - can push arbitrary Kubernetes resources into the cluster through the deployment workflow. When a deployment is started, Karavan unmarshals the project's kubernetes.yaml and applies every resource it contains without restricting resource kinds, rejecting security-sensitive pod options (hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation, added capabilities), or pinning a target namespace. The vendor score is 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), while the independent assessment scores it scope-changed (S:C) because successful exploitation escapes the Karavan namespace boundary; the practical blast radius is capped by the RBAC permissions granted to Karavan's Kubernetes service account. There is no CISA KEV listing and no public exploit code identified at time of analysis, and the issue is fixed in 4.22.1.

Stored cross-site scripting in Progress Telerik Report Server versions prior to 12.2.26.1007 allows an authenticated report author to execute arbitrary script in another user's session by embedding javascript: or vbscript: URLs in report navigation actions or HTML text-box links. When a higher-privilege user, such as an administrator, views the malicious report and triggers the embedded navigation, the script runs in the web report viewer's origin, enabling privilege escalation in multi-user deployments. The vulnerability has a CVSS score of 8.9, requires authentication and user interaction, and no public exploit has been identified at time of analysis.

Incorrect privilege assignment in Progress Telerik Report Server (versions prior to 12.2.26.1007) lets an authenticated user, including a low-privilege or guest account with a valid bearer token, register as a trusted service agent through the service-agent SignalR hub. On the next server settings-synchronization event, the rogue agent receives storage settings and encryption private keys, enabling disclosure of stored data-source credentials and connection strings, impersonation of legitimate agents, and interference with task dispatch. No public exploit code has been identified at time of analysis, and exploitation requires the attacker to persist until the synchronization event occurs.

Account takeover in the FooSales WordPress plugin before 1.43.3 allows any authenticated user to have the plugin act as an arbitrary other account, including an administrator, exposing that user's account details and enabling full account takeover. The vulnerability is a broken-access-control flaw (CWE-269) in which the plugin never verifies that the caller is entitled to act as the user named in a request; it is remote (AV:N), low-privilege (PR:L), and requires no victim interaction (UI:N), yielding a CVSS score of 8.8. Publicly available exploit code exists, but there is no CISA KEV confirmation of active exploitation and EPSS estimates only a 0.13% (2nd percentile) probability of exploitation. Any site running FooSales prior to 1.43.3 that permits untrusted users to hold accounts - for example, sites with open self-registration - is at meaningful risk.

Local privilege escalation in Deskin 3.3.4.3 and earlier on macOS allows any local unprivileged process to gain full root by connecting to the root-owned com.deskin.service.installer XPC service, which performs no client authentication, and invoking its privileged installer method with an attacker-supplied installer package. Because the flaw (CWE-306) sits on a local Mach/IPC path, an attacker must already hold a local account or code-execution foothold on a host where Deskin is installed and the installer service is running, making it a post-compromise escalation primitive rather than an initial access vector. Publicly available exploit code exists (GitHub PoC, reported via VulnCheck) but there is no confirmed active exploitation (CISA KEV) at time of analysis; the submitted CVSS 4.0 score of 8.5 and the independently assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) both reflect high confidentiality, integrity and availability impact once the local prerequisite is satisfied.

Local privilege escalation in Guardium Data Protection 12.2 allows an authenticated low-privileged local user to abuse the cp_wrapper component to gain root privileges and access or modify sensitive system files. The issue is not remotely exploitable (AV:L) and requires a pre-existing local foothold (PR:L), so it is most relevant to insider threats, compromised low-privileged accounts, and post-compromise escalation; no public exploit identified at time of analysis, and no CISA KEV confirmation was provided. IBM has released a vendor patch, and this is a credible but not emergency-tier priority.

Authenticated attackers with a Zimbra Collaboration Suite account can exploit an authorization flaw in the GrantRightsRequest SOAP operation to grant the loginAs right to another local account, creating persistent mailbox access and mail-sending authority that survives password changes and session expiry. The vulnerability requires only low privileges (PR:L) and no user interaction, affecting all versions of Zimbra Collaboration Suite per the CPE. No public exploit or active exploitation has been identified at time of analysis, but the moderate CVSS score of 7.1 reflects the high confidentiality impact and the stealthy, persistent nature of the granted access.

Unauthenticated SQL execution in mJobTime (all builds through 15.7.3.32) allows any remote attacker who can reach Login.aspx to submit arbitrary SQL that executes with DBA/sysadmin privileges on the backing Sybase SQL Anywhere database and, via xp_cmdshell and xp_read_file, achieve remote code execution as LocalSystem in a single HTTP request. The runQueryButton postback and exportSqlQuery_Server PageMethod are gated only by a client-side sessionStorage flag, so no credentials, user interaction, or non-default configuration are required (independent assessment CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, consistent with the reported CVSS 4.0 score of 9.3 under AV:N/AC:L/AT:N/PR:N/UI:N). There is no CISA KEV listing for this CVE and no public exploit identified at time of analysis, though the technique is documented in the VulnCheck advisory and Sprocket Security write-up.

Red Hat OpenShift Container Platform 4 ships by default with an insights-operator-gather ClusterRole that grants the operator's 'gather' service account cluster-wide get/list access to core-group secrets, with no namespace or resourceNames scoping. An authenticated actor who can create or influence a pod specification in any namespace - and set 'serviceAccountName: gather' on it - can mount that service account and read every secret in every namespace, making this a privilege-escalation and cluster-wide credential-disclosure primitive (CWE-269, CVSS 7.7, scope-changed confidentiality-only). Exploitation requires a pre-existing foothold with pod-create or service-account-binding rights (PR:L), so it is not remotely exploitable by an unauthenticated user; no public exploit code has been identified at time of analysis, and the over-broad grant exists out of the box rather than behind a non-default feature flag.

Local privilege escalation in TightVNC Server for Windows before 2.8.88 allows an authenticated low-privileged user to tamper with the service's IPC channel, potentially gaining SYSTEM-level access, disclosing session data, or causing denial of service. The flaw stems from a named shared memory segment in the Global\ namespace created with a NULL DACL and a predictable time-seeded name, enabling any local process to open and modify pipe HANDLE values used between the TightVNC service and its desktop server process. No public exploit code has been identified at time of analysis, and exploitation requires a local authenticated session on a host actively running the vulnerable service as SYSTEM.

Incorrect default permissions in the Windows installer for Progressive Robot hMailServer 6.0.0 through 6.3.5 let any local authenticated user read the mail server's stored messages, logs, temporary files, and built-in database, because the data, log, temp, database and event folders and the hMailServer.INI file inherit the local Users group's read access from the default installation path under Program Files. The readable INI exposes the database password, which is protected only by the machine's DPAPI key and can therefore be unsealed by any local account - handing full control of an external database - while the built-in database's account password hashes become readable whenever the hMailServer service is stopped; the Linux AppImage 6.3.0 through 6.3.5 has a parallel weakness in per-user data folder permissions. Exploitation requires an untrusted local account able to sign in to the host, no public exploit was identified at time of analysis, and the vendor has released 6.3.6 as the fix.

Argument injection in Infoblox NIOS troubleshooting commands allows an authenticated high-privilege administrator to escalate to root-level shell access on the appliance. The flaw resides in the maintenance-mode diagnostic interface where user-supplied arguments are passed to underlying system commands without proper sanitization, and exploitation requires a pre-existing administrative credential (PR:H) rather than being reachable by anonymous or low-privilege users. No public exploit code or confirmed active exploitation was identified at time of analysis, and realistic risk is confined to malicious insiders or attackers who have already compromised NIOS admin credentials.

Local privilege escalation in Brocade Active Support Connectivity Gateway (ASCG) before 3.5.0 stems from a well-known Brocade default password embedded in a script that is distributed to every customer, allowing any local authenticated user with read access to the installation path to recover the credential and elevate privileges on Open Virtual Appliance (OVA) deployments where default configuration settings remain in place. The flaw is rated 7.0 (High) under CVSS 4.0 with a local vector (AV:L, PR:L, UI:P), meaning an attacker must already hold a low-privilege local account and passive user interaction is required, so it is not remotely reachable. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the realistic risk is concentrated on OVA deployments that have not rotated the default credential.

Unauthenticated account takeover, including full administrator compromise, affects WordPress sites running the Frontend Dashboard plugin versions 3.0.0 up to but not including 3.0.5. Missing authorization and nonce checks on actions available to unauthenticated users allow an attacker to invoke an arbitrary PHP function or class method with attacker-controlled arguments, resulting in complete loss of confidentiality, integrity, and availability. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV); the vendor has released a patch in version 3.0.5.

Privilege escalation in Brocade Fabric OS versions before 9.2.2d and 10.0.0 through 10.0.0a1 allows an authenticated CLI user or local process to bypass Role-Based Access Control (RBAC) validation by manipulating the process execution environment, resulting in root privileges. The flaw requires local access (AV:L), a low-privilege authenticated foothold (PR:L), and high attack complexity (AC:H) to control environment variables or settings, sharply narrowing exposure. No public exploit code or active exploitation has been identified at time of analysis.

Local privilege escalation in Brocade Fabric OS (versions before 9.2.2d and 10.0.0 through 10.0.0a1) allows an unprivileged local user to submit malformed logging configurations that inject arbitrary directives into the system logging daemon's configuration file. These directives execute with elevated privileges when the logging service reloads, enabling an attacker to gain root-level access on the switch. The vulnerability requires an existing low-privilege local account (PR:L) and no user interaction (UI:N); no public exploit has been identified at time of analysis, and the assessed CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects high impact within the local scope.

Privilege escalation in Brocade Fabric OS (versions before 10.0.1) allows a low-privilege authenticated account to obtain root-equivalent chassis administrative access when the switch is configured to use an external AAA identity source. The switch fails to constrain crafted Vendor-Specific Attributes or directory claims returned by RADIUS, LDAP, TACACS+, or a Federated IdP against its administrative role restrictions during session establishment, so an attacker who can influence those returned attributes is granted full control. Exploitation is conditional rather than mass-scale: it requires external AAA integration to be configured (deployments using only local authentication are unaffected), a valid low-privilege account (CVSS PR:L), management-network adjacency (AV:A), and attacker influence over IdP-returned attributes (AT:P); no public exploit code was identified at time of analysis, and vendor-released patch version 10.0.1 is available.

Read-only management accounts on Brocade Fabric OS switches can escalate to restricted administrative operations by submitting management-protocol requests whose non-standard action opcodes the RBAC validation engine mis-categorizes during its permission check; the flaw affects Fabric OS releases before 10.0.1 and is scored CVSS 4.0 base 7.1 (CWE-269, improved privilege management failure). Exploitation is gated: an attacker must already hold a valid authenticated read-only management account (PR:L) and be positioned on an adjacent/management network (AV:A) to reach the affected management plane, with no user interaction required (UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis, so practical risk is driven by the attacker's existing credentials and management-network access rather than by remote unauthenticated reachability.

Privilege escalation in HashiCorp Vault and Vault Enterprise allows an authenticated principal with delegated permissions to bypass explicit deny ACL rules by referencing a resource or policy name in non-canonical form, potentially reaching a protected resource or assigning a denied policy. Affected are Vault Community Edition before 2.1.2 and Vault Enterprise before 2.1.2, 1.21.12, 1.20.17, and 1.19.23, rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires an already high-privileged, delegated user (PR:H) operating in a policy model that depends on explicit deny rules, and no public exploit code or confirmed active exploitation was identified at time of analysis (no EPSS data was provided), so this is best handled as a defense-in-depth hardening fix rather than an emergency.

Local privilege escalation in Splunk Enterprise on Linux (versions below 10.4.3, 10.2.7, 10.0.10, and 9.4.15) allows an attacker who can already run commands as the OS account running Splunk Enterprise to inject operating-system commands into installation content that a subsequent root-privileged Linux package upgrade will execute as root. The flaw is conditional: the attacker must modify the installation and then a privileged package upgrade must occur, so there is no at-will escalation. No public exploit or confirmed active exploitation was identified at time of analysis.

Account-deactivation privilege escalation in wger before 2.6 lets an authenticated user who holds only the gym_trainer role disable higher-privileged accounts - including gym_manager and general_gym_manager - within the same gym, locking those users out of the application entirely. Access control on UserDeactivateView (and the mirror-image UserActivateView) uses OR logic across gym.manage_gym, gym.manage_gyms and gym.gym_trainer, with no privilege-hierarchy check and only a same-gym membership check in dispatch(), so the assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N - an insider/lower-privileged-role escalation, not a remote unauthenticated attack, and one that cannot cross gym boundaries. Publicly available exploit code exists (the vendor advisory itself publishes a working PoC of the GET request), but there is no confirmed active exploitation (CISA KEV) and no EPSS score was supplied in the intelligence feed; a gym manager provisioning a trainer account, which get_permission_list() always allows, is the amplifying path by which a trainer can then turn around and disable the manager who created it.

Cross-tenant information disclosure in wger allows an authenticated trainer account that holds both the gym.gym_trainer and gym.add_adminusernote permissions but has no gym assignment (userprofile.gym = None) to read private admin notes, uploaded documents, gym contracts, user configuration and permission data belonging to any other unassigned (gym = None) user on the same instance. The root cause is an authorization guard that fails open: the five affected views compare gym objects with the Python operator '!=', and 'None != None' evaluates to False, so HttpResponseForbidden is never reached and the following queryset is filtered only by the attacker-supplied member_id. Rated CVSS 7.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N, authenticated, low privilege), the bug is amplified because gym = None is the default state for newly registered users, so any instance with public registration plus delegated trainer permissions is exposed; a detailed proof-of-concept is documented in the published GitHub advisory and the permission-edit endpoint is also reachable, giving a possible privilege-escalation path, though no confirmed in-the-wild exploitation has been reported.

Privilege escalation in the Koinonia Link WordPress plugin (versions 1.1.2 through earlier than 1.1.5) lets any authenticated user, including a low-privileged subscriber, grant themselves the Administrator role by tampering with the role value submitted during a profile update. The flaw is a missing authorization check on the role-save routine (CWE-269), not a memory-safety or injection bug, and it is remotely reachable with no user interaction (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 8.8), meaning successful exploitation yields total control of the WordPress site. Publicly available exploit code exists and the vendor has released a fix in 1.1.5; the practical barrier is only the need for a valid account, so sites with open self-service registration are exposed to unauthenticated attackers who simply register first, while sites with registration disabled limit the threat to existing users.

Privilege escalation in Octopus Server lets an authenticated user who already holds permission to modify roles weaken a built-in role's protections and add their own account to a privileged team, effectively granting themselves administrative reach without ever being assigned those rights legitimately. The flaw stems from improper validation of unsafe equivalence in input (CWE-1289), meaning role/permission data that should not be treated as equivalent is mishandled during validation. The primary limiter is the prerequisite: the attacker must already have been delegated role-modification rights, so environments that keep that permission confined to a small trusted administrator set face materially lower exposure. No public exploit code has been identified at time of analysis, and this CVE is not confirmed actively exploited (CISA KEV); the Octopus vendor advisory SA2026-11 is the authoritative source for affected and fixed builds.

Improper preservation of access restrictions in Backstage's @backstage/backend-defaults package lets an authenticated holder of a restricted external service credential (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L, rated 7.6) escalate privileges by routing requests through plugin-to-plugin delegation: the credential's permission-name or permission-attribute limits (for example action:read) are dropped when a plugin request token is minted on the credential's behalf, so a read-only principal can perform write operations on plugins it should only be able to read. Only deployments that both use @backstage/backend-defaults and configure external service credentials with accessRestrictions are exposed, and exploitation is scoped to plugins reachable through the delegation path. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); fixed releases are @backstage/backend-defaults 0.16.1 and 0.17.8.

Local privilege escalation in the HPE/Aruba ClearPass Policy Manager OnGuard Linux agent lets a user who already holds a low-privileged account on a managed Linux endpoint elevate to root, rated CVSS 3.1 base 7.8 (HIGH). Exploitation is local only (AV:L), requires an existing foothold on the host (PR:L), needs no user interaction, and yields full confidentiality, integrity, and availability impact once root is obtained; Windows and macOS clients, and Linux hosts without the OnGuard agent, are out of scope per the vendor report. No CISA KEV listing, public proof-of-concept, or EPSS score was supplied with the available intelligence, so the current status is no public exploit identified at time of analysis, and the practical exposure is limited to environments that deploy the OnGuard Linux agent to endpoints where an attacker can first obtain a local unprivileged account.

Authenticated privilege escalation in the HPE Aruba Networking AOS-S management API allows a read-only account to escalate to full administrative access, giving the attacker complete control over confidentiality, integrity, and availability of the affected switch (CVSS 3.1 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is network-reachable and low-complexity, requiring no user interaction and no non-default configuration beyond the API being reachable, but it is gated by the prerequisite of a valid low-privilege credential (PR:L), so risk concentrates in environments where read-only accounts exist, are shared, or can be compromised; the vendor reports this as a privilege-escalation issue in the AOS-S API. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, yet the combination of a low-bar prerequisite and a total privilege gain makes this a credible, actionable priority rather than an inflated high-CVSS score.

Unauthenticated remote attackers can bypass authentication in the web management interface of HPE AOS-S (ArubaOS-Switch), gaining full administrative control of the switch, as reflected in the 9.8 CVSS score (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Any device with the HTTP/HTTPS management service reachable from an untrusted network is exposed, and because the vector requires no credentials and no user interaction, network reachability of that interface is the primary limiting factor. No public exploit code was identified at time of analysis and there is no CISA KEV confirmation of active exploitation; this is a genuine high-priority issue whose exact affected firmware versions and fixed releases are not detailed in the available data and must be confirmed against the HPE advisory.

Incorrect authorization in Elasticsearch 8.x and 9.x allows an authenticated, already-privileged user (CVSS PR:H) who has been granted a non-default, delegated role-management privilege to escalate privileges within a cluster. By abusing a role-definition setting that expands the set of indices matched against a delegated index-scoped privilege, the holder can modify their own assigned role and reach indices that should remain restricted, including internal security data, and from there potentially obtain full administrative control of the cluster. Exploitation is only possible when the cluster has the configurable delegated role-management privilege explicitly enabled and granted with a broadly-scoped index pattern; default deployments that never delegate this capability are not affected. No public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited (not in CISA KEV). Vendor-released patches are available in Elasticsearch 8.19.22, 9.4.7, and 9.5.4.

Sandbox escape in Google Chrome on macOS, affecting releases prior to 155.0.8059.39, allows an attacker who has already compromised the browser's renderer process to execute arbitrary code outside the sandbox when the victim views a crafted HTML page. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, base 8.3) confirms a network-reachable, scope-changing escape that requires user interaction and carries high confidentiality, integrity and availability impact once triggered, but the AC:H rating and CISA SSVC 'Automatable: no' reflect that it cannot be used standalone - a prior renderer compromise is a hard prerequisite. Per the authoritative assessment this is a chained second-stage exploit limited to macOS; no public exploit code and no confirmed active exploitation were identified at time of analysis.

A use-after-free race condition in the Android kernel's epoll teardown path (ep_free in eventpoll.c) lets a locally installed or otherwise compromised unprivileged app escalate to kernel-level privileges by reclaiming a freed eventpoll object before cleanup completes. The flaw is tracked as CVE-2026-56906 (CWE-362) with a CVSS 3.1 base score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires an existing low-privilege code-execution foothold and a successful, timing-sensitive race - no user interaction and no special product configuration are needed. There is no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV absent; SSVC Exploitation='none', Automatable='no'), which places this in the second-tier priority band for most defenders.

Improper access control in the npm package @payloadcms/plugin-mcp (versions 3.61.0 up to but excluding 3.88.0) lets any authenticated user of the configured user collection create, read, update, and delete MCP API keys belonging to other accounts; because an MCP key authenticates as the user it is bound to, an attacker can mint or rebind a key to a higher-privileged account and take it over. The flaw is network-reachable and requires only a low-privileged account (CVSS 4.0 score 8.6 and the independent assessment's CVSS 3.1 vector both carry PR:L with high confidentiality and integrity impact), and it is only exploitable when the application actually exposes the MCP API Key collection - installations that do not use @payloadcms/plugin-mcp are entirely unaffected. The vendor fixed the issue in 3.88.0; no public exploit code and no confirmed active exploitation were identified at time of analysis.

Privilege escalation in Dell Container Storage Modules (CSM) Operator versions prior to 1.18.0 allows an authenticated, low-privileged attacker who can create or modify the ContainerStorageModule Custom Resource to obtain root-level access on Kubernetes cluster nodes. The flaw is an improper privilege management weakness (CWE-269) in the ContainerStorageModule Custom Resource reconciler, rated CVSS 3.1 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) because the impact crosses a security scope boundary and delivers total confidentiality, integrity, and availability impact against the underlying nodes. Exploitation is not unrestricted: it requires a low-privileged cluster credential with rights to submit or alter the CSM Custom Resource (PR:L, no user interaction), so multi-tenant clusters that grant this permission broadly are the highest-risk deployments. No public exploit code has been identified at time of analysis and no CISA KEV entry exists; EPSS data was not provided.

Unauthenticated privilege escalation in the Salon Booking System WordPress plugin (versions 10.31.7 and earlier) allows remote attackers to elevate privileges by inducing a victim to trigger a crafted request, due to incorrect privilege assignment (CWE-266) in the plugin's role handling. The attack requires user interaction (UI:R) but no authentication (PR:N), and affects any WordPress site with the vulnerable plugin active. No public exploit code has been identified at time of analysis, and the issue is not confirmed as actively exploited, yet the high CVSS score (8.8) and potential for significant site compromise warrant prompt remediation.

Privilege escalation in the WordPress plugin WP User Profiles (versions 2.7.3 and earlier) allows an authenticated subscriber-level user to elevate to higher privileges, achieving full confidentiality, integrity and availability impact on the affected site. The flaw is network-exploitable with no user interaction and requires only a valid low-privilege account, which is trivially obtainable on any site that permits open user registration; sites that restrict account creation substantially raise the bar. At time of analysis there is no public exploit identified and the CVE is not listed in CISA KEV, but the 8.8 base score and the low prerequisite make prompt patching or plugin removal the priority.

Privilege escalation in the WordPress plugin Import and Export Users and Customers (versions through 2.5.5) allows an authenticated Editor-level account to assign itself or another user the administrator role by abusing the plugin's user import/export functionality, a CWE-266 incorrect privilege assignment flaw rated CVSS 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation is conditional: the attacker needs a pre-existing high-privilege account (Editor or comparable), the plugin installed and active, and no user interaction is required once that session exists. No confirmed active exploitation (CISA KEV) and no publicly available exploit code were identified at time of analysis, so the practical risk is a serious but situational escalation on multi-author or multi-tenant WordPress sites that delegate Editor accounts to less-trusted users rather than a broad internet-facing emergency.

Unauthenticated privilege escalation in the GiveWP WordPress donation plugin (versions up to and including 4.17.0) lets a remote attacker gain elevated privileges on a vulnerable site without any credentials or user interaction, consistent with the assessed vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The key mitigating nuance is the High attack complexity: success depends on preconditions the attacker cannot fully control, so this is a serious 8.1 High-severity issue rather than a trivially scriptable one. No public exploit code has been identified at time of analysis and the CVE is not listed in CISA KEV, but because it is unauthenticated and grants high confidentiality, integrity, and availability impact, sites running GiveWP 4.17.0 or earlier should treat it as urgent; sites that do not run the plugin or have already moved past 4.17.0 are not affected.

Unauthenticated privilege escalation in the SMS Alert Order Notifications WordPress plugin through 4.0.0 allows network attackers to obtain elevated privileges on affected sites, with the CVSS 3.1 vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (base 8.1 High) indicating no authentication or user interaction but high attack complexity. The underlying issue is CWE-266 incorrect privilege assignment, and successful exploitation depends on a condition outside the attacker's control such as a race condition, predictable value, or specific plugin/site state; the exact trigger was not disclosed in the provided data. No public exploit identified at time of analysis.

Privilege escalation in the PublishPress Capabilities WordPress plugin (slug capability-manager-enhanced) up to and including version 2.45.0 lets an attacker who already holds an elevated authenticated role use the plugin's role/capability management functions to grant themselves capabilities they should not receive, potentially reaching full site compromise (CVSS 3.1 base 7.2 High, AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). The dominant risk-limiting factor is the PR:H prerequisite: the actor must already possess a high-privilege role, so sites that reserve such roles for fully trusted administrators face substantially reduced real-world exposure. No public exploit code has been identified at time of analysis, and the flaw is not reported as actively exploited in the provided intelligence.

Subscriber-level privilege escalation in the JobZilla - Job Board WordPress theme through version 2.2 allows an authenticated low-privilege user to elevate their permissions, with high impact to confidentiality, integrity, and availability (CVSS 8.8). The attack is network-reachable, low-complexity, and requires no user interaction; because the CVSS vector includes PR:L, the attacker must be authenticated, and in typical job-board deployments with open self-registration obtaining a Subscriber account is trivial, while sites with registration disabled still require a valid low-privilege credential first. No public exploit identified at time of analysis, so this is an actionable priority for affected sites but not an unauthenticated emergency.

Privilege escalation in the WordPress plugin Tourfic Pro (the paid extension of the Tourfic travel and hotel booking plugin) at version 1.17.3 and earlier allows an attacker to elevate to a higher-privileged WordPress role, with a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflecting full loss of confidentiality, integrity and availability within the affected site. The CVSS vector's PR:L indicates the attacker must first hold a low-privilege authenticated account (for example a self-registered subscriber) and that no user interaction is required, but the vendor's own description labels the flaw 'Unauthenticated' - a material conflict that determines whether only registered users or any site visitor can trigger it, and defenders should verify which precondition actually applies. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; the plugin's comparatively small installed base further limits real-world exposure, so this is best treated as a credible priority for sites running the plugin rather than a broadly exploited campaign.

Unauthenticated privilege escalation in the Doctreat Core WordPress plugin (versions 1.7.0 and earlier, vendor namespace amentotech) lets a remote visitor gain administrator-level rights on any affected site without logging in, supplying credentials, or interacting with a victim. The input assigns a maximal CVSS 3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), reflecting a low-complexity, unauthenticated, network-reachable flaw with scope change and full loss of confidentiality, integrity, and availability; only sites with this specific plugin installed and un-updated are in scope. No public exploit identified at time of analysis, and no CISA KEV listing is present in the provided data.

Privilege escalation in the WebAppick Challan WordPress plugin (published as PDF Invoice for WooCommerce) version 3.7.88 and earlier allows an authenticated WooCommerce Shop Manager to obtain capabilities beyond the intended Shop Manager role, rated CVSS v3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Because the vector carries PR:H, only attackers who already hold valid Shop Manager credentials or control a Shop Manager session can reach the flaw; anonymous visitors and self-registered subscriber-level users cannot use it, and WooCommerce must be active on the site for that role to exist at all. No public exploit code or confirmed active exploitation was identified in the provided intelligence at time of analysis.

Unauthenticated privilege escalation in Meta Box AIO versions 3.7.1 and earlier allows remote attackers to gain elevated privileges on WordPress sites where the plugin is installed and active. With a CVSS score of 9.8 (Critical) and a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, the flaw requires no authentication or user interaction and can be exploited over the network. No public exploit code has been identified at the time of analysis, but the vulnerability is rated critical due to its potential for full site compromise.

Unauthenticated privilege escalation in the Amentotech Taskbot plugin for WordPress (versions 6.6 and earlier) allows any remote attacker to elevate privileges on a vulnerable site without credentials or victim interaction, as reflected by the CVSS 3.1 vector PR:N/UI:N/AC:L and a 9.8 base score. Because the flaw sits in privilege-assignment logic that is reachable in the plugin's default configuration, a standard installation that simply has Taskbot active is exposed; the practical limiting factor is that exposure depends entirely on this relatively uncommon plugin being deployed. There is confirmed actively exploited status absent - no CISA KEV entry was provided - and no public exploit code was identified in the supplied intelligence at time of analysis, so this should be prioritized on the basis of severity and ease of exploitation rather than observed attacks, with the caveat that corroborating intelligence is sparse and comes primarily from the Patchstack report.

Local privilege escalation in ClamXAV versions 3.3 through 3.11 allows an attacker who already holds a low-privileged local account on a macOS host to execute arbitrary code with system privileges by winning a race condition in the bundled Privileged Helper Tool that combines with insufficient file validation. Exploitation is timing-dependent (AV:L/AC:H/PR:L/UI:N in the assessed vector, with high confidentiality, integrity, and availability impact) and typically requires repeated attempts rather than a single deterministic trigger, making this a credible but not emergency-tier priority; no public exploit code has been identified at time of analysis, and ClamXAV 3.11.1 fully remediates the flaw.

Privilege escalation in Ghost CMS (versions 4.39.0 through 6.63.x) lets a staff user holding the 'view staff invites' permission read the secret tokens stored in pending invitations, including invitations issued for roles more privileged than their own, and then accept such an invite to elevate their account. Exploitation requires an authenticated staff session against the Admin API plus at least one pending higher-privilege invite at the time of attack, which is why the vendor rates attack complexity as high and the real-world priority is moderate rather than urgent. No public exploit has been identified at time of analysis, and the flaw is fixed in Ghost 6.64.0.

Local privilege escalation in the Android Settings component lets an attacker-controlled application that is already running on the device with low privileges (CVSS PR:L, AV:L) abuse a confused-deputy permission check and cause the more-privileged Settings process to perform operations on the caller's behalf, delivering high confidentiality and integrity impact with no user interaction required. Confirmed-affected builds are Android 14, Android 15, Android 16, and Android 16-qpr2, and the only vendor reference provided is the Android Automotive OS security bulletin for 2026-10-01, so the breadth of exposure across Android form factors should be confirmed with Google. There is no public exploit identified at time of analysis, and CISA's SSVC evaluation records exploitation as none, so this is a genuine but second-tier, local-only escalation path rather than a remotely reachable or actively exploited issue.