HTTP request smuggling in Progress Telerik Fiddler Classic for Windows (versions prior to v6.0.20262.10021) allows a low-privileged local user sharing the same Fiddler proxy instance to desynchronize requests and poison responses delivered to other users. Fiddler forwards conflicting multiple Content-Length headers verbatim to the origin while framing the body using only the first value, and because the server connection is returned to Fiddler's pipe pool after reading only the first response, an unread smuggled response stays buffered on the socket and is served to the next session that reuses it. Exploitation is authenticated (CVSS vector PR:L), local-only (AV:L), and high complexity (AC:H), requiring a non-RFC-9110-compliant keep-alive origin server; no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a fix.
apko truncates out-of-range UID and GID values that it parses from package-supplied /etc/passwd and /etc/group entries, so a crafted package can make an account that appears unprivileged be written into the resulting image as UID 0 / GID 0 (root). An attacker must first control a package installed into the image being built - a supply-chain foothold rather than arbitrary remote access - and the impact is confined to the produced image's file ownership and its resolved run-as user, not the build host itself. The flaw affects apko versions 0.2.0 up to but not including 1.4.5 on 64-bit platforms; it is rated 6.3 under CVSS 4.0 (independently assessed as AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N on CVSS 3.1), and no public exploit code or confirmed active exploitation was identified at time of analysis. Vendor-released patch: 1.4.5.
A double-free flaw in MediaTek's AI Processing Unit (APU) component allows a locally executing attacker - such as a malicious or compromised installed application - to crash an affected device, producing a local denial of service. Per the assessed CVSS vector (AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), no authentication, elevated privileges, or user interaction are required once local code execution is achieved, and the impact is limited to availability; there is no data exposure or code-execution gain from this defect. Exploitation is confined to devices built on the enumerated MediaTek chipsets (MT8781, MT6899, MT8668, MT8910, MT6993) running unpatched firmware; no public exploit code has been identified at time of analysis and the issue is not listed as confirmed actively exploited (CISA KEV).
PHP object injection in FacturaScripts before version 2026.7 allows an authenticated attacker to delete arbitrary files on the server, causing denial of service and potentially enabling a reinstall hijack that resets the application. The flaw is reachable through the multiple-select handling path in WidgetSelect::processFormData(), which passes raw POST data to unserialize() without restricting allowed classes; submitting a crafted serialized XLSXWriter object triggers its __destruct() destructor, which performs the file deletion (config.php and backup data are the notable targets). Exploitation requires a valid authenticated session (CVSS 4.0 vector reports PR:L, so an account is mandatory), and no public exploit code has been identified at time of analysis, so priority is moderate rather than urgent. The vendor has released the fixed 2026.7 version.
Stored cross-site scripting in Bacularis 5.4.0 through 6.5.1 allows an attacker to write script content into the "Organization name" field, which is then rendered unsafely and executes in the browser of any user who views the affected page. The independent assessment rates this moderate at CVSS 6.1, and it requires an authenticated account holding organization create/edit rights plus victim interaction - a separate user, typically an administrator, must load the view that renders the stored name - with impact confined to the browser session and no direct server compromise. The supplied CVE record vector lists PR:N, but the assessed vector and exploitation conditions indicate PR:L is correct; exploitation status is no public exploit identified at time of analysis, upstream detection is minimal, and EPSS is low at 0.15% (4th percentile), though the 6.1 score together with a scope-changing (S:C) XSS in an administrative interface keeps this relevant for defenders who have not yet reviewed stored organization data.
Server-side request forgery in Penpot before 2.18.0 allows an authenticated user who controls a media-import URL, or an administrator who controls a webhook URL, to reach internal and cloud-metadata endpoints by supplying IPv6 transition addresses (NAT64 64:ff9b::/96, 6to4 2002::/16, or Teredo 2001:0000::/32) that embed a blocked IPv4 destination such as 169.254.169.254, 127.0.0.1, link-local, or RFC1918 addresses. The bypass works because the backend blocklist app.util.ssrf/blocked-address? applies its extra CIDR checks only to IPv4 values and relies on Java InetAddress predicates that do not classify transition-mechanism addresses; exploitation further requires the request to traverse a NAT64 gateway or the attacker to control a DNS AAAA record the Penpot server resolves, with cloud environments that already run DNS64/NAT64 directly exploitable, while non-NAT64 deployments depend on the harder attacker-controlled AAAA path. Media import can disclose response bodies, whereas webhook delivery exposes only response status as a network-probing side channel, and there is no public exploit identified at time of analysis. Penpot 2.18.0 is the vendor-released fix (commit 326d83e780ae120b45ccd6f3d7bd24922b54461c).
BuildKit (moby/buildkit) contains a policy-validation bypass in which a specially crafted Git source build step makes a repository appear to originate from a different remote URL than the one actually used during git clone, so repository-identity or URL-based policy rules can be evaded. The issue affects BuildKit builds prior to v0.33.1 and requires an attacker to hold build-submission privileges (CVSS vector PR:L); policies that validate commit SHA, commit data, or cryptographic signatures continue to apply correctly, which limits the practical impact (vendor CVSS 4.0 base 6.0, independent assessment 3.1 base with AC:H, low confidentiality and high integrity impact, no availability impact). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the vendor reports a patch is available.
Login cross-site request forgery in the Chaterm desktop client before 0.12.1 allows unauthicated remote attackers to inject a forged login state by triggering a crafted chaterm:// OAuth deep-link callback that the client neither signs nor validates against the original state parameter. A victim only needs to visit an attacker-controlled page while the chaterm:// handler is registered; the client then completes login as the attacker's account, and if default data sync is enabled, saved hosts, passwords, and private keys are uploaded into that attacker-controlled account. Exploitation is conditional rather than trivial - it requires victim interaction and a reachable callback/login state (AC:H, AT:P), and the confidentiality impact scales with how many secrets the victim has stored; there is no confirmed active exploitation and no public exploit code identified at time of analysis, and the vendor has released the fix in 0.12.1, which adds RSA-SHA256 signature verification of deep-link callbacks plus time-bound pending-state tracking.
BuildKit, the container build engine used by Docker and exposed through `docker build`/buildx, can be tricked into performing file operations on special file inodes - device nodes, FIFOs, or sockets - at paths where it expects ordinary regular files, a confused-deputy condition (CWE-441). A user who builds an attacker-controlled Dockerfile or build context can therefore cause build operations to hang/block, and on rootful workers can obtain unintended access to host devices; rootless configurations are effectively limited to availability and integrity effects. The attack is local and requires the victim to actively run a build on the malicious input, so exposure concentrates in multi-tenant or untrusted-source CI/CD pipelines that use rootful BuildKit workers; no public exploit has been identified at time of analysis and the flaw is not in CISA KEV. This is best treated as a medium-severity, defense-in-depth hardening issue rather than an urgent remote-exploitation priority.
Unauthenticated retrieval of customer-uploaded files is possible in the File Uploads Addon for WooCommerce WordPress plugin (versions 1.7.2 through 1.7.6), which stores customer submissions in a publicly web-accessible uploads directory while the access restriction it generates fails to actually block direct requests; an attacker who knows or can guess a file's name can fetch it straight from the web root, bypassing the plugin's authenticated download mechanism. The issue is a broken access control / insecure direct object reference problem (CWE-284) rather than a true authentication bypass, and only confidentiality of already-uploaded files is affected - no integrity or availability impact. Rated CVSS 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N), the attack is unauthenticated and needs no user interaction, but the High attack-complexity component reflects that the attacker must correctly guess or otherwise learn the target filename; there is no public exploit identified at time of analysis and no evidence of confirmed active exploitation (CISA KEV).
Unauthenticated disclosure of other customers' uploaded files is possible through the File Uploads Addon for WooCommerce WordPress plugin in versions 1.7.2 through 1.7.5, because the plugin serves stored uploads without verifying that the requester is the customer who originally uploaded the file (CWE-639). An attacker who knows or guesses the exact file name of a previously uploaded file can retrieve it over the network with no account and no user interaction, as reflected by CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (5.9 Medium) - the High attack complexity stems entirely from the file-name discovery prerequisite, so real-world difficulty hinges on whether the plugin generates guessable or sequential names versus long random tokens. There is no public exploit identified at time of analysis, and the vendor has released a fix in 1.7.6.
BuildKit can cache a fetched snapshot under a claimed content digest without adequately verifying that the blob bytes match that digest, letting an attacker who controls or compromises a registry or OCI-layout blob source poison the cache and compromise the integrity of later victim builds that reuse that digest. The attacker does not need credentials per the CVSS PR:N vector, but they must be able to serve BuildKit blob requests, and a victim must run a build against the attacker-influenced source for exploitation to matter. No public exploit was identified at time of analysis; vendor patch v0.33.1 is available, and an independent assessment rates this as a moderate, conditions-dependent integrity flaw rather than a drop-everything emergency.
Penpot versions prior to 2.18.0 leak the contents of other users' in-progress uploads because the backend assemble-chunks routine fetches an upload session by ID alone instead of scoping the lookup to the calling account. An authenticated attacker (PR:L) who comes to know a victim's live, completed-but-not-yet-assembled upload-session UUID can assemble the victim's stored chunks into the attacker's own file, team font, or project import - reading the uploaded bytes (C:H) and wiping the victim's pending session (A:L). Successful abuse is gated by the UUID's randomness and the brief window before the session is consumed, which the assessed vector captures as AC:H; no public exploit code or CISA KEV entry is associated with this issue at time of analysis.
Logout in Penpot versions prior to 2.18.0 clears the browser's auth-token cookie but leaves the matching server-side session record in the http_session_v2 table intact, so a previously captured session token continues to authenticate requests with the victim's authority until it naturally expires. This is a medium-severity session-management flaw (CVSS 5.9, CWE-613) rated with a network vector, no privileges required (PR:N), and user interaction (UI:R) - although in practice an attacker must first obtain a valid token through a separate vector such as a shared machine, interception, or XSS, and only that specific captured session is affected. The vendor addressed the issue in the 2.18.0 release and via fixing commit 7c85837, and no public exploit code has been identified at time of analysis.
Server-side request forgery in Docling 2.91.0 through 2.131.x lets an attacker-supplied document reach internal services whenever remote document fetching is explicitly enabled, because validate_url_safety in docling/backend/utils/image_resource_loader.py performs only a single IPv4 lookup before the HTTP client re-resolves and parses the original URL. The same trust gap applies to HTMLBackendOptions(render_page=True), which issues HTTP and HTTPS browser requests without validating their resolved destination, so exploitation also covers DNS rebinding, mixed public/internal address records, and backslash-authority parser disagreement. Exploitation is gated by non-default configuration (fetch_images=True with enable_remote_fetch=True, --html-image-fetch remote, or render_page=True), requires the attacker to supply a processed document and win a rebinding timing race, and exposure is limited to responses successfully decoded as images or passively captured in a page screenshot; CVSS 3.1 is 4.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N), no public exploit identified at time of analysis, and the issue is fixed in 2.132.0.
Moby BuildKit (all versions in the affected range per the unbounded CPE cpe:2.3:a:moby:buildkit:*:*:*:*:*:*:*:*) can be made to run its cleanup routine against a modified CA bundle when proxy networking with CA injection is enabled, a time-of-check-to-time-of-use (CWE-367) race that causes cleanup to block, operate outside the build rootfs, or fail without failing the build. The attacker must be able to submit or execute a build on the builder (local, low-privilege access; PR:L) and must first change the build's injected CA bundle before cleanup runs; the non-default proxy-with-CA-injection mode sharply narrows exposed deployments, and the dominant consequence is availability and integrity of the cleanup operation (VA:H, VI:L) rather than confidentiality loss. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; vendor-released patch v0.33.1 is available.
Stored cross-site scripting in Zabbix lets a crafted email media type configuration run arbitrary JavaScript in the browser of the Super Admin who approves it: the media type's OAuth form passes the attacker-controlled 'Authorization endpoint' value directly to window.open() without validating the URL scheme, so a javascript: URL executes in the frontend's origin. Exploitation is authenticated and interaction-dependent - the payload must first be delivered as an import file by a user with high frontend privileges (PR:H), and a Super Admin must then open that media type's OAuth form and actively click to grant consent (UI:A / UI:R) - which is consistent with the published CVSS 4.0 base score of 5.6 and our assessed CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:L/A:N. No public exploit code and no confirmed active exploitation were identified at time of analysis, so although the flaw is genuine and script execution occurs in a highly privileged session, it is a constrained medium-severity issue rather than a mass-exploitation priority.
Keycloak's User Session Note protocol mapper fails to screen session note keys for sensitive internal credentials, allowing an authenticated delegated client administrator to copy a victim's upstream federated access/bearer token into tokens issued to the application they manage (CVSS 3.1 5.7, AV:N/AC:L/PR:L/UI:R, C:H/I:N/A:N). Exploitation requires the attacker to hold scoped client-administration rights sufficient to configure protocol mappers, a realm federated with external identity providers that persist upstream tokens as user session notes, and the victim to actually authenticate to the attacker-controlled client, so impact is decisive only in federated-token deployments and default configurations without federated token storage are not exposed. Red Hat has published an advisory and Bugzilla record for the issue, but no public exploit code and no confirmed active exploitation were identified in the available intelligence at time of analysis.
A malicious external BuildKit frontend can issue crafted requests against the daemon's internal API that trigger a data race, causing the BuildKit daemon to panic and crash. The issue affects BuildKit deployments where the operator has opted into running an untrusted or attacker-controlled frontend (for example through a `# syntax=` reference to a third-party image); default builds that use trusted first-party frontends are not exposed. It is a medium-severity denial-of-service condition: exploitation requires low-level privileges (PR:L) through the frontend channel, local access (AV:L), and successful timing of a race (AT:P), and there is no public exploit identified at time of analysis. A vendor fix is available in BuildKit v0.33.1.
Missing authentication in the Admin Signup component (admin/signup.php) of the kishor-23 Food Waste Management System allows remote, unauthenticated attackers to manipulate the 'sign' argument and bypass the intended signup/authentication check, resulting in limited confidentiality, integrity, and availability impact on the affected endpoint. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, E:P) confirms the attack is network-reachable, requires no credentials or user interaction, and that publicly available exploit code exists; there is no CISA KEV entry, so active exploitation in the wild is not confirmed. Real-world risk is modest: the project is an obscure open-source PHP application, generally not deployed at production scale, and the project has not responded to the issue report, meaning no patched release is available.
Authenticated path traversal in the Mitel MiVoice Office 400 web management portal (TCP 443) lets a high-privilege maintenance or administrator user read files outside the intended system logs directory by supplying crafted path input to the Maintenance → System Logs download function. Only users who already hold valid high-privilege portal credentials can trigger it (CVSS vector PR:H), and the impact is limited to confidentiality - files can be read or downloaded, but there is no write, code-execution, or denial-of-service capability. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the assessed risk is moderate rather than critical because exploitation is gated behind authenticated administrative access to an interface that should normally be restricted to trusted networks.
Unauthenticated SQL injection in the signup.php user-registration endpoint of the kishor-23 food-waste-management-system allows remote attackers to manipulate the email, name, and gender parameters to inject arbitrary SQL into the application's database queries. The CVSS vector confirms PR:N/UI:N, meaning no credentials or user interaction are required, and publicly available exploit code exists; however, there is no evidence of confirmed active exploitation (not in CISA KEV), and realistic impact is bounded to Low confidentiality, integrity, and availability for a single application database. Because the project follows a rolling-release model, no affected or patched version numbers are published, and the maintainer has not responded to the upstream GitHub issue reporting the flaw.
SQL injection in itsourcecode Online Admission System 1.0 allows remote attackers to inject arbitrary SQL through the 'ID' parameter of /admin/creteria.php, potentially reading or modifying the underlying database. The vulnerable script is located under the /admin/ path, so although the published CVSS 4.0 vector indicates PR:N (no authentication), real-world exploitation most likely requires either an admin area deployed without access control or an existing administrative session. Publicly available exploit code exists and the flaw was disclosed publicly, but there is no CISA KEV entry and no observed evidence of active exploitation; assessed severity is medium (CVSS 4.0 base 5.5).
SQL injection in itsourcecode Online Admission System 1.0 lets remote attackers inject arbitrary SQL through the schedid request parameter handled by /admin/confirm.php, potentially reading or altering admission-related database records. The vendor's CVSS 4.0 vector (5.5, E:P) claims no authentication is required (PR:N), though the /admin/ path suggests an administrative session may in practice be needed; our independent assessment scores it CVSS 3.1 5.6-adjacent at PR:L with limited confidentiality and integrity impact. Publicly available exploit code exists (a GitHub issue demonstrating the flaw), but there is no indication of confirmed active exploitation and no CISA KEV listing; exposure is limited to internet-reachable deployments of this relatively obscure PHP application.
SQL injection in SourceCodester Drug Recommendation System 1.0 allows unauthenticated remote attackers to execute arbitrary SQL commands via the cmdschool parameter in /Auth/add_student.php. A public exploit has been released (publicly available exploit code exists; no evidence of active exploitation in CISA KEV) and the CVSS 4.0 base score is 6.9 (medium). The vulnerability is limited to low confidentiality, integrity, and availability impact, and real-world risk is low because the application is a niche academic/demo PHP project rarely exposed to the internet.
Read-only administrative users on Red Hat Quay can retrieve repository write (delegate) tokens through the build trigger API, then use those tokens to push arbitrary container images into private repositories despite their restricted role. Exploitation requires an account already holding global read-only administrative privileges (CVSS vector PR:H) plus repositories that have build triggers configured with embedded delegate tokens, so realistic risk is confined to malicious insiders or attackers who have already compromised a read-only admin credential. The flaw is rated moderate at CVSS 5.5 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:N), and no public exploit identified at time of analysis.
Privilege-model bypass in Rapid7 Velociraptor's Windows.Sysinternals.SysmonLogForward artifact allows an authenticated operator who holds only the COLLECT_CLIENT permission (typically the built-in 'Investigator' role) to launch an arbitrary, attacker-chosen binary on monitored Windows endpoints instead of the installed Sysmon binary. Because the artifact exposes a user-controllable binary-path parameter and fails to enforce the additional EXECVE permission that gates comparable dangerous artifacts, successful collection results in code execution on the endpoint under the elevated privileges the artifact normally runs with, yielding high confidentiality, integrity, and availability impact (assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). Exploitation is not anonymous: the attacker must already be a trusted Velociraptor operator with artifact-collection rights, and the chosen binary must be reachable or placeable on the target endpoint, which narrows realistic exposure to insiders or compromised operator accounts. No public exploit code or confirmed active exploitation was identified at time of analysis; the issue is a moderate, privilege-escalation class flaw rather than a mass-exploitation threat.
Local information disclosure in MediaTek Modem firmware affects devices built on more than 80 MediaTek chipset models, including MT6983, MT6895, MT6989, and MT6768, when running unpatched modem firmware. A local app with ordinary low privileges (PR:L) can access sensitive modem debug information without user interaction, yielding high confidentiality impact but no code execution or integrity/availability loss; CVSS is 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N). No public exploit code has been identified at time of analysis, and there is no CISA KEV entry indicating confirmed active exploitation, but MediaTek patch MOLY01645293 and the October 2026 product security bulletin address the flaw.
A local, low-privileged user can crash the sssd authentication daemon by submitting a crafted passkey (FIDO2/WebAuthn) authentication token that omits expected null terminators, causing an out-of-bounds read and terminating the service, which disrupts authentication for all users relying on that host. Rated CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), the flaw is purely an availability issue confined to systems where sssd's passkey authentication path is configured and reachable; there is no confidentiality or integrity impact and no remote or unauthenticated route. At the time of analysis, no public exploit code has been identified and there is no confirmed active exploitation (not listed in CISA KEV), and no vendor-released patch has been identified.
Crashing the SSSD autofs responder process via a crafted request to its UNIX socket allows a local, low-privileged attacker to cause a denial of service on affected Red Hat Enterprise Linux 6 through 10 and OpenShift Container Platform 4 systems. The vulnerability stems from improper buffer offset calculation during request parsing, leading to an out-of-bounds read (CWE-125) that terminates the responder process; it carries a CVSS 3.3 (Low) score with no confidentiality or integrity impact. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the autofs responder service must be enabled for the flaw to be exploitable.
An out-of-bounds read in Android's NFC Type 5 Tag reader/writer implementation (rw_t5t.cc) lets a local, low-privileged context read memory that should be out of reach, resulting in information disclosure with no user interaction required. The flaw carries a CVSS 3.1 base score of 5.5 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), and per that vector the attacker must already hold a low-privileged foothold on the device, such as an installed application capable of exercising the NFC read path; there is no write or code-execution impact. No public exploit code or confirmed active exploitation was identified at time of analysis, and remediated builds are addressed through the Android Security Bulletin dated 2026-10-01.
Persistent local denial of service in Android's DevicePolicyManagerService (Android 14, 15, 16, 16-QPR2 and 17) allows an on-device caller holding device-owner or profile-owner rights to feed malformed input into the setPermissionGrantState path and corrupt persisted permission/policy state. Because the resulting denial of service is persistent rather than transient, recovery typically requires administrative cleanup (clearing policy state, removing the managed profile/account, or in the worst case a factory reset) rather than a simple reboot. Scoring is AV:L/PR:L/UI:N with availability-only impact (CVSS 5.5), there is no remote vector, and no public exploit has been identified at time of analysis; CISA SSVC records Exploitation: none and Automatable: no, so this is a moderate local availability issue rather than an urgent, remotely exploitable flaw.
Authentication bypass in Casdoor up to 3.161.1 lets remote unauthenticated attackers access API endpoints that should require authentication, because the ApiFilter function in routers/authz_filter.go does not correctly enforce auth. Publicly available exploit code exists, and the reporter rates the issue CVSS 4.0 6.9 with PR:N; independent assessment agrees that exploitation requires only network reachability to the Casdoor API and that impact is Low for confidentiality, integrity, and availability, with no scope change. The vendor was contacted but did not respond, and no fixed version was identified at time of analysis.
Authenticated users of Plane before 1.4.0 can bypass API rate limits by arbitrarily increasing a token's allowed_rate_limit, enabling high-volume API requests that may consume backend resources. Exploitation requires a valid account with access to the API-tokens endpoints, and the issue is fixed in version 1.4.0. No public exploit identified at time of analysis; severity is moderate and impact is limited to integrity of the rate-limit setting and availability pressure.
Cross-site scripting in the OAuth callback handler of Red Hat Quay 3 lets an unauthenticated remote attacker run arbitrary JavaScript in a logged-in user's browser session by luring that user to a crafted URL, with no attacker privileges required (PR:N) but mandatory victim interaction (UI:R), giving a CVSS 3.1 score of 5.4. Successful exploitation is scoped to the victim's Quay application session (S:U, low confidentiality and integrity impact, no availability impact), potentially exposing registry metadata or allowing actions to be performed as the victim, rather than yielding server-side compromise. The vulnerability class is CWE-79 improper neutralization of input during web page generation; no public exploit code was identified in the available intelligence at the time of analysis, and CISA KEV status was not indicated.
Authenticated editors on a Penpot file (prior to version 2.18.0) can delete share links that were created by other users, because the delete-share-link RPC only checks that the caller can edit the parent file and never verifies ownership of the specific share link. By supplying the UUID of a colleague's or owner's share link - IDs that editors can enumerate from the file's view-only bundle - a mid-privileged collaborator can revoke external reviewers' access and disrupt published viewing/inspection links. Rated CVSS 5.4 (broken access control, PR:L), this requires an existing edit-rights account rather than anonymous access, and no public exploit code has been identified at time of analysis. Vendor-released patch: 2.18.0.
An authenticated Project Member (role 15) in Plane can escalate a Project Guest (role 5) to the Member role without Project Admin approval by sending a PATCH request to the project-member update endpoint at /api/workspaces/{workspace_slug}/projects/{project_id}/members/{member_pk}/. The role-update logic only rejected assignments where the new role exceeded the requester's own role, so submitting a role equal to the attacker's Member role slipped past the check and granted the guest Member-level project capabilities, bypassing project governance controls. This is a moderate-severity, authenticated privilege-escalation flaw (CWE-269) affecting Plane deployments prior to 1.4.0; no public exploit code was identified and the issue is not confirmed as actively exploited (CISA KEV).
Authenticated low-privilege users can read and modify support tickets they do not own in the JS Help Desk WordPress plugin (Ahmad) through version 4.0.0, due to an insecure direct object reference (CWE-639) that exposes user-controlled ticket identifiers. Rated CVSS 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N), exploitation requires a valid low-privilege account and is limited to confidentiality and integrity impact on support-ticket data, with no availability impact. No public exploit identified at time of analysis; no exploit code or KEV listing is referenced in the available intelligence.
Improper Unicode encoding in the pwhois command-line tool shipped with Net::Whois::Raw before 2.99044 for Perl causes WHOIS lookups for certain internationalized domain names to be sent for the wrong domain, disclosing the queried name to an unrelated registry and returning results for the incorrect domain; the Net::Whois::Raw library modules themselves are not affected. The flaw (CWE-176, CVSS 3.1 5.4, vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) is unauthenticated but requires user interaction - the victim must run pwhois against a unicode label that pwhois does not lowercase (i.e., contains uppercase letters other than ASCII/Cyrillic, or is not in NFC form) - and only the CLI path is impacted. EPSS is low at 0.18% (7th percentile), no public exploit code exists, there is no CISA KEV entry indicating active exploitation, and a vendor patch is available in release 2.99044.
Stored cross-site scripting in Penpot before 2.18.0 allows an authenticated user holding file-edit permission to upload SVG media whose <script> blocks, event-handler attributes, and <foreignObject> elements are persisted without sanitization and later served as image/svg+xml from the Penpot origin; any victim who directly navigates to the stored asset URL executes attacker-controlled JavaScript in that origin and can issue requests and read data with the victim's Penpot session authority. Exploitation requires both a privileged authenticated account (PR:L, effectively a trusted collaborator or a compromised one) and victim navigation to the asset URL (UI:R), which confines realistic exposure to multi-user or externally shared Penpot instances rather than single-user deployments. No public exploit code was identified at time of analysis and the issue is not listed in CISA KEV; the vendor-released fix is version 2.18.0.
Private AI workflow data in Langflow 1.0.0 through 1.10.0 can be read, enumerated, and partially executed by a caller who knows the target flow's UUID, because the deprecated POST /api/v1/build/{flow_id}/vertices and /vertices/{vertex_id} handlers never verified flow ownership. Through 1.7.1 these handlers were reachable without authentication, while in 1.7.2 through 1.10.0 the attacker must be authenticated but needs no elevated privileges, consistent with the assessed CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (score 5.4). Impact is deliberately bounded: a caller can disclose private flow structure, configured values, and selected vertices' outputs and can trigger victim-configured side effects and build-history records, but cannot read the victim's variable-store credentials or modify the stored flow. No public exploit code identified at time of analysis, and the issue is fixed in Langflow 1.10.1 / langflow-base 0.10.1.
Deactivated workspace owners retain owner-level administrative access in Plane project management instances prior to version 1.4.0. The WorkspaceOwnerPermission check queries workspace membership with role=Admin but omits the is_active=True filter, so a formerly-owner account that has been deactivated is still treated as an authorized owner; an attacker who holds valid credentials for such an account - an offboarding or insider-abuse scenario, not a broad unauthenticated compromise - can keep exercising administrative control. The impact is amplified because the authentication adapter (base.py save_user_data) automatically reactivated inactive accounts on login in affected versions, and the fix in 1.4.0 adds the missing is_active check and rejects deactivated logins. No public exploit code has been identified at time of analysis and this issue is not confirmed in CISA KEV; the vendor-released patch is version 1.4.0.
Missing authorization checks in the Starter Templates (astra-sites) WordPress plugin, affecting versions through 4.7.7, allow a remote attacker holding a low-privilege account on the target site - such as a subscriber where open registration is enabled - to trigger plugin functionality that should be restricted to higher-privileged roles, resulting in low-level integrity and availability impact with no confidentiality loss (CVSS 5.4). The flaw is a CWE-862 incorrectly configured access-control level, requiring no user interaction and no special complexity, but it cannot be reached by a fully unauthenticated visitor (CVSS vector PR:L). At the time of analysis there is no public exploit identified and no indication of confirmed active exploitation, so risk is driven primarily by the population of sites running the plugin with open or loosely controlled user registration.
Authentication bypass in the maestro gRPC broker shipped with Red Hat Multicluster Engine for Kubernetes lets a client that already holds a valid mTLS client certificate skip the broker's authentication check and then subscribe to other consumers' event streams or publish forged agent status messages. The consequence is unauthorized information disclosure and loss of data integrity inside the broker, with no availability impact and scope unchanged; the assessed CVSS 3.1 base score is 5.4 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N). There is no confirmed active exploitation (not listed in CISA KEV) and no public exploit code identified at time of analysis, and the valid-client-certificate prerequisite confines abuse to trusted-but-lower-privileged or already-compromised clients rather than anonymous remote attackers.
Stored cross-site scripting in the Bacularis backup management web interface (versions 1.0.0 through 6.5.1) lets an authenticated user with permission to create backup pools inject a script payload into the pool LabelFormat field, which then executes in the browser of any user - such as an administrator - who later views the affected pool configuration. Because exploitation requires a valid low-privileged account (CVSS PR:L) and the payload fires only when a higher-privileged victim opens the crafted view (UI:R), the realistic blast radius is limited and the flaw is rated moderate severity (CVSS 5.4, scope-changed). EPSS is very low at 0.14% (3rd percentile), no CISA KEV entry exists, and no public exploit code has been identified at time of analysis, though a researcher disclosure is referenced at hekk.one.
Boot-time arbitrary code execution is possible on AMD Versal Adaptive SoCs and related Alveo accelerator cards, but only when USB boot mode has been enabled through physical board modifications - a configuration AMD explicitly describes as non-default. A crafted boot image delivered over USB can trigger an out-of-bounds write (CWE-787) that overflows a buffer and overwrites an active function pointer, yielding high confidentiality, integrity, and availability impact confined to the boot process. Because exploitation requires both physical access to the device and a deliberately modified board, plus a non-trivial (high-complexity) overflow, realistic risk is limited to supply-chain, manufacturing, or evil-maid scenarios; no public exploit identified at time of analysis, and no confirmed in-the-wild activity, though the vendor bulletin AMD-SB-8028 documents the issue.
Authenticated members of any workspace on multi-tenant Plane instances running versions prior to 1.4.0 can exploit an IDOR (CWE-639) in the BulkDeleteIssuesEndpoint and SubIssuesEndpoint to delete cycle/module associations or re-parent issues belonging to foreign workspaces, because the permission decorator only verifies membership in the URL-named workspace/project and does not validate that the supplied issue IDs are within that scope. The CVSS 5.4 (Medium) reflects limited confidentiality and integrity impact (C:L/I:L/A:N) with no availability impact; exploitation requires valid credentials and knowledge of foreign issue IDs (typically UUIDs), and no public exploit code has been identified at time of analysis. The vendor released a patch in version 1.4.0, documented in a public GitHub Security Advisory.
Cross-workspace IDOR in Plane prior to 1.4.0 lets any authenticated workspace member create issue relations that link their own issues to issues owned by other workspaces on the same instance, exposing the targeted issue's metadata (titles, identifiers, activity/event data) through the resulting activity events. The flaw affects the issue-relation endpoint and the related cycle, module and sub-issue endpoints, all of which accepted caller-supplied issue UUIDs without confirming they belonged to the caller's workspace; exploitation requires a valid low-privilege account (PR:L) on a multi-workspace instance and knowledge or enumeration of a foreign issue UUID. No public exploit code was identified at time of analysis and no EPSS or KEV signal was provided, so this is best treated as a moderate, authorization-scoped information-disclosure and integrity issue rather than an urgent remote-code-execution class bug. Vendor-released patch: 1.4.0.
Host-based authentication controls in Perforce P4 Search prior to 2026.4.2 can be bypassed because the service trusts a client-supplied address when validating certain authentication requests, allowing a holder of a stolen P4 Server ticket to defeat ticket host-binding and trusted-address restrictions and obtain access to P4 Search as that ticket's owner. The flaw is authenticated in nature (CVSS:4.0 vector shows PR:L and the independent assessment concurs), so it does not grant access on its own - the attacker must already possess a valid but stolen ticket, and the bypass is only meaningful in deployments that rely on host-binding or trusted-address controls; where those controls are absent, the stolen ticket already grants the same access. Severity is moderate (CVSS 5.3, independent CVSS:3.1 base 5.3) with low confidentiality and integrity impact confined to the single compromised ticket's permissions; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV), so this is best treated as a medium-severity defense-in-depth gap rather than a standalone critical issue.
A divide-by-zero fault in vgmstream's Microsoft IMA ADPCM decoder (decode_ms_ima in src/coding/ima_decoder.c) allows an attacker to crash an application that uses the library by tricking a user into opening or playing a malformed IMA ADPCM-encoded audio file. All builds up to and including r2117 are affected, and the issue is reachable remotely only in the sense that the hostile file can be delivered over a network - the victim must still actively load it into a vgmstream-based player or tool, and the CVSS vector confirms the attack is unauthenticated but requires user interaction. Impact is limited to denial of service: the decoder process aborts with no code execution, data disclosure, or integrity loss, and there is no public exploit identified at time of analysis, so this is best treated as a moderate-severity availability bug rather than an emergency.