Code injection in Alfresco Activiti through 7.21.0-rc.692 lets an authenticated low-privileged user who can route input into JuelScriptEngine.eval execute attacker-supplied JUEL expressions, potentially leading to remote code execution on the server. The vendor was contacted but did not respond, and no public exploit or fixed release has been identified at time of analysis. The supplied CVSS 4.0 base score is 5.3 (medium), while the independent assessment's CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects the higher potential impact if the reachable evaluator permits arbitrary Java invocation; the trigger feature or field that feeds eval is not described in the available sources.
Stored cross-site scripting in YesWiki 4.2.0 through 4.6.7 lets any authenticated user who can post a comment embed raw HTML and JavaScript using the wiki's "".."" raw-HTML syntax, which is saved with only whitespace trimming and later rendered through a Twig raw filter, so the payload executes in the wiki origin for every visitor of that page, including administrators. Shipped defaults (allow_raw_html = true, comments_activated = true) keep the path open, but exploitation additionally requires that comments be enabled on at least one page, because the global default_comment_acl is comments-closed; the vendor confirms the flaw is fixed in 4.7.0, and the GitHub security advisory includes proof-of-concept request steps, while no CISA KEV listing or other evidence of active exploitation was supplied. Scored 5.3 on CVSS 4.0 (PR:L, scope changed, low confidentiality and integrity impact), the realistic outcome is script execution in a higher-privileged viewer's session, plausibly enabling session theft and follow-on wiki actions rather than server compromise.
Server-side request forgery in phpMyFAQ's PDF export feature lets an attacker who can plant an image URL inside FAQ answer content make the server fetch a destination of their choosing - for example a loopback or internal HTTP service - and embed the response in the generated PDF. All releases before 4.1.10 are affected, and the vendor has released 4.1.10 as the fix. The reported chain requires two preconditions: permission to create or modify the FAQ containing the malicious <img> reference, and the target host being permitted by records.allowedMediaHosts (the reporter explicitly added 'localhost' to that allowlist, a non-default setting); the reporter could not demonstrate the full chain against a completely unauthenticated attacker or against default configurations, and confirmed only that retrieval and embedding occur, not that arbitrary internal data can be extracted. No CISA KEV entry or EPSS score was supplied, and the advisory ships a local reproduction script rather than verified working exploit code; the priority signal is a routine monthly patch cadence.
Cross-site request forgery in LinkStack (linkstackorg:linkstack) affects all versions up to and including 4.8.8 and lets a remote, unauthenticated attacker cause a logged-in user's browser to submit state-changing requests against the instance. Exploitation depends on an authenticated victim with an active session being tricked into interacting with attacker-controlled content, so a successful attack yields only a low integrity impact on LinkStack itself, with no confidentiality or availability effect. No vendor patch or advisory has been issued - the maintainers were contacted about the disclosure and did not respond - and no public exploit code or proof-of-concept has been identified at time of analysis; the reported CVSS 4.0 score of 5.3 and the this_month priority label place this as a moderate, non-urgent item to schedule rather than an emergency.
Stored cross-site scripting in WWBN AVideo 26.0 through 29.3.0 allows any user who holds comment permission on a viewable video to persist JavaScript that executes in other viewers' browsers under the application origin. The payload must begin an HTML block with an image tag carrying an event handler, because the custom Parsedown subclass sanitizes inline image/link markup but hands leading block-level `<img>`/`<a>` tags to the raw HTML handler. Exploitation requires an authenticated commenter, comment visibility, and a victim viewing the comment (UI:P); impact is bounded to low confidentiality/integrity per the assessed vector, and a CSP that blocks inline event handlers neutralizes the demonstrated payload. No public exploit code or confirmed active exploitation was identified, and no verified patched release exists as of the advisory date.
Stored cross-site scripting in YesWiki before 4.7.0 lets any authenticated low-privilege user upload an unsanitized SVG through the bazar ImageField, which the server stores byte-identical and serves as image/svg+xml, so script executes in the browser of anyone who opens the entry or navigates to the stored file. The vulnerable sink is a sibling of the one fixed in 4.6.7 for GHSA-67v5-7pfv-pp9m (CVE-2026-104461): the cleanFile() denylist was added only to FileField, leaving ImageField with an isImage() gate that passes svg because it sits in the default attach_config.ext_images list, so stock configurations are exposed. A vendor fix is available in 4.7.0, and the GitHub advisory documents a public proof-of-concept with recorded live reproduction on v4.6.7; it is not verified here as working exploit code, and there is no CISA KEV signal of active exploitation.
Stored cross-site scripting in SiYuan Note 2.10.0 through 3.8.6 lets a user who already holds edit permission on a document plant a `javascript:` URL inside math-block content, for example `$$\href{javascript:alert('xss')}{clickme}$$`, so that script runs in the application origin when a reader clicks the rendered link. The rendering path passes math TeX to KaTeX with `trust: true` and mounts the resulting HTML through `innerHTML`, so `\href`, `\url` and `\includegraphics` payloads (including mixed-case `JaVaScRiPt:` schemes) survive unsanitized. Exploitation is not unauthenticated and is not automatic: the attacker needs writer access to a shared document and the victim must open it and click, which caps practical severity at CVSS 5.1; the vendor advisory GHSA-hhvq-jqv9-pgjq includes a detailed proof-of-concept reproduction against a real Chromium instance, though no CISA KEV listing or public weaponized exploit is reported, and the priority label is this_month.
Path traversal in the EventCatalog (@eventcatalog/sdk) custom-documentation helpers, fixed in 2.30.0, lets a caller that already has local access to the SDK escape the catalog docs directory when reading, writing, or deleting custom docs. The vulnerable functions getCustomDoc, getCustomDocs, writeCustomDoc and rmCustomDoc joined attacker-supplied path values directly onto the docs directory, so '../' sequences, absolute or leading-slash paths, Windows drive-letter or UNC paths, null bytes, or symlinks could redirect file operations outside the catalog. Exploitation is limited to local-host callers who can already invoke the SDK - typically local build or documentation tooling rather than a network service - with low confidentiality, integrity and availability impact; no public exploit code was identified at time of analysis and the issue is rated moderate with low urgency.
Stack exhaustion in ImageMagick's MVG decoder can crash the process, causing a denial of service limited to availability; no code execution, data disclosure, or integrity impact is assessed. ImageMagick 6.x before 6.9.13-58 and 7.x before 7.1.2-33 are affected, and a crafted MVG file must be processed through certain decoder paths with specific arguments, requiring local access and user interaction or an automated pipeline. Vendor patches are available in 6.9.13-58 and 7.1.2-33, and no public exploit has been identified at time of analysis.
ImageMagick's PS, PDF and XPS decoders allow a security-policy limit on scene selection to be bypassed by supplying a specific argument, so a crafted input can make the tool process more scenes than the configured policy permits and consume resources. Only installations that define such a list-length limit in their security policy have a limit to circumvent; the CVSS 4.0 vector (AV:L/AC:L/PR:L/UI:N) scores it 4.8 and confines impact to low availability, with no confidentiality or integrity effect. Fixes are released in 6.9.13-58 and 7.1.2-33, no public exploit code or PoC reference is identified in the supplied sources, and the issue is not flagged as actively exploited (no CISA KEV entry); priority is 'this_month' rather than emergency.
ImageMagick 6.x before 6.9.13-58 and 7.x before 7.1.2-33 can be driven into memory exhaustion when the -cdl (color decision list) option processes attacker-influenced input, because allocated memory is not released along that code path. The issue is a CWE-401 memory leak scored 4.8, with local reachability and passive user interaction in the assessed CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R, availability-only Low), and exploitation depends on the -cdl option being reachable in the deployment. No public exploit was identified at time of analysis; vendor fixes are available in 7.1.2-33 and 6.9.13-58.
PerlMagick, the Perl binding shipped with ImageMagick, leaks memory in five property-reading code locations before release 7.1.2-33, so an attacker who can repeatedly drive property reads through that binding can exhaust process memory and cause a denial of service. Exposure is confined to applications or scripts that actually use PerlMagick and read image properties - the core C library and other language bindings are not affected through this path, and a single read leaks only a trivial amount, so the reads must recur. The vendor has released a fix in 7.1.2-33; no public exploit code was identified at time of analysis and the issue is not in CISA KEV, which fits its genuinely low priority despite the moderate 4.8 CVSS 4.0 score.
A missing memory release in ImageMagick's `-set profile` handling causes each invocation that touches that code path to leak memory, which can degrade or exhaust resources on hosts that repeatedly process attacker-influenced images. The flaw affects 6.x builds before 6.9.13-58 and 7.x builds before 7.1.2-33; exploitation requires a user or automated job to be induced to process a crafted image with the `-set profile` option, giving a local vector with passive user interaction and no privileges required. Impact is confined to availability - a single run leaks rather than crashes, so a meaningful denial of service needs repeated processing - and no public exploit was identified at time of analysis.
Heap buffer overflow in ImageMagick's X11 animate path (versions before 6.9.13-58 and 7.x before 7.1.2-33) allows an attacker-supplied crafted image to overwrite heap memory and crash the application when a user runs an X11 animate operation with an X11 display available. Exploitation requires local user interaction and the available assessment limits impact to availability; no public exploit was identified at time of analysis. Vendor patches are available in 6.9.13-58 and 7.1.2-33.
MVG encoder injection in ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 lets an attacker who can supply drawing options write arbitrary MVG drawing commands into generated MVG output. The flaw is medium severity (CVSS 4.0 base 4.8; assessed CVSS 3.1 vector AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), requires a local attack path and a downstream step that processes the resulting MVG file, and affects applications that pass untrusted drawing options to ImageMagick. No public exploit identified at time of analysis; vendor fixes are available in 6.9.13-58 and 7.1.2-33.
Heap buffer over-read in ImageMagick before 7.1.2-33 can disclose adjacent heap memory or crash the process when a crafted image is processed through the minimum-bounding-box printing path. The issue is local, requires no privileges, and depends on a victim or automated service feeding attacker-controlled image data into that specific operation, with impact limited to read-only disclosure and availability loss. No public exploit was identified at time of analysis, and the vendor has released 7.1.2-33 as the fixed version; the priority signal is this_month.
ImageMagick 6.x before 6.9.13-58 and 7.x before 7.1.2-33 can run an executable that policy.xml is intended to block, because delegate invocations are parsed incorrectly. The bypass matters only where an administrator has configured policy.xml to deny a delegate or executable and where crafted input reaches delegate processing; the assessed vector is local (AV:L) with user interaction (UI:R) and integrity-only impact, and no public exploit was identified at time of analysis. Vendor patches are available in 6.9.13-58 and 7.1.2-33.