CVE-2026-32095
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPlunk is an open-source email platform built on top of AWS SES. Prior to 0.7.1, Plunk's image upload endpoint accepted SVG files, which browsers treat as active documents capable of executing embedded JavaScript, creating a stored XSS vulnerability. This vulnerability is fixed in 0.7.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePlunk's image upload endpoint (prior to v0.7.1) accepts SVG files without sanitization. SVG files are XML-based and can contain embedded JavaScript that executes when viewed in a browser, creating a stored XSS vulnerability where malicious scripts persist on the server and execute when users view uploaded images.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Plunk versionCheck the installed version of Plunk by reviewing package.json, running 'plunk --version', or checking the running service version bannerAffected if The installed version is below 0.7.1
-
Locate the image upload endpointIdentify the HTTP endpoint handling image/file uploads in the Plunk application (typically /upload, /api/upload, or similar path in the routes configuration)Affected if An image upload endpoint exists and is accessible without authentication restrictions
-
Test SVG upload capabilitySend a POST request to the upload endpoint with a file containing an SVG with embedded script tags (e.g., <script>alert(1)</script>) and verify the file is accepted and storedAffected if The endpoint accepts and stores SVG files without rejecting or sanitizing them
-
Verify stored SVG is served unsanitizedAccess the stored SVG file via its direct URL in a browser and confirm the embedded JavaScript executesAffected if The SVG file is served with its original content intact, allowing script execution
A user is affected if Plunk version is below 0.7.1 AND the image upload endpoint accepts and serves SVG files without sanitization, allowing stored XSS.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.7.1
Upgrade to Plunk v0.7.1 or later. If immediate upgrade is not possible, configure the upload endpoint to reject SVG MIME types or implement server-side SVG sanitization before serving uploaded files.
0.7.1 or later
- Backup your Plunk installation and database before proceeding with any updates
- Update Plunk to version 0.7.1 or later release
- Verify the upgrade completed successfully by checking the running version
- Confirm that the image upload endpoint now properly sanitizes or blocks SVG file uploads
- Test with a benign SVG file to verify proper handling
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32095 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32095 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data