Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-55876 Overview
CVE-2026-55876 is a stored cross-site scripting (XSS) vulnerability [CWE-79] in Helium, a free online student planner for classes, homework, grades, and notes. The flaw resides in the POST /planner/attachments/ endpoint, which allowed authenticated users to upload SVG and HTML files. The configuration file conf/configs/common.py omitted these formats from BLOCKED_ATTACHMENT_EXTENSIONS and BLOCKED_ATTACHMENT_MIME_TYPES, and helium/planner/serializers/attachmentserializer.py relied on those blocklists for validation. Helium 2.2.60 fixes the issue.
Critical Impact
An uploaded SVG served as image/svg+xml executes embedded script when a visitor opens its public attachment URL, enabling persistent attacker-controlled content and phishing under an application-managed storage URL.
Affected Products
- Helium Platform (HeliumEdu/platform) versions prior to 2.2.60
- Deployments exposing the /planner/attachments/ endpoint to authenticated users
- Instances serving uploaded attachments with original MIME types
Discovery Timeline
- 2026-10-15 - CVE-2026-55876 published to the National Vulnerability Database (NVD)
- 2026-10-21 - Last updated in the NVD database
Technical Details for CVE-2026-55876
Vulnerability Analysis
The vulnerability stems from an incomplete blocklist governing attachment uploads. The attachment serializer helium/planner/serializers/attachmentserializer.py validates uploads against BLOCKED_ATTACHMENT_EXTENSIONS and BLOCKED_ATTACHMENT_MIME_TYPES defined in conf/configs/common.py. Both lists omitted .svg and .html, allowing authenticated users to upload active content.
When a visitor opens the resulting attachment URL, the server returns the SVG with a Content-Type: image/svg+xml header. Browsers parse SVG as XML and execute embedded <script> elements. The result is persistent, attacker-controlled script execution against anyone who visits the attachment URL.
Because attachment storage uses a separate origin from the application, the same-origin policy prevents the injected script from reading application cookies or session storage. The maintained deployment configuration does not support application-session compromise through this flaw. The practical impact is limited to phishing, UI redress, and arbitrary active content hosted under a trusted-looking storage URL.
Root Cause
The root cause is a blocklist-based input validation design that failed to enumerate dangerous file types. The configuration omitted SVG and HTML extensions and MIME types, so the serializer accepted them as safe. Blocklist validation is fragile; an allowlist of known-safe formats would have prevented the oversight.
Attack Vector
An authenticated attacker crafts an SVG document containing an embedded <script> payload. The attacker uploads the file through POST /planner/attachments/, which stores it and returns a public URL. The attacker distributes that URL to targets. When a victim loads the URL, the browser renders the SVG and executes the embedded script in the context of the attachment storage origin.
# Security patch in conf/configs/common.py - Release 2.2.60
__copyright__ = "Copyright (c) 2025, Helium Edu"
__license__ = "MIT"
-__version__ = "2.2.59"
+__version__ = "2.2.60"
import json
import os
Source: GitHub Commit f0de5c9
Detection Methods for CVE-2026-55876
Indicators of Compromise
- Attachment records with file extensions .svg or .html created before upgrading to 2.2.60
- HTTP responses from the attachment storage origin carrying Content-Type: image/svg+xml with embedded <script> tags
- Outbound requests from victim browsers to attacker-controlled domains originating from attachment URL referrers
Detection Strategies
- Scan existing attachment storage for files whose MIME type is image/svg+xml or text/html and inspect contents for script elements or event-handler attributes
- Review application logs for POST /planner/attachments/ requests uploading disallowed extensions prior to the 2.2.60 upgrade
- Correlate attachment access logs with unusual referrer patterns indicating URL sharing campaigns
Monitoring Recommendations
- Alert on uploads to /planner/attachments/ where the submitted filename or declared MIME type matches SVG or HTML
- Monitor the attachment storage origin for responses containing executable markup rather than binary image data
- Track user accounts that upload attachments at anomalous rates following credential compromise or new account creation
How to Mitigate CVE-2026-55876
Immediate Actions Required
- Upgrade Helium Platform to version 2.2.60 or later immediately
- Audit existing attachments for SVG and HTML files uploaded prior to the patch and remove or quarantine untrusted entries
- Rotate credentials for any accounts suspected of uploading malicious attachments
Patch Information
The fix is released in Helium 2.2.60. The patch updates the version string in conf/configs/common.py and adds supporting hardening in helium/common/utils/httputils.py. Review the full change in GitHub Commit f0de5c9 and the GitHub Security Advisory GHSA-7r65-76fw-ch5c.
Workarounds
- Configure the attachment storage origin to serve uploaded files with Content-Type: application/octet-stream and Content-Disposition: attachment to force download instead of inline rendering
- Place a reverse proxy rule that rejects uploads whose extension or detected MIME type is SVG or HTML until the patch is applied
- Restrict the /planner/attachments/ endpoint to trusted user roles while planning the upgrade
# Example nginx rule to force download of attachment responses
location /attachments/ {
add_header Content-Disposition "attachment" always;
add_header X-Content-Type-Options "nosniff" always;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

