VulnerabilityPublished 11 Mar 2026Updated 12 Mar 2026

CVE-2026-32095: useplunk plunk · Cross-site Scripting

Affects useplunk plunkSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 0.7.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.7.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade plunk and useplunk/plunk to 0.7.1.

Affected software

Product	Affected	Fixed in
useplunkplunk	Affected <0.7.1	Fixed in 0.7.1
GitHubuseplunk/plunk`pkg:github/useplunk/plunk`Other threats	Affected <0.7.1	Fixed in 0.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should upgrade Plunk to version 0.7.1 or later, where the SVG upload handling is fixed. If immediate upgrade is not feasible, implement strict input validation and sanitization on the image upload endpoint to reject or properly sanitize SVG files, removing any embedded scripts or active content. Employ Content Security Policy (CSP) headers to restrict script execution from untrusted sources and reduce the impact of potential XSS attacks. Additionally, enforce least privilege principles to limit who can upload files and monitor upload activity for suspicious behavior. Regularly audit and scan web applications for XSS vulnerabilities using automated tools and manual testing. Educate users about the risks of interacting with unexpected or suspicious content within the platform. Finally, maintain up-to-date backups and incident response plans to quickly address any exploitation attempts.

Description

CVE-2026-32095 is a stored cross-site scripting (XSS) vulnerability in the open-source email platform Plunk, versions prior to 0.7.1. The issue arises because Plunk's image upload endpoint accepted SVG files, which can contain embedded JavaScript and be treated as active documents by browsers. This improper input neutralization allows attackers to inject malicious scripts that execute in the context of users' browsers, potentially compromising confidentiality and integrity. Exploitation requires low privileges and some user interaction, but no known active exploits have been reported. The vulnerability has a CVSS score of 5.4, indicating medium severity. Organizations using affected versions should upgrade to 0.7.

Impact

The primary impact of this vulnerability is the potential compromise of user confidentiality and integrity within affected Plunk deployments. Successful exploitation can lead to session hijacking, unauthorized actions performed on behalf of users, and the injection of malicious content that could mislead or harm users. While availability is not affected, the breach of trust and data confidentiality can have significant consequences, especially in email platforms where sensitive communications occur. Organizations relying on Plunk versions prior to 0.7.1 may face reputational damage, regulatory compliance issues, and increased risk of further attacks leveraging stolen credentials or session tokens. The requirement for some user interaction (viewing the malicious SVG) and privileges to upload files somewhat limits the attack scope but does not eliminate risk, particularly in environments with many users or less stringent access controls.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/useplunk/plunk/security/advisories/GHSA-69jg-7493-cx5x (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:19 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats