NocoDB before 2026.10.1 contains a stored HTML injection vulnerability that allows authenticated users with record edit rights to inject forms, images, and styled overlays into rich text cells, which are sanitized only with DOMPurify's default policy. Attackers can place a page-sized spoofed sign-in form or remote image in a cell to harvest passwords and disclose viewer IP addresses in expanded records, gallery and kanban cards, and shared views.
Wiki.js is an open source wiki app built on Node.js. Prior to 2.5.315, an authenticated user with write:pages can store JavaScript expressions in the v-slot:tabs or v-slot:content attributes of page HTML because server/modules/rendering/html-security/renderer.js adds those executable Vue directives to DOMPurify's allowlist. The sanitized output is inserted as rendered page HTML and later compiled by the Vue 2 runtime compiler, so the expressions execute in the Wiki.js origin when another user views the page even when the author lacks write:scripts and administrative permissions. The script runs with the viewer's browser session and can read same-origin data, modify displayed content, present phishing content, or perform actions available to that viewer, including privileged GraphQL operations when a privileged user opens the page. This issue is fixed in version 2.5.315.
The popup shown when hovering an issue reference loaded its data from the path of the hovered link and inserted part of the response as HTML. A user who can post a comment or other rendered content could add a link that is displayed as an ordinary issue reference but points to a file in a repository they control, so that the popup inserted that file's content into the page of anyone hovering the link and ran script in the viewer's session. The popup now requests the issue by the owner, repository and index parsed from the link.
CVE-2026-126192 is a performance-related vulnerability in Soup Sieve where using a general sibling combinator (~) inside the :has() CSS selector causes quadratic time complexity when matching against untrusted HTML. This can lead to significant CPU consumption and potential denial of service if an attacker controls the HTML input and the selector is applied. The issue arises because the selector implementation performs nested scans over sibling elements, causing processing time to grow quadratically with the number of siblings. The vulnerability affects Soup Sieve versions starting from 1.3.0. Mitigations include careful use of :has() selectors, avoiding large numbers of children on the anchor element, and preferring more restrictive combinators like > or + inside :has().
Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. Prior to 2.25.3, Loofah's SVG_ALLOW_LOCAL_HREF safelist lists textPath with lowercase spelling that does not match the HTML5 parser's element name and omits mpath, so external href and xlink:href values on those elements survive sanitization. Firefox fetches the attacker-chosen URL when a viewer renders the content, which can disclose the viewer's IP address, user agent, referrer, and access to hosts routable only from the viewer's network. Chrome and WebKit do not fetch these references, and the impact is a network request rather than script execution. The rails-html-sanitizer PermitScrubber reuses the affected safelist when SVG elements are permitted. This issue is fixed in version 2.25.3.
Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. Prior to 2.25.3, Loofah::HTML5::Scrub.scrub_css checks only the first parse of a style attribute, then rebuilds CSS with identifier escapes decoded so escaped parentheses, property names, comments, or quotes can become a live url() without a second safety check. An attacker can use list-style to make a viewer's browser request an attacker-chosen URL when content renders, or cursor to make the request on hover. The request can disclose the viewer's IP address, user agent, access timing, and access to internal-network hosts, but no script survives sanitization and the attacker cannot read the response. This issue is fixed in version 2.25.3.
OHIF Viewers is a zero-footprint DICOM viewer with shared extension packages. From 3.5.0-beta.0 until 3.12.15, 3.13.7, and 3.14.0-beta.19, the dicom-pdf extension reads the attacker-controlled MIMETypeOfEncapsulatedDocument value in extensions/dicom-pdf/src/getSopClassHandlerModule.js and uses it as the Blob media type for the attacker-controlled EncapsulatedDocument bytes. When a victim opens Encapsulated PDF SOP Class 1.2.840.10008.5.1.4.1.1.104.1, extensions/dicom-pdf/src/viewports/OHIFCornerstonePdfViewport.tsx embeds the Blob URL in an object element. A Blob labeled as HTML is handled as HTML despite the application/pdf object hint, and the Blob inherits the OHIF origin, allowing embedded script to access session storage, authentication tokens, and same-origin PACS requests. The malicious DICOM object may be opened locally, uploaded to a shared PACS, or supplied by a DICOMweb source. This issue is fixed in source versions 3.12.15, 3.13.7, and 3.14.0-beta.19.
Otter Wiki versions before 2.26.2 have a stored cross-site scripting (XSS) vulnerability in the OtterwikiMdRenderer.block_code component. This flaw allows attackers with page editing permissions, including anonymous users under default settings, to inject arbitrary scripts by placing HTML inside math fenced code blocks. The injected scripts execute unescaped for every viewer of the affected page. The vulnerability has a CVSS 4.0 base score of 5.3 (medium severity) and was fixed in version 2.26.2.
CVE-2026-115355 is a vulnerability in the Mistune markdown parser's Include directive that allows path traversal and cross-site scripting (XSS). The directive does not properly validate file paths, enabling attackers to read arbitrary files via '../' sequences. Additionally, error messages and included file contents are rendered without HTML escaping, causing XSS even when escaping is enabled. This vulnerability affects versions >=1.3.0 and <1.4.0_6 of the adr-viewer product. A fix is available in version 1.4.0_6.
CVE-2026-55486 is a critical cross-site scripting (XSS) vulnerability in the intranda goobi-viewer-core web application. It affects versions from 25.08 up to but not including 26.05. The vulnerability arises because the IIIF Auth 2.0 endpoints auth/login and auth/token accept an origin query parameter without proper validation, which is then embedded unsafely into the Content-Security-Policy header and HTML response body, enabling reflected XSS attacks. The issue has been fixed in version 26.05.
The Quick PayPal Payments: Payment Button & Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'form' parameter in all versions up to, and including, 6.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because wp_kses_post strips only HTML tags, a quote-breaking payload containing no angle brackets survives post save intact, and the injected script fires for every viewer of the post — including higher-privileged Editors and Administrators who routinely preview a Contributor's pending content.
xhtml2pdf versions before 0.2.19 contain an OS command injection vulnerability in the pisa.startViewer() function. This flaw allows attackers to execute arbitrary OS commands by supplying input files with specially crafted names containing double quotes and shell metacharacters. The vulnerability is triggered when the pisa tool is used with the -s or --start-viewer option, causing the unescaped file name to be passed to os.system. The vulnerability has a high severity rating with a CVSS score of 7.8.
CVE-2026-104250 is a stored cross-site scripting (XSS) vulnerability in the unstructured library prior to version 0.24.1. When unstructured parses untrusted HTML documents and outputs them as HTML, it fails to escape malicious markup such as event handlers (e.g., onerror, onmouseover) and javascript: URLs. This allows embedded scripts to execute automatically in a viewer's browser when the output is rendered. The vulnerability affects the to_html() function and related HTML output paths. Exploitation can occur without user interaction, leading to information disclosure and potential privileged actions in ingestion pipelines where untrusted documents are reviewed in a web UI.
In Progress® Telerik® Report Server prior to version 12.2.26.1007, a stored cross-site scripting vulnerability in the shared reporting engine allows an authenticated report author to embed javascript: or vbscript: URLs in report navigation actions or HTML text box links. When another user views the malicious report and the embedded navigation is triggered, attacker-controlled script can execute in the web report viewer's origin. In a multi-user Report Server deployment, this can enable privilege escalation by performing actions in a higher-privilege user's authenticated session, including an administrator's session.