traQ: XSS in the User Uploaded File Retrieval API
Only affects traQ instances with TRAQ_STORAGE_TYPE set to local. The vulnerability is fixed in traQ 3.28.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.28.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. TRAQ_STORAGE_TYPE is set to local
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 3.28.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
traQ, a messenger application, is affected when it uses local file storage, allowing a user who can upload files to trick another user into opening a crafted SVG or HTML file that runs malicious scripts in the victim's browser. This could let an attacker take actions as the victim or access their data within the application.
Read the original description
traQ is a messenger application built for Digital Creators Club traP. Prior to 3.28.3, instances configured with TRAQ_STORAGE_TYPE=local can return user-uploaded SVG or HTML content from the /files/{fileId} retrieval endpoint for direct browser rendering. An attacker with file-upload capability can provide crafted active content and induce another user to open its file URL, causing attacker-controlled JavaScript to execute in the victim's browser. This issue is fixed in version 3.28.3.
What to do
Check whether your setup matches what the bug needs.
TRAQ_STORAGE_TYPE is set to localUpgrade to a fixed version: 3.28.3.
Workaround: Change TRAQ_STORAGE_TYPE to a storage backend other than local, or ensure all requests to /files/{fileId} include dl=1
Timeline
- CVE published
- First seen by cve.now
Affected versions
- traPtitech traQ
fixed in 3.28.3
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63197
What does this mean?
The User Uploaded File Retrieval API has a cross-site scripting flaw that lets an attacker run arbitrary JavaScript in a victim's browser.Source: github.com
Am I affected, and how do I check?
traQ instances with TRAQ_STORAGE_TYPE set to local, before version 3.28.3. To check, look at the TRAQ_STORAGE_TYPE setting in the instance configuration and the traQ version the instance is running.Source: github.com
What should I do about it?
Upgrade traQ to version 3.28.3 or later, which contains the fix. If an upgrade is not yet possible, the workaround is listed under no-patch guidance.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data