Use-after-free memory corruption in MediaTek's apusys driver allows a local attacker who has already obtained Android System privilege (uid system) to escalate to kernel-level code execution on affected devices, with no user interaction required once that foothold exists. The flaw affects firmware running on a broad set of MediaTek SoCs - including MT6897, MT6899, MT6989, MT6991, MT8196, MT8678 and the other MT-series chipsets listed in MediaTek's October 2026 bulletin - and is addressed by Patch ID ALPS11076799 (Issue ID MSV-8143). Because the CVSS vector carries PR:H and AV:L, this is a second-stage privilege-escalation link that presupposes a prior System-level compromise rather than a standalone remotely reachable bug; no public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in MediaTek AIDL on affected chipsets is possible via a use-after-free memory corruption, but only after an attacker has already obtained Android System privilege and local access. Successful exploitation requires no user interaction and can yield high confidentiality, integrity, and availability impact within that privileged context. No public exploit identified at time of analysis; the vendor patch ID ALPS11185225 and the October 2026 MediaTek security bulletin address the issue.
Local privilege escalation in the aidl component shipped on a defined set of MediaTek chipsets (MT6899, MT6991, MT8910, MT8781, MT6881, MT8668, MT6989, MT8188, MT6878, MT6993, MT8695, MT8189, MT8696) allows a process that already holds Android System privilege to trigger a use-after-free, corrupt memory, and gain higher-integrity code execution with high confidentiality, integrity, and availability impact. The attack is local (AV:L) and needs no user interaction, but the PR:H prerequisite means it cannot be used for initial access and only functions as a follow-on escalation from an already-compromised privileged context. At time of analysis there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; EPSS data was not supplied for this CVE. MediaTek has published a fix under Patch ID ALPS11242428 in its October 2026 Product Security Bulletin.
Local privilege escalation in the MediaTek display component could allow an attacker who already holds Android System-level privilege to gain elevated code execution through an integer overflow (CWE-190), with no user interaction required. The flaw affects a broad set of MediaTek chipsets (including MT6893, MT6895, MT6983, MT6991, and MT8188) running unpatched firmware and is rated CVSS 6.7 (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified at time of analysis, but MediaTek has published patch ID ALPS11296678 in its October 2026 security bulletin.
Local privilege escalation in the MediaTek display component lets a process that already holds System privilege trigger an out-of-bounds write in a display-path buffer, corrupting memory and potentially escalating to higher-level code execution with high impact to confidentiality, integrity, and availability. The defect is a missing bounds check (CWE-787) reachable without user interaction and with low attack complexity, but only from an existing System-privileged, on-device context (CVSS 3.1 6.7 Medium, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), so it functions as a second-stage escalation primitive rather than an initial-access or remote vector. Affected hardware spans a broad set of MediaTek chipsets including MT6991, MT6993, MT2718, MT8168-class MT8668/MT8678, MT8171, MT8188, MT8189, MT8196, MT8793, and MT8126; MediaTek has issued Patch ID ALPS11292777 (issue MSV-9195) and no public exploit code has been identified at time of analysis.
Local privilege escalation in the battery component shipped with a wide range of MediaTek chipsets (including MT6765, MT6768, MT6853, MT6893, MT6991, MT8186, MT8188 and MT8196) allows an attacker who already holds System privilege to trigger an out-of-bounds write through a missing bounds check, yielding high impact to confidentiality, integrity and availability. No user interaction is required once System access is held, and the flaw is reachable in default configurations of the listed chipsets, making it a post-compromise escalation rather than an initial foothold; the CVSS 6.7 score is dominated by the PR:H prerequisite. A vendor patch is available under MediaTek's October 2026 Product Security Bulletin (patch ID ALPS11276677, issue MSV-9217), and no public exploit code or confirmed active exploitation has been identified at time of analysis.
A missing permission check in the MediaTek AIDL (Android Interface Definition Language) component allows an attacker who already holds the Android System privilege to escalate to higher privileges locally, with no user interaction required. The expected impact is high across confidentiality, integrity, and availability (CVSS 3.1 base 6.7, AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H), but the local-only vector and the PR:H precondition mean an ordinary unprivileged app cannot trigger it directly - it is only useful as a second-stage step in an existing exploit chain or for already-privileged malware. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); this is a moderate, defense-in-depth issue rather than a top-tier emergency.
Privilege escalation in Penpot before 2.18.0 lets a non-owner team administrator promote themselves to team owner by creating or modifying team invitations with the :owner role, since the invitation code path lacked the role-ceiling check that guards update-team-member-role. Exploitation requires the attacker to already hold the team-level 'administrator' role (authenticated, PR:H), and the resulting access is confined to that team's owner-only controls; no public exploit code or confirmed active exploitation was identified at time of analysis, and no EPSS score was supplied. It is a moderate-priority, within-tenant integrity issue rather than an internet-facing emergency.
Device halt - an availability-only denial of service - in Qt for MCUs is triggered when a Text element rendering styled (rich) text encounters an <img> tag with an attribute whose value is empty, causing an internal validation check to fail and the default error handler to abort execution. Per the CVSS vectors (PR:N/UI:N) the trigger is reachable without authentication or user interaction, but exposure is conditional: only applications that parse styled markup and allow attacker-influenced text into the Text element are affected, and plain-text Text elements are not. There is no code execution, data disclosure, or integrity impact, and no public exploit has been identified at time of analysis (CVSS E:U).
Local privilege abuse in Progress Telerik Fiddler Classic for Windows (versions prior to v6.0.20262.10021) lets a low-privileged local attacker plant an attacker-controlled root certificate in the machine's Trusted Root Certification Authorities store by winning a TOCTOU race during Fiddler's one-time HTTPS-decryption certificate trust workflow. The attacker must already have code execution on the host, the legitimate user must initiate the trust operation and approve the UAC elevation prompt, and the substitution of Fiddler's temporary certificate file must land in the narrow window between write and the elevated TrustCert helper's read. No public exploit code has been identified at time of analysis and the flaw is local-only with no remote vector, so this is a conditional, probabilistic privilege-abuse issue rather than an internet-facing emergency.
Path traversal in the k6 MCP server (packaged by Grafana, CPE cpe:2.3:a:grafana:mcp_k6) lets a caller who can already invoke prompts on the server read arbitrary files as the OS user running the server. The convert_playwright_script prompt is documented to accept a script path in '@'-prefixed form, which is confined to the server's working directory, but bare paths and '~'-prefixed paths are handled by a separate undocumented code path that applies no restriction and expands '~' to the user's home directory, making files such as SSH private keys directly addressable; the '@' restriction can also be bypassed with a symlink inside the working directory pointing outside it. All releases from v0.3.0 onward are affected, and v0.3.0/v0.4.0 enforce no restriction on either path form; there is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis, and the impact is bounded by the requirement for prompt-invocation privileges (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
Structured-output validation in vLLM versions prior to 0.30.0 can escape the per-request path and terminate the shared EngineCore process, denying service to every co-tenant on that engine. Three distinct triggers are sufficient on their own: a per-request structured-output backend mismatch that re-raises a grammar compilation exception, the -1 sentinel padding generated by the ngram_gpu speculative-decoding mode being passed as a negative token id to llguidance validation, and a Rust frontend that admits empty structured-output values which the Python frontend correctly rejects. Exploitation requires the ability to submit constrained-generation requests to the inference endpoint (CVSS PR:L, unauthenticated only if the endpoint is exposed without authentication), and the impact is availability-only with no code execution or data exposure; no public exploit code was identified at time of analysis and the flaw is fixed in 0.30.0.
Malformed cache_salt values submitted to vLLM's OpenAI-compatible inference endpoints can crash the EngineCore process and deny service to every concurrent user on deployments configured with the LMCache-MP connector. Only vLLM releases prior to 0.30.0 are affected, and exploitation requires low-privilege API access (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base score 6.5) plus the non-default LMCache-MP connector; a cache_salt containing '@', '/', '\\', or NUL, or longer than 128 characters, raises an uncaught ValueError during scheduler cache lookup. The flaw is fixed in version 0.30.0, and no public exploit code or confirmed active exploitation was identified at time of analysis, making this a genuine but moderate-priority availability issue rather than a high-severity emergency.
Unauthenticated REST API write access in Maestro, the messaging and resourcing component shipped with Red Hat Multicluster Engine for Kubernetes, lets a remote attacker create, modify, or delete consumers and resource bundles without supplying any credentials, token, or session. Because the affected endpoints were registered without authentication middleware (CWE-306), preconditions reduce to network reachability of the Maestro API: deployments where the API is cluster-internal, gated by NetworkPolicy, or fronted by an authenticating gateway/service mesh are materially less exposed, while anything publishing those endpoints are directly exploitable with no user interaction. The exploitability posture is driven by impact rather than by observed activity - integrity is assessed as high and availability as low, and no public exploit code or confirmed in-the-wild exploitation (CISA KEV) was identified at time of analysis.
Missing authorization checks in Penpot prior to 2.18.0 let a holder of a valid share link read design and shape data from pages outside that link's authorized page set, within a file they can already access. Exploitation requires an authenticated Penpot session (the get-page RPC is authenticated, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, base 6.5) plus knowledge of the target page's random UUID, so the impact is limited to read-only information disclosure of design data rather than modification or denial of service. No public exploit code identified at time of analysis, and the flaw is fixed in version 2.18.0.
Improper input validation in vLLM's disaggregated scale-out (token-in-token-out) serving path lets an authenticated low-privilege remote caller send forged multimodal request fields to the /inference/v1/generate endpoint and terminate the shared EngineCore process. Affected are vLLM releases prior to 0.30.0 that are explicitly deployed in the disaggregated scale-out mode; attacks on the cache variant additionally require the attacker to know or induce a victim's content hash so that forged cache identifiers (mm_hashes) match, enabling cross-request encoder-cache poisoning or retrieval and, in the same input-validation failure, corrupted replayed transport semantics from dropped sparse placeholder masks. Both confidentiality and integrity impact are therefore low-severity and preconditional, while availability impact on the shared engine is high; the CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Broken authorization in Ghost CMS versions 5.81.0 through 6.59.x lets an authenticated staff account with the Author role delete posts and pages authored by other users, including through bulk filter-based delete requests. The flaw is a missing primary-author check on the destroy path in the post model's permission logic (CWE-862), rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) - unauthenticated exploitation is not possible, and only multi-author instances with delegated Author accounts are realistically exposed. No public exploit code has been identified at time of analysis and there is no indication the issue has been actively exploited; Ghost fixed the behavior in version 6.60.0.
Authenticated Ghost members can read comments and comment replies they are not authorized to access on sites running Ghost 5.9.0 up to (but not including) 6.44.1. The defect is an authorization/input-validation flaw in the comments subsystem (CWE-943) that lets a low-privileged member account reach a code path intended for administrators, disclosing reply content across membership boundaries; the impact is read-only, with no write, post, or availability effect. Vendor-released patch: 6.44.1, and no public exploit identified at time of analysis.
Unbounded rowspan/colspan attribute handling in Docling 2.0.0 through 2.130.x lets a deliberately crafted document force sustained CPU consumption or multi-gigabyte memory allocation during table parsing, denying service to the process doing the conversion. Four document backends are affected - HTML, JATS, OpenDocument spreadsheet, and BoxNote - and the built-in document_timeout setting does not interrupt the single backend conversion call, so the usual safeguard against runaway parses is ineffective. The flaw is rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H): unauthenticated from the network but requiring the target to ingest the malicious file, with availability as the sole impact. No public exploit code identified at time of analysis, and the vulnerability is fixed in 2.131.0.
Missing authorization checks (CWE-862) in the VillaTheme Lookzy / woo-lookbook WordPress plugin, versions up to and including 1.1.14, let remote unauthenticated attackers invoke plugin functionality that should be protected by access-control and capability checks. Affected sites are those running the plugin (typically alongside WooCommerce) on internet-reachable WordPress installations; per the assessed vector AV:N/AC:L/PR:N/UI:N, exploitation is remote, unauthenticated, and requires no user interaction. Impact is bounded to the plugin's own functionality (integrity and availability low, confidentiality none), and no public exploit code has been identified at time of analysis, so the practical risk is constrained by the narrow population of sites running this specific plugin.
Out-of-bounds read in Google Android's MMS PDU parsing code (PduParser.java) allows a remote attacker who can deliver a crafted or malformed Protocol Data Unit to the device to trigger a denial of service against the affected messaging/telephony component, with no user interaction required. Affected platforms are Android 14, 15, 16, 16-qpr2 and 17, per the EUVD version list and the wildcard CPE cpe:2.3:a:google:android:*; the vulnerability is rated CVSS 6.5 (MEDIUM), though independent review downgrades the availability impact to Low and confirms confidentiality and integrity are unaffected, with no code execution possible. No public exploit code has been identified and SSVC rates the issue as non-automatable with exploitation status 'none', so this is assessed as a moderate, low-priority denial-of-service hardening issue rather than an urgent threat.
Arbitrary file deletion in Feehi CMS 2.1.1 allows an authenticated backend user holding article-edit permission to remove any file that is writable by the PHP/web-server process. The attacker supplies a crafted path through an article's image metadata, which the application concatenates into a filesystem path and passes to unlink() without traversal or directory validation (CWE-22). There is no confidentiality or code-execution impact - the primitive is file deletion only - and no public exploit code has been identified at time of analysis; EPSS is low at 0.24% (14th percentile), consistent with a moderate, not urgent, priority.
Unsafe reflection (CWE-470) in the Unlimited Elements For Elementor (Free Widgets, Addons, Templates) WordPress plugin through version 2.0.22 lets a low-privileged authenticated account steer which class or code the plugin loads, exposing information that account should not be able to read. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, score 6.5) confirms the attacker must hold a valid WordPress login with at least low privileges, that no user interaction is required, and that impact is limited to confidentiality with no integrity or availability effect. There is no public exploit identified at time of analysis and no confirmed actively exploited (CISA KEV) status, so this is a moderate-severity authenticated information-disclosure issue rather than an emergency, though it is worth remediating because the authentication bar is low on multi-author and membership sites.
Missing authorization checks in the UsersWP WordPress plugin (all versions through 1.2.74) allow an authenticated low-privilege user to perform privileged actions that modify site data, with no user interaction required on the victim's part. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N), the barrier to exploitation is a valid low-privileged account - realistically a self-registered subscriber on sites that leave public registration open - after which the attacker gains a high-integrity impact without any data disclosure or denial of service. This is a moderate-risk broken access control (CWE-862) issue; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Keycloak's Dynamic Client Registration flow fails to filter security-sensitive client attributes, allowing an authenticated attacker with a valid Initial Access Token to register a client that bypasses audience checks during token introspection. This results in read-only disclosure of sensitive identity information, roles, and session details from access tokens belonging to other applications in the same realm. The flaw is rated CVSS 6.5 and requires the target realm to have Dynamic Client Registration enabled and the attacker to possess a registration token; no public exploit code or confirmed active exploitation has been identified at time of analysis.
Missing authorization in the WordPress plugin WC Ukraine Shipping (wc-ukr-shipping) through version 1.23.2 lets an authenticated low-privilege user invoke plugin functionality that performs no capability check, allowing unauthorized modification of shipping configuration and related store data. The attack is network-reachable and requires no victim interaction, but it does require a valid session on the target site (PR:L) - a modest barrier that is often trivial to clear on WooCommerce stores that allow open customer registration, and the assessed impact is integrity-only with no confidentiality or availability effect. This is a moderate-risk, not top-priority, vulnerability: no public exploit code has been identified at time of analysis, and there is no indication of confirmed active exploitation (CISA KEV).
Improper access control in the WP User Manager plugin for WordPress, affecting all versions through 2.9.20, allows remote attackers to reach user-management operations they are not authorized to perform, resulting in privilege abuse (CVSS 6.5, CWE-284). The published vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) indicates unauthenticated, remote reachability with low confidentiality and integrity impact, although the Patchstack classification of this as a privilege-escalation issue suggests a pre-existing low-privileged WordPress account may be the practical prerequisite; that prerequisite should be confirmed against the vendor advisory. There is no indication of confirmed active exploitation (not in CISA KEV), and no public exploit code was identified at time of analysis; patch status is not established in the available data, so sites running the plugin should treat 2.9.20 and earlier as vulnerable pending a fixed release.
Missing authorization in the Arraytics Timetics WordPress plugin (versions through 1.0.63) lets remote attackers trigger plugin actions that lack proper access-control checks, allowing limited integrity and availability impact on affected sites (CVSS 6.5, CWE-862). The assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L confirms exploitation is unauthenticated and requires no victim interaction, though the impact is bounded - no confidentiality loss - and any WordPress installation running the vulnerable plugin with the affected endpoint reachable is exposed. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue was reported by Patchstack, and the affected range ends at 1.0.63.
Denial of service in the Apache Struts REST plugin affects Struts 2.1.8 through 2.3.37, 2.5.0 through 2.5.33, 6.0.0 through 6.11.0, and 7.0.0 through 7.3.0: a remote unauthenticated request with an oversized body is read into memory without any size bound, letting a single request exhaust the Java heap and deny service to other users. Exposure is limited to applications that actually deploy the optional REST plugin and accept request bodies - Struts core is unaffected, and the vendor confirms that no additional setting has to be enabled for a default REST-plugin deployment to be reachable, while form submissions and multipart uploads are not parsed by the affected code path. No CISA KEV listing, public exploit code, or EPSS score was present in the source data, so active exploitation is not confirmed; vendor-fixed releases 6.12.0 and 7.4.0 cap request bodies at 2 MB (2,097,152 characters) by default.
Incorrect authorization in Rapid7 Velociraptor allows an authenticated user with the LABEL_CLIENTS permission to alter server-wide metadata via the SetClientMetadata operation, which should be restricted to server administrators. The flaw is rated CVSS 3.1 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) and classified as CWE-863 (Incorrect Authorization), producing high integrity impact with no confidentiality or availability impact. No public exploit code or confirmed active exploitation was identified at time of analysis; the primary risk is privilege escalation for insiders or compromised low-privilege accounts, with impact scaling to how broadly LABEL_CLIENTS is delegated in a given deployment.
Stored cross-site scripting (XSS) in the Webful Creations RepairBuddy WordPress plugin (computer-repair-shop) through version 4.1225 allows an authenticated attacker with low-level privileges to inject malicious JavaScript into fields such as repair tickets or customer records. The payload is stored and later executed when a privileged user views the affected page, potentially leading to session hijacking or unauthorized actions on behalf of the victim. Rated CVSS 6.5 (Medium), exploitation requires a valid account and victim interaction; no public exploit code has been identified at time of analysis.
Stored cross-site scripting in the GhozyLab Image Slider Widget WordPress plugin (versions through 1.1.130) lets an authenticated low-privilege user - a contributor or author able to submit content - inject script into slider fields that executes in the browser of any administrator or editor who later views the rendered slider. CVSS 3.1 rates this 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L), reflecting mandatory authentication (PR:L), required victim interaction (UI:R), and scope change because the payload escapes the plugin's context into the broader WordPress page. No public exploit identified at time of analysis, and the plugin is not in CISA KEV.
Stored cross-site scripting in the Brainstorm Force Starter Templates (astra-sites) WordPress plugin, affecting all versions through 4.7.7, allows an authenticated user with only low-level privileges to plant persistent JavaScript that executes in the browser of a higher-privileged user (such as an administrator or editor) who later views the affected page. Rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), exploitation consumes a valid low-privilege account plus victim interaction, so it is not remote-unauthenticated and the realistic attacker population is limited to sites that permit untrusted registration or loose role assignment. There is no CISA KEV listing and no public exploit code identified at time of analysis; risk is moderate and warrants routine rather than emergency patching.
Stored cross-site scripting in the WordPress plugin Name Directory (versions through 1.34.2) lets an authenticated attacker with low privileges (PR:L) save a script payload into directory content that executes in the browser of any user who later views the affected page (UI:R). Because the injected content persists, a single submission can fire for administrators or visitors on every subsequent page load, though the attacker must already hold an account able to author or edit Name Directory entries and the payload remains inert until someone else opens the page; per the CVSS vector PR:N is absent, so this is an authenticated-context issue rather than an unauthenticated one. The independent assessment rates it CVSS 3.1 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L), with impact confined to browser-context script execution and no public exploit identified at time of analysis.
Stored cross-site scripting in the Presto Player WordPress plugin (Brainstorm Force) through version 4.5.2 lets an authenticated attacker with at least low-level content-contribution privileges save a malicious payload into a Presto Player field, which then executes in the browser of any user who views the affected page. Because the assessed vector is PR:L/UI:R with a scope change (S:C), the attacker cannot be fully anonymous and the impact depends on a second, potentially privileged victim loading the stored content, which is why this is rated medium severity at CVSS 6.5. There is no public exploit identified at time of analysis and no confirmed active exploitation; the only public reference is the Patchstack advisory.
Stored cross-site scripting (XSS) in the LeapWorx Premium Addons for Elementor WordPress plugin, affecting versions through 4.11.109, allows an authenticated low-privileged user (contributor/author level, PR:L) to persist malicious script into plugin-handled content that executes in the browser of a higher-privileged victim who later views it (UI:R). Successful exploitation can lead to session theft, credential harvesting, or administrative actions performed in the victim's context, though it requires valid account access and victim interaction rather than being a zero-click or unauthenticated attack. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (not in CISA KEV); EPSS data was not available for this CVE. The reported CVSS 3.1 base score is 6.5 with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L.
Stored cross-site scripting in the Sonaar MP3 Audio Player for Music, Radio & Podcast WordPress plugin (all versions through 5.14.2) lets an authenticated low-privilege user persist malicious script content that executes in the browser of any user who later views the affected page. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N (vendor score 6.5), meaning exploitation requires a valid account on the target WordPress site plus a victim who loads the rendered content, so real-world risk is concentrated on sites that grant accounts to untrusted or self-registered users. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS score was supplied with the available data.
Stored cross-site scripting in the GiveWP WordPress donation plugin (versions through 4.17.0) lets an authenticated user with only low-level privileges persist a script payload that executes in the browser of any user who later views the affected page. Because the injected code runs in the origin of the WordPress site (CVSS scope change: S:C), an attacker who convinces an administrator to open the poisoned screen can steal session cookies, harvest nonces, or perform privileged actions as that administrator. A vendor/Patchstack CVSS 3.1 base score of 6.5 (Medium) applies, exploitation requires an authenticated account plus victim interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Stored cross-site scripting in the bPlugins B Blocks WordPress plugin (all versions through 2.1.8) lets an authenticated user with posting privileges inject persistent JavaScript that executes in the browser of any privileged user who subsequently views the crafted block content. Rated CVSS 6.5 (medium), exploitation requires a low-privileged WordPress account and victim interaction, but it can lead to session theft, defacement, or administrative actions performed under the victim's identity. No public exploit code or active exploitation has been identified at time of analysis.
Stored cross-site scripting in the WordPress plugin Image Photo Gallery Final Tiles Grid (final-tiles-grid-gallery-lite, WP Chill) through version 3.6.13 lets an authenticated low-privileged user - a contributor, author, or equivalent role permitted to submit gallery content - inject script that is stored server-side and later rendered in the browser of any victim who views the affected gallery page, including administrators. Because the CVSS vector is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L (score 6.5, Medium), successful exploitation requires a valid low-privileged account plus a second human interaction step (the victim loading the tainted page), and impact is confined to the victim's browser session rather than the underlying server. No public exploit code has been identified at time of analysis, and no CISA KEV entry indicates active exploitation; the risk is elevated on multi-author sites, membership sites, or any installation that allows untrusted users to register or post gallery content.
SQL injection in ApiAdmin 5.0 and earlier allows a low-privilege authenticated user to read arbitrary data from the backend database by supplying crafted input in the gid parameter of the user-list endpoint GET /admin/User/getUsers. The vulnerability requires an authenticated session to the ApiAdmin administrative area (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), so an unauthenticated outsider cannot trigger it directly, and impact is bounded to confidentiality (high) with no integrity or availability effect. Publicly available exploit code exists per the SSVC assessment (Exploitation: poc), but there is no indication of confirmed active exploitation, and EPSS is low at 0.15% (4th percentile), consistent with a medium-severity, moderate-risk issue rather than a broad internet-wide threat.
Missing authorization in the WP VR WordPress plugin (WPFunnels Team) allows an authenticated low-privileged user to invoke privileged plugin functionality that should be restricted, affecting every version through 9.1.3. Exploitation requires a valid account on the target site (CVSS PR:L) plus a user-interaction step (UI:R), and the resulting impact is limited to low confidentiality, integrity, and availability loss under a changed scope, for a base score of 6.5. No public exploit identified at time of analysis, no CISA KEV listing, and the supplied intelligence does not name a fixed plugin version.
Stored cross-site scripting (CWE-79) in the Themepoints 'Logo Showcase' WordPress plugin, affecting all versions through 4.0.4, allows an authenticated low-privileged user to persist malicious script into a logo showcase entry that executes in the browser of any user who later views the rendered page. Because the input is stored rather than reflected, a single submission can fire against administrators or site visitors repeatedly, and the CVSS:3.1 vector (PR:L, UI:R, S:C) confirms that exploitation requires at least a contributor/author-level account on the WordPress site plus victim interaction with the poisoned page. Per Patchstack's report, no public exploit code was identified at time of analysis and there is no indication of confirmed active exploitation (not in CISA KEV); the plugin's limited install base and the need for a content-submission account keep practical risk moderate rather than critical.
Stored cross-site scripting in impleCode's eCommerce Product Catalog plugin for WordPress (versions through 3.6.2) allows an authenticated user holding only low-level privileges to plant malicious JavaScript in catalog content, which then executes in the browser of any user - typically an administrator - who views the affected catalog page. The issue is rated CVSS 3.1 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L), and the available intelligence shows no public exploit identified at time of analysis and no vendor-released patch version confirmed in the provided data. Real-world risk is constrained because the attacker needs some authenticated role on the target site and must wait for a victim to load the poisoned page, and the plugin has to be installed and active - it is a niche e-commerce plugin rather than a default WordPress component.
QR Redirector WordPress plugin through 2.0.5 allows an authenticated low-privilege user to store malicious input via its redirect-entry functionality, which then executes in the browser of a higher-privileged victim who views the affected page. This is a moderate-severity stored cross-site scripting issue tracked as CVE-2026-105069 (CVSS 6.5, CWE-79); exploitation requires an authenticated account and victim interaction, and no public exploit identified at time of analysis.
Cross-tenant issue manipulation in Plane (open-source project management tool) before 1.4.0 lets an authenticated user add issues from any workspace into a cycle they control by supplying arbitrary issue UUIDs, and when a victim issue already belongs to another cycle the operation reassigns it, silently removing it from the victim's cycle. The flaw is a user-controlled-key authorization bypass (CWE-639/IDOR) in the cycle-issues endpoint, scored CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) because it requires a valid account (PR:L) and requires the attacker to know or enumerate victim issue UUIDs, which are not trivially guessable and constrain opportunistic abuse. Vendor-released patch: 1.4.0. No public exploit identified at time of analysis; realistic impact is concentrated on multi-tenant or shared Plane deployments where untrusted users share an instance.
Plane's project member roster API (GET /api/v1/workspaces/{slug}/projects/{project_id}/members/) leaks the full membership list of a private project - including each member's email address, name, display name, avatar, and role - to any authenticated user who belongs to at least one project in the same workspace, including a Guest. The flaw is in the DRF permission class ProjectMemberPermission, whose SAFE_METHODS branch validated only workspace-scoped project membership without binding the check to the requested project_id, while the view filtered records solely on the URL-supplied project_id. Only Plane versions prior to 1.4.0 are affected, no public exploit code has been identified at time of analysis, and the impact is read-only disclosure of member PII (personally identifiable information) with no write or availability effect; an attacker must already hold a valid account and know or enumerate the target project's ID.
Improper authorization in Plane (makeplane) prior to 1.4.0 allows an authenticated workspace member or guest who is not a member of a victim's secret project to download that project's private file assets through the workspace-scoped endpoint GET /api/assets/v2/workspaces/{workspace_slug}/download/{asset_id}/, which issues a 302 redirect to a signed download URL instead of enforcing project membership. The flaw is a broken-access-control/IDOR issue (CWE-639) rated CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), with confidentiality-only impact and no integrity or availability effect; exploitation requires a valid workspace-authenticated session plus knowledge of the target FileAsset UUID, and only project-bound asset types (ISSUE_ATTACHMENT, COMMENT_DESCRIPTION, PAGE_DESCRIPTION, PROJECT_COVER) are exposed, while workspace-level assets with a null project_id are unaffected. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; a vendor fix is available in Plane 1.4.0 (PR #9372, commit e63f0c3b3404d669ae05dd9050aab72292f87e5c).
SQL injection in the maestro component of Red Hat Multicluster Engine for Kubernetes (MCE) allows remote attackers to perform read-only blind extraction of database contents through the orderBy parameter on REST API list endpoints. The vendor CVSS vector specifies PR:L, indicating a low-privileged authenticated account may be needed, while the description and independent assessment note that authentication may not be required; defenders should resolve this discrepancy because it changes exposure materially. At time of analysis there is no public exploit identified, and exploitation is constrained by blind, read-only extraction and the requirement for network reachability to the vulnerable MCE API; CVSS is 6.4 medium severity.
Server-side request forgery (SSRF) in Event Gallery for Joomla before 6.6.0 allows an attacker to make the server send the Google Photos OAuth access token to an arbitrary address or probe internal network resources. The vulnerability resides in the back-end upload page's Google Photos picker, which fetches image thumbnails using a user-supplied address without validation and without a form token, enabling exploitation via CSRF against a logged-in administrator or directly by a back-end user with 'Manage' permission. No public exploit code has been identified, and the risk is assessed as moderate and targeted.