parse-community parse-server up to 8.6.83/9.0.0-9.10.0-alpha.2 FileUpload content-type cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.61+ |
Summary
A vulnerability marked as problematic has been reported in parse-community parse-server up to 8.6.83/9.0.0-9.10.0-alpha.2. Affected by this issue is some unknown functionality of the component FileUpload. Performing a manipulation of the argument content-type results in cross site scripting. This vulnerability is cataloged as CVE-2026-61448. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as problematic has been found in parse-community parse-server up to 8.6.83/9.0.0-9.10.0-alpha.2. This affects an unknown code of the component FileUpload. The manipulation of the argument content-type 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 affected by a stored cross-site scripting (XSS) vulnerability in versions >= 9.0.0, < 9.10.0-alpha.2 and <= 8.6.83. When an uploaded file's extension is not recognized by the mime package, Parse Server preserves the client-supplied Content-Type. A malformed Content-Type that is not a valid type/subtype media type (e.g., 'image', 'image/', or 'image//svg+xml') bypasses the fileUpload.fileExtensions blocklist and is stored unchanged. On storage adapters that persist and serve the uploaded Content-Type (such as Amazon S3, Google Cloud Storage, or Azure Blob Storage), a browser cannot parse the malformed value and falls back to MIME-sniffing; a file whose body begins with HTML is rendered as HTML, executing embedded script in the application's origin against other users who open the file URL. The default GridFS storage adapter is not affected. Fixed in 9.10.0-alpha.2 and 8.6.84.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-61448 since 07/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 9.10.0-alpha.2 or 8.6.84 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
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
- 8.6.41
- 8.6.42
- 8.6.43
- 8.6.44
- 8.6.45
- 8.6.46
- 8.6.47
- 8.6.48
- 8.6.49
- 8.6.50
- 8.6.51
- 8.6.52
- 8.6.53
- 8.6.54
- 8.6.55
- 8.6.56
- 8.6.57
- 8.6.58
- 8.6.59
- 8.6.60
- 8.6.61
- 8.6.62
- 8.6.63
- 8.6.64
- 8.6.65
- 8.6.66
- 8.6.67
- 8.6.68
- 8.6.69
- 8.6.70
- 8.6.71
- 8.6.72
- 8.6.73
- 8.6.74
- 8.6.75
- 8.6.76
- 8.6.77
- 8.6.78
- 8.6.79
- 8.6.80
- 8.6.81
- 8.6.82
- 8.6.83
- 9.0.0-9.10.0-alpha.0
- 9.0.0-9.10.0-alpha.1
- 9.0.0-9.10.0-alpha.2
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Cross site scriptingCWE: 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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: parse-server 9.10.0-alpha.2/8.6.84
Timeline
07/09/2026 CVE reserved07/11/2026 Advisory disclosed
07/11/2026 VulDB entry created
07/11/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-61448 (🔒)
GCVE (CVE): GCVE-0-2026-61448
GCVE (VulDB): GCVE-100-377829
Entry
Created: 07/11/2026 16:24Changes: 07/11/2026 16:24 (54)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.