Plane prior to 1.4.0 leaks cycle and module metadata from private projects to any authenticated member of the same workspace, because the WorkspaceCyclesEndpoint and WorkspaceModulesEndpoint filter results only by workspace__slug rather than by project membership. A low-privileged user such as a Guest with access to a single project can enumerate cycle and module names, descriptions, sprint dates, issue counts, progress snapshots, external integration IDs, linked URLs, and member lists belonging to projects they were never added to. The issue is fixed in 1.4.0 via upstream commit b3591b9e; there is no public exploit identified at time of analysis, and the assessed CVSS is 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), reflecting an authenticated, read-only confidentiality impact.
Authenticated staff holding the Editor or Super Editor role in Ghost CMS versions 0.5.0 through 6.63.x can escalate the privileges of Author and Contributor accounts by assigning their own Editor role to those users through the Ghost Admin API, even though they lack permission to grant that role. The flaw is bounded - attackers can only confer their own Editor-level role and cannot push targets to Administrator or Owner - and exploitation requires an existing, trusted staff account rather than outsider access. No public exploit code was identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but the vendor released a fix in version 6.64.0, so unpatched, multi-role Ghost publications should upgrade promptly.
Missing authorization checks in the WordPress Event Tickets plugin from Liquid Web / StellarWP (versions through 5.30.0) allow an authenticated low-privilege user to carry out restricted ticket-related actions they should not be permitted to perform, resulting in limited integrity impact with no data disclosure or denial of service. As confirmed by the CVSS vector (PR:L), exploitation requires a valid account on the target site at a low privilege level - typically a self-registered subscriber, customer, or event attendee - so sites that allow open user registration carry more exposure than those with registration closed. No public exploit code has been identified at time of analysis and the issue is not reported as actively exploited; the assessed severity is low (CVSS 4.3), making this a genuine-but-low-priority hardening item rather than an emergency patch.
Information disclosure in the WP SYNTEX Polylang WordPress plugin through 3.8.7 lets an authenticated low-privileged user bypass a missing authorization check (CWE-862) and retrieve embedded sensitive data they are not entitled to access. The issue carries a CVSS 3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N): exploitation is network-reachable, low complexity and needs no user interaction, but requires a valid account with at least low privileges such as a default Subscriber, with no impact to integrity or availability. No public exploit code has been identified at time of analysis and the issue is not confirmed as actively exploited (not in CISA KEV), so exposure is materially higher on sites that permit open user registration or host many low-trust accounts than on sites with restricted account creation.
Missing authorization checks in the WordPress plugin WP Admin Audit (Brandtoss) through version 1.2.17 let an already-authenticated low-privilege user reach plugin functionality and audit data they are not permitted to see. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) the attacker must hold a valid account on the target site, so the flaw is not anonymously exploitable, and the impact is limited to confidentiality with no integrity or availability effect. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; severity is moderate (vendor-reported 4.3), with the main risk being disclosure of audit-log information to subscribers or other low-privilege accounts.
Missing authorization checks in the WordPress plugin WP Dummy Content Generator (all versions through 4.0.0) let an authenticated low-privilege user - a subscriber or contributor, per the CVSS vector's PR:L - invoke plugin functionality that should be reserved for higher-privileged roles, producing a limited integrity impact (CVSS 3.1 score of 4.3, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, CWE-862). Exploitation requires the plugin to be installed and active and the attacker to hold valid credentials for a registrable low-privilege account, with no user interaction needed, and the effect is confined to modification of content the plugin manages rather than disclosure or denial of service. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV listing); no EPSS score was supplied in the source data, so the residual risk is low-to-moderate and is highest on sites that permit open self-registration.
Information disclosure in Penpot prior to 2.18.0 lets a holder of a page-scoped share link pull comment threads and full comment bodies from pages they were never granted access to within the same file, exposing commenter names, email addresses, profile photos, and internal page identifiers; those leaked page IDs can then be chained with other page-reading functionality to reach unshared design content. The flaw sits in the get-comment-threads, get-comment-thread, and get-comments RPC commands, which called the comment permission check but never enforced the share link's :pages restriction; exploitation requires an authenticated party (CVSS PR:L) who already possesses a valid page-scoped share link, so it is not anonymous access to arbitrary files. Risk is moderate and confidentiality-only (CWE-200, CVSS 4.3), there is no public exploit identified at time of analysis and no CISA KEV listing, and the issue is fully remediated in Penpot 2.18.0, so instances on 2.18.0 or later are not affected.
Authenticated cross-workspace issue linking in Plane versions prior to 1.4.0 lets a user who holds a valid account in any workspace attach issues belonging to a different workspace to modules, cycles, relations, or sub-issues inside their own workspace by passing foreign issue UUIDs in the URL path. The flaw is an object-reference authorization gap (CWE-639) scored CVSS 4.3 with integrity-only impact (I:L, C:N, A:N); it requires knowledge of a specific victim issue UUID, which Plane generates as a non-enumerable 128-bit identifier, making practical exploitation opportunistic rather than broad. No public exploit code has been identified at time of analysis, and CISA KEV does not list this CVE; a vendor-released patch exists in Plane 1.4.0.
Cross-site scripting in Red Hat Quay 3 lets an unauthenticated remote attacker execute arbitrary script in a victim's authenticated browser session by tricking the user into completing login through a crafted URL, because the application does not validate the post-login redirect destination before navigating. Exploitation is tightly constrained: the deployment must be configured with direct database authentication (installs delegating to OIDC/LDAP/SSO are unaffected) and the victim must both click the malicious login link and finish authenticating through it. Severity is low-to-moderate (CVSS 4.2, AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N), impact is confined to the victim's own session, and no public exploit identified at time of analysis.
vLLM versions prior to 0.30.0 derive the flash late-interaction query-cache key from the caller-controlled X-Request-Id header, so an authenticated API caller on a shared deployment can collide with a victim's in-flight request and cause the victim's documents to be scored against the attacker's query through the /score and /rerank endpoints, while shared use counters can also give rise to a late-interaction cache-miss error. The assessed vector is CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L (base 4.2), reflecting a narrow concurrency race that requires knowledge of or a lucky guess at the victim's request identifier, and no confidentiality impact; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV). The issue is fixed in vLLM 0.30.0, and the practical risk is confined to multi-tenant or otherwise shared deployments that actually enable the flash late-interaction scoring path.
Server-side request forgery (SSRF) in Ghost CMS versions 6.0.9 through 6.64.x lets an unauthenticated remote attacker induce the server to issue limited HTTP requests to hosts on its internal network. The flaw is blind - no response body is ever returned to the attacker - so the practical value is confined to request-triggered side effects and liveness/timing inference rather than data exfiltration, and exploitation depends on the target deployment actually having reachable internal hosts (e.g. NAT64/DNS64 setups or flat internal networks). The vendor fixed the issue in Ghost 6.65.0; no public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV, consistent with the assessed CVSS 3.1 score of 4.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N).
Blind server-side request forgery (SSRF) in Ghost CMS versions 6.54.1 through 6.64.x lets an unauthenticated remote attacker coerce the server into issuing limited HTTP requests to hosts on its internal network, using functionality such as the Webmentions feature to submit attacker-controlled URLs that are later fetched by Ghost's oembed/bookmark/favicon pipeline. The impact is constrained: no response body is returned to the attacker, so the attack yields only internal-host reachability probing rather than data exfiltration, and exploitation depends on winning a DNS-rebinding race (AC:H per the assessed vector, overall CVSS 4.0). No public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation; the vendor-released patch is Ghost 6.65.0.
A use-after-free class defect in the Linux kernel's virtio-gpu paravirtualized GPU driver is exposed through the resource-mapping cleanup path when blob-backed scanouts are torn down, potentially allowing memory corruption. Only local users running inside a virtual machine guest that exposes a virtio-gpu device and who are able to open the DRM/render node and allocate blob-backed scanout resources can reach the vulnerable code, per the assessed vector AV:L/AC:H/PR:L/UI:N with high confidentiality, integrity and availability impact - there is no remote or unauthenticated path implied. Exploitation is judged difficult because it depends on specific cleanup ordering/timing; no public exploit code has been identified at time of analysis, and the defect is not listed in CISA KEV.
Risk cannot be meaningfully assessed from the provided data: CVE-2026-94291 carries no published description, no CVSS score or vector, no CWE classification, and no named product, component, or version. The only intelligence signal in this dataset is that the record was reported through the Ubuntu security feed, which indicates that an Ubuntu-packaged component is affected, but neither a Ubuntu Security Notice nor an upstream advisory is included here, so the affected subsystem, attack surface, and prerequisites are all undefined. Exploitation status is unconfirmed - the CVE is not marked as confirmed actively exploited (CISA KEV), no publicly available exploit code exists in the supplied data, and no EPSS score was provided; authentication requirements not confirmed from available data.