CVE-2025-57813: traPtitech traQ · Sensitive Data in Logs
Affects traPtitech traQSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 3.25.0 when convenient.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.25.0
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade traPtitech traQ to 3.25.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| traPtitech traQ | Affected
| Fixed in
|
AI-suggested
- Upgrade traQ to version 3.25.0 or later, where the vulnerability has been patched to prevent sensitive information from being logged during SQL errors.
- If immediate upgrading is not possible, implement strict access controls on SQL error log files. Ensure that only trusted administrators with a clear need can access these logs.
- Regularly audit log file permissions and access logs to detect any unauthorized access attempts.
- Monitor database performance and error rates to detect abnormal loads or error patterns that could indicate attempts to trigger SQL errors maliciously.
- Implement network segmentation and role-based access controls to limit the number of users who can view sensitive logs.
- Educate administrators and users with elevated privileges about the risks of exposing sensitive tokens and the importance of secure log management.
- Consider additional logging configurations that mask or exclude sensitive tokens from logs.
- Review OAuth token lifecycle policies to ensure tokens are short-lived and can be revoked promptly if compromised.
Description
traQ is a messenger application built for Digital Creators Club traP. Prior to version 3.25.0, a vulnerability exists where sensitive information, such as OAuth tokens, are recorded in log files when an error occurs during the execution of an SQL query. An attacker could intentionally trigger an SQL error by methods such as placing a high load on the database. This could allow an attacker who has the authority to view the log files to illicitly acquire the recorded sensitive information. This vulnerability has been patched in version 3.25.0. If upgrading is not possible, a temporary workaround involves reviewing access permissions for SQL error logs and strictly limiting access to prevent unauthorized users from viewing them.