CVE-2025-57813 Insertion of Sensitive Information into Log File in github.com/traPtitech/traQ
Attackers can trigger SQL errors to leak OAuth tokens into logs, allowing log-accessing attackers to steal sensitive credentials.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-57813?
CVE-2025-57813 is a medium-severity vulnerability in traPtitech traQ, published on 26 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Official 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.
Weakness: CWE-532
Which versions are affected by CVE-2025-57813?
3 open source packages ship an affected version, including github.com/traPtitech/traQ.
| Package | Affected | Fixed in |
|---|---|---|
github.com/traPtitech/traQ Go | All versions | None |
github.com/traPtitech/traQ Go | All versions | 3.25.0 |
github.com/traPtitech/traQ Go | All versions | 3.25.0 |
How do I fix CVE-2025-57813?
Upgrade github.com/traPtitech/traQ to 3.25.0 or later.
Is CVE-2025-57813 being exploited?
There is no known exploitation of CVE-2025-57813 in the wild and no public exploit code.
Sources
Also known as GHSA-27r7-3m9x-r533, GO-2025-3913.