CyberIntel ⬡ News
★ Saved ◆ Cyber Reads
← Back ⬡ Vulnerabilities & CVEs Mar 19, 2026

CVE-2026-32728 | parse-community parse-server up to 8.6.40/9.6.0-alpha.14 File Extension cross site scripting (GHSA-42ph-pf9q-cr72)

VulDB Archived Mar 19, 2026 ✓ Full text saved

A vulnerability classified as problematic was found in parse-community parse-server up to 8.6.40/9.6.0-alpha.14 . Affected by this issue is some unknown functionality of the component File Extension Handler . Such manipulation leads to cross site scripting. This vulnerability is listed as CVE-2026-32728 . The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised.

Full text archived locally
✦ AI Summary · Claude Sonnet


    VDB-351639 · CVE-2026-32728 · GHSA-42PH-PF9Q-CR72 PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.40/9.6.0-ALPHA.14 FILE EXTENSION CROSS SITE SCRIPTING HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 3.4 $0-$5k 1.39+ Summaryinfo A vulnerability, which was classified as problematic, has been found in parse-community parse-server up to 8.6.40/9.6.0-alpha.14. This affects an unknown part of the component File Extension Handler. Performing a manipulation results in cross site scripting. This vulnerability is cataloged as CVE-2026-32728. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component. Detailsinfo A vulnerability classified as problematic has been found in parse-community parse-server up to 8.6.40/9.6.0-alpha.14. This affects an unknown functionality of the component File Extension Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. 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. This is going to have an impact on integrity. The summary by CVE is: Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.15 and 8.6.41, an attacker who is allowed to upload files can bypass the file extension filter by appending a MIME parameter (e.g. `;charset=utf-8`) to the `Content-Type` header. This causes the extension validation to fail matching against the blocklist, allowing active content to be stored and served under the application's domain. In addition, certain XML-based file extensions that can render scripts in web browsers are not included in the default blocklist. This can lead to stored XSS attacks, compromising session tokens, user credentials, or other sensitive data accessible via the browser's local storage. The fix in versions 9.6.0-alpha.15 and 8.6.41 strips MIME parameters from the `Content-Type` header before validating the file extension against the blocklist. The default blocklist has also been extended to include additional XML-based extensions (`xsd`, `rng`, `rdf`, `rdf+xml`, `owl`, `mathml`, `mathml+xml`) that can render active content in web browsers. Note that the `fileUpload.fileExtensions` option is intended to be configured as an allowlist of file extensions that are valid for a specific application, not as a denylist. The default denylist is provided only as a basic default that covers most common problematic extensions. It is not intended to be an exhaustive list of all potentially dangerous extensions. Developers should not rely on the default value, as new extensions that can render active content in browsers might emerge in the future. As a workaround, configure the `fileUpload.fileExtensions` option to use an allowlist of only the file extensions that your application needs, rather than relying on the default blocklist. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-32728 since 03/13/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK. Upgrading to version 8.6.41 or 9.6.0-alpha.15 eliminates this vulnerability. Applying the patch 4f53ab3cad5502a51a509d53f999e00ff7217b8d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor parse-community Name parse-server Version 8.6.0 8.6.1 8.6.2 8.6.3 8.6.4 8.6.5 8.6.6 8.6.7 8.6.8 8.6.9 8.6.10 8.6.11 8.6.12 8.6.13 8.6.14 8.6.15 8.6.16 8.6.17 8.6.18 8.6.19 8.6.20 8.6.21 8.6.22 8.6.23 8.6.24 8.6.25 8.6.26 8.6.27 8.6.28 8.6.29 8.6.30 8.6.31 8.6.32 8.6.33 8.6.34 8.6.35 8.6.36 8.6.37 8.6.38 8.6.39 8.6.40 9.6.0-alpha.0 9.6.0-alpha.1 9.6.0-alpha.2 9.6.0-alpha.3 9.6.0-alpha.4 9.6.0-alpha.5 9.6.0-alpha.6 9.6.0-alpha.7 9.6.0-alpha.8 9.6.0-alpha.9 9.6.0-alpha.10 9.6.0-alpha.11 9.6.0-alpha.12 9.6.0-alpha.13 9.6.0-alpha.14 License open-source Website Product: https://github.com/parse-community/parse-server/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 3.5 VulDB Meta Temp Score: 3.4 VulDB Base Score: 3.5 VulDB Temp Score: 3.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cross site scripting CWE: CWE-79 / CWE-94 / CWE-74 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: parse-server 8.6.41/9.6.0-alpha.15 Patch: 4f53ab3cad5502a51a509d53f999e00ff7217b8d Timelineinfo 03/13/2026 CVE reserved 03/18/2026 +5 days VulDB entry created 03/19/2026 +0 days Advisory disclosed 03/19/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-42ph-pf9q-cr72 Status: Confirmed CVE: CVE-2026-32728 (🔒) GCVE (CVE): GCVE-0-2026-32728 GCVE (VulDB): GCVE-100-351639 Entryinfo Created: 03/19/2026 00:10 Changes: 03/19/2026 00:10 (70) Complete: 🔍 Cache ID: 99:B43:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸
    💬 Team Notes
    Article Info
    Source
    VulDB
    Category
    ⬡ Vulnerabilities & CVEs
    Published
    Mar 19, 2026
    Archived
    Mar 19, 2026
    Full Text
    ✓ Saved locally
    Open Original ↗