Path traversal in IBM MQ Web Console allows an authenticated administrator to write files outside the intended directory in deployments using IBM MQ Operator or IBM MQ Advanced Container Images. The issue is low severity (CVSS 2.7) with integrity-only impact and a high privilege prerequisite, and no public exploit identified at time of analysis; a vendor patch is available per IBM advisory.
Cookie host-only protection can be silently stripped from aiohttp's client CookieJar when a client that shares one jar across a parent domain and its subdomains is lured into requesting an attacker-controlled subdomain that returns a same-named cookie carrying an explicit Domain attribute. Only aiohttp releases prior to 3.14.4 are affected, and per the vendor the practical impact is narrow: an attacker gains little unless the application reflects the affected cookies back into a browser context. The issue is low severity (CVSS 2.3, independently assessed as CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N), is not listed in CISA KEV, and no public exploit code was identified at time of analysis; the vendor-released patch is version 3.14.4.
Parse Server fails to enforce class-level create and addField permissions on its built-in _Session class, allowing an authenticated user-or anyone holding that user's valid session token-to create additional persistent sessions and add fields to _Session through POST requests to /sessions or /classes/_Session. Affected releases are Parse Server before 8.6.98 and 9.0.0 before 9.10.3-alpha.1; sessions created this way are not revoked when the original session is logged out. Impact is limited to session integrity with no confidentiality or availability loss, and no public exploit code was identified at time of analysis.
FOSSBilling 0.8.4 through 0.8.5 has an authorization gap where hasManagePermission returns early for inactive non-core modules, letting a low-privileged staff account that holds only module-level extension access read decrypted retained extension secrets via api/admin/extension/config_get and overwrite stored extension configuration via config_save without holding the extension.manage_extensions permission. Exploitation is authenticated (PR:L) and limited to deactivated non-core modules, with low confidentiality and integrity impact and no availability impact, which is why the vendor-assigned and independently assessed severity are both low. There is no public exploit code and no confirmed active exploitation (no public exploit identified at time of analysis); the flaw is resolved in 0.8.6 and is a residual path left over from the earlier CVE-2026-62962 authorization fix.
DOM-based cross-site scripting in the ic-tree-item component of the Intelligence Community UI Kit's @ukic/canary-web-components (pre-release versions 3.0.0-canary.12 through 3.0.0-canary.47) lets unauthenticated remote attackers execute JavaScript in a victim's browser when tree item truncation is enabled and the attacker can influence a tree item's router-item slot label. The flaw is narrow: it only triggers on the non-default truncation code path, requires a victim to render the affected tree, and is limited to low-integrity/low-confidentiality impact within the victim's browser, which is why it carries a low CVSS 4.0 score of 2.3. No public exploit code and no CISA KEV entry were identified at time of analysis; only canary builds are affected, with the fix landing in 3.0.0-canary.48.
Server-side request forgery in smrealms smr's Album Website feature lets a low-privileged authenticated user supply an arbitrary URL in the album 'Website' field, which is passed unvalidated to isUrlReachable() and fetched server-side via curl. The request is headers-only (CURLOPT_NOBODY) with a five-second timeout and the response body is never returned, so this is a blind SSRF that only reveals reachability and HTTP status class, limiting confidentiality impact. Exploitation requires an authenticated account (PR:L per the CVSS vector); publicly available exploit code exists, CVSS 4.0 base score is 5.3 (Medium), and the vendor has released a fix commit but the rolling-release model means no versioned patch is published.
Reflected cross-site scripting in the 'msg' parameter of feedback.php in subhajitkhan's online-clinic-management-system allows remote attackers to inject script into a victim's browser session. The product uses rolling releases, so no specific affected or fixed version is available; exploitation requires a victim to click a crafted link (UI:R) and is limited to integrity impact (no confidentiality or availability impact). Publicly available exploit code exists, but there is no indication of active exploitation (not in CISA KEV), and the issue remains low priority due to required user interaction and niche deployment.
Server-side request forgery in ANX Calibre Manager up to 1.13.12 allows an authenticated low-privileged user to supply a malicious base_url to the LLM Configuration Handler, causing LLMClient.chat to make outbound requests to attacker-chosen destinations. The issue is reachable only when the LLM integration feature is enabled and the attacker can access and submit configuration to that endpoint, with impact limited to low confidentiality disclosure. Publicly available exploit code exists, but there is no CISA KEV confirmation of active exploitation.
Server-side request forgery in TiBillet Lespass v1 API allows an authenticated attacker with high privileges to make the server fetch arbitrary URLs supplied through the img_url or image_url argument in the get_img_from_url function, potentially reaching internal services. The vendor confirms the weakness affects versions up to commit 10e87909c5d526dffa6d424c104fc12860740537 and states that destination IP validation, redirect re-checks, and download timeout/size limits are planned for the v2 API. Exploitation is rated difficult (AC:H) and no public exploit was identified at time of analysis; this is a low-priority, vendor-confirmed issue.
Server-side request forgery filter bypass in Krayin CRM 2.2.5 through 2.2.6 allows authenticated users with webhook permissions to make blind requests to internal services and cloud metadata endpoints via DNS rebinding. The flaw requires winning a time-of-check/time-of-use race: the webhook URL validator resolves a public address, while Guzzle later re-resolves the same hostname to an internal address. No public exploit has been identified at time of analysis, and the assessed severity is low (CVSS 2.1) because exploitation is gated by high privileges and high complexity.
Server-side request forgery in Client St0r through 3.17.586 lets any logged-in user - including read-only accounts - force the server to fetch arbitrary internal URLs through the Property URL Importer endpoint (POST /locations/<id>/import-property-from-url/). Because the pre-patch code only checked for an http:// or https:// prefix and used a plain requests.get() that followed redirects and honoured proxy environment variables, attackers could reach 127.0.0.1, RFC1918 hosts, and the 169.254.169.254 metadata endpoint, with failure exception text echoed back to the requester. Exploit code is publicly available, but no confirmed active exploitation (CISA KEV) is reported; upgrading to 3.17.587 resolves the issue.
Local image file disclosure in NoteGen through 0.38.3 allows authenticated attackers with write access to the victim's configured sync target to plant absolute paths or file:// URLs in synced conversation data, causing the chat image analysis (image_inspect) flow to read local images and send them to the configured AI provider. Exploitation requires the crafted sourceUrl to survive sync merging and the victim to use the image-analysis feature, and impact is limited to confidentiality of local image files. The issue is rated low severity (CVSS 4.0 score 2.1; independently assessed CVSS 3.1 vector with low confidentiality impact), and no public exploit was identified at time of analysis.
SQL injection in iWebShop-5 up to 5.16 via the Util::search function in classes/util.php allows a high-privileged authenticated remote attacker to manipulate database queries, with limited confidentiality, integrity, and availability impact. Publicly available exploit code exists, but active exploitation is not confirmed (no KEV listing provided). The vendor has not responded to the issue report, and the required administrative session significantly limits practical risk.
Signature-algorithm confusion in the russh Rust SSH server library (every release from 0.34.0-beta.1 through 0.63.3, plus main) allows a client to announce one publickey algorithm (e.g. rsa-sha2-512) while presenting a signature made with a different one (e.g. ssh-rsa/SHA-1) and still be authenticated, because the requested algorithm name is never compared against the signature's own algorithm. The practical impact is limited: the attacker must already hold an RSA private key that the server accepts, so authentication strength is not weakened - only servers that rely on the announced algorithm to block SHA-1 signatures (as OpenSSH does by default since 8.8) or to record/audit which algorithm a user authenticated with are meaningfully affected, giving low integrity impact. No CISA KEV listing, no EPSS score and no CVSS vector were supplied, so there is no evidence of active exploitation; the upstream advisory does include a proof-of-concept unit test that reproduces the acceptance of a SHA-1 signature, and the vendor has released a fix in 0.64.0.