The Check & Log Email – Easy Email Testing & Mail logging plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.0.17 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires an administrator to open the relevant log entry and click the planted anchor link in the Preview panel, at which point the ThickBox gadget parses the title attribute as live HTML in the wp-admin origin. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.
EGroupware is a web-based groupware server written in PHP. Prior to 23.1.20260601 and 26.5.20260507, the processURL2InlineImages logic in api/src/Mail.php treats non-HTTP image sources in an HTML mail body as local paths and passes a decoded attacker-controlled file:// URI to file_get_contents. Any authenticated user with mail access can cause files readable by the web server process to be embedded as inline MIME attachments in outgoing email, exposing local configuration, credentials, private keys, or other server files. This issue is fixed in versions 23.1.20260601 and 26.5.20260507.
NodePress through 8.5.1 contains an HTML injection vulnerability in linesToEmailContent() that allows unauthenticated attackers to inject markup into notification emails because comment content is not escaped. Attackers can post comments or replies via POST /comments containing forged links, images, or tracking resources rendered in administrator and author mail clients from the blog's address.
Multiple denial of service and cross-site scripting vulnerabilities were identified in the Go language components used by the skopeo command in Red Hat Enterprise Linux 9. These include issues in net/mail, encoding/asn1, net/url, net/http, html/template, and crypto/tls packages. The vulnerabilities allow denial of service via pathological input parsing, excessive recursion, quadratic complexity, unencrypted HTTP/2 connections, indefinite KeyUpdate messages, and cross-site scripting via pathological input. Red Hat has released an important security update for skopeo to address these issues.
The Mime Mail module for Drupal allows sending HTML email messages. Under rare configurations, a user able to send HTML emails could expose non-public files uploaded to the site by including them in emails. Exploitation requires the attacker to have prior knowledge of the uploaded files and the ability to send HTML emails to chosen recipients. A fix is available in version 2.0.4.
CVE-2026-120332 is a cross-site scripting (XSS) vulnerability in the TYPO3 Extension "Mail". It allows backend users with access to the mail module to inject arbitrary HTML and JavaScript into the mail preview or report views. This injected code executes in the context of other backend users, potentially leading to unauthorized actions or data exposure. The vulnerability affects versions 4.0.0 up to but not including 4.2.0 and versions prior to 3.12.5. A fix is available in versions 4.2.0 and 3.12.5. The CVSS 4.0 score is 5.1, indicating a medium severity level.
baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a stored cross-site scripting (XSS) vulnerability. This occurs because global shortcode expansion processes the entire rendered page, including HTML-escaped blog comments from unauthenticated users. An attacker can inject a malicious script URL via the BcBaser.getGoogleMaps shortcode in a comment, which executes when an administrator or visitor views the affected article. Other shortcodes like Mail.getForm can embed active forms with valid CSRF tokens. The vulnerability is patched in versions 5.3.2 and 5.4.2.
EspoCRM versions prior to 9.3.9 contain a cross-site scripting (XSS) vulnerability. An unauthenticated remote attacker can send an email with arbitrary HTML in the plain-text body to a monitored group or IMAP address, including email-to-Case addresses. EspoCRM stores and renders this HTML without proper escaping in Email Received stream notification emails sent to users, enabling HTML injection and potential JavaScript execution in mail clients that process these emails. This vulnerability is fixed in version 9.3.9.
The MemberHero WordPress plugin through 6.9 does not perform any capability or nonce check on one of its AJAX actions, allowing any authenticated user, such as a subscriber, to make the site send arbitrary HTML emails to arbitrary recipients from its own mail system, which can be abused to relay phishing carrying the site's identity and domain reputation.
Cross-site scripting in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote attacker who can send a user an encrypted message to run script in the webmail's origin with that user's session. When the webmail decrypted an S/MIME message (from 6.3.2) or an OpenPGP message (from 6.3.4) in the browser, it offered each decrypted attachment as a blob URL of the media type the message declared for it. A click saved the file, but if the user opened the attachment in a new tab, a part declared as text/html was rendered as a document of the webmail's origin and its script could read the mailbox, send mail and change the account through the REST API. The webmail is served only when the REST API is enabled, which it is not by default.
The WP Mail Logging WordPress plugin before 1.17.0 does not properly restrict the HTML and CSS of logged emails before rendering them in its admin log screens, allowing unauthenticated users to inject styled content and links, for example through a public contact form, that can deceive an administrator viewing the log and send their browser to an attacker-controlled page.
CVE-2026-90918 is a cross-site scripting (XSS) vulnerability in Joomla! CMS affecting versions 4.0.0 through 5.4.8 and 6.0.0 through 6.1.3. The issue arises from the mail template feature lacking proper escaping mechanisms, allowing injection of malicious scripts in HTML mail templates. This vulnerability has a medium severity rating with a CVSS score of 6.9.
Horilla is an HR and CRM software. From 1.0.0 until 1.6.0 and 2.0.0, the get_mail_preview handlers in recruitment/views/actions.py and employee/not_in_out_dashboard.py render a user-controlled body at /recruitment/get-mail-preview/ and /employee/get-employee-mail-preview with the full request object in the Django template context. An authenticated user with a valid CSRF token can use template attribute traversal to read request.user.password, request.META, and related-user attributes, exposing password hashes, personal data, and server request metadata. Django template restrictions prevent arbitrary code execution through this primitive, so the demonstrated impact is information disclosure and possible offline password cracking or account compromise. This issue is fixed in versions 1.6.0 and 2.0.0.
In the Linux kernel, the following vulnerability has been resolved: powerpc/irq: Fix missing r2 clobber in PCREL inline assembly In CONFIG_PPC_KERNEL_PCREL mode, r2 is no longer reserved for the TOC pointer and is available as a caller-saved register [0]. Both call_do_irq() and call_do_softirq() use inline assembly to call functions with stack switching, but fail to list r2 in their clobber lists. This causes the compiler to assume r2 is preserved across these calls, leading to register corruption when the called functions (__do_irq and __do_softirq) clobber r2. As a result of this kernel crash during interrupt handling is seen and the kernel fails to boot: BUG: Unable to handle kernel data access on write at 0xc000000404697638 Faulting instruction address: 0xc0000000000181ec Oops: Kernel access of bad area, sig: 11 [#1] NIP [c0000000000181ec] __do_IRQ+0x6c/0xc0 With older GCC, the compiler would conservatively allocate callee-saved registers (like r31) for values spanning function calls, accidentally avoiding the bug: <__do_IRQ>: 00 00 00 60 nop a6 02 08 7c mflr r0 f8 ff e1 fb std r31,-8(r1) f0 ff c1 fb std r30,-16(r1) 2d 03 10 06 pla r31,53297316 ... 3d e8 ff 4b bl c0000000000165ac <__do_irq> 00 00 21 e8 ld r1,0(r1) 28 00 4d e9 ld r10,40(r13) 40 00 21 38 addi r1,r1,64 2a f9 aa 7f stdx r29,r10,r31 With newer GCC 14, the compiler uses r2 for such values, exposing the missing clobber specification: <__do_IRQ>: 00 00 00 60 nop a6 02 08 7c mflr r0 f0 ff c1 fb std r30,-16(r1) f8 ff e1 fb std r31,-8(r1) 29 02 10 06 pla r2,36252592 # c0000000022aadc0 <__irq_regs> ... 85 dc ff 4b bl c000000000015ee0 <__do_irq> 00 00 21 e8 ld r1,0(r1) 28 00 2d e9 ld r9,40(r13) 30 00 21 38 addi r1,r1,48 2a 11 c9 7f stdx r30,r9,r2 Fix this by adding r2 to the clobber list for both call_do_irq() and call_do_softirq() when CONFIG_PPC_KERNEL_PCREL is enabled. [0]: https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg313226.html
Red Hat OpenShift Container Platform 4.19.48 includes multiple security fixes addressing denial of service, privilege escalation, and cross-site scripting vulnerabilities in various Go language packages. These issues affect components such as net, encoding/asn1, net/mail, golang.org/x/net/idna, mime, html/template, encoding/xml, net/url, and crypto/tls. Users of OpenShift Container Platform 4.19 are advised to upgrade to the updated packages and images to mitigate these vulnerabilities.
File Viewer is a browser-native viewer for Office, PDF, CAD, archive, and other files in private and internal web applications. Prior to @file-viewer/doc 2.3.1 and msdoc-viewer 0.2.2, the legacy DOC renderer emitted document-controlled hyperlink targets into generated HTML after character escaping but without restricting URL schemes. A crafted legacy DOC file could place javascript:, vbscript:, data:, or another unsafe scheme in a rendered link, and script could execute in the embedding application's origin when a user clicked the link. The fix blocks external document links by default, allows only HTTP(S), mail, telephone, safe relative URLs, and internal bookmarks when external links are explicitly enabled, and applies mount-boundary sanitization as defense in depth. This issue is fixed in @file-viewer/doc 2.3.1 and msdoc-viewer 0.2.2.
The Easy Appointments WordPress plugin before 4.0.2.2 does not use an unguessable token to authorize its mail-link appointment cancellation and confirmation action, deriving the token from a hardcoded source-embedded salt and the appointment's creation timestamp, so unauthenticated attackers who know or guess that timestamp can cancel or confirm arbitrary appointments.