CVE-2025-57813

Workaround

If you cannot apply the update immediately, as a temporary workaround, please review access permissions for SQL error logs and strictly limit access to prevent unauthorized users from viewing them.

A vulnerability exists where sensitive information, such as OAuth tokens, is 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.

CVE-2025-57813 has a CVSS score of 5.9 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.25.0); upgrading removes the vulnerable code path.

Kodem intelligence

This vulnerability was temporarily fixed by #2787 and will be completely resolved by #2788.

This issue may have caused OAuth tokens to be leaked to users who can view logs on traQ instances using versions prior to v3.25.0.

While it is possible that OAuth tokens for both human users and Bots were leaked, revoking Bot access tokens is not recommended as it may cause errors. This issue will be resolved in a future update.

Currently, the recommended mitigation is to invalidate the OAuth tokens of human users only. To apply this measure, please execute the following SQL statement directly:

UPDATE oauth2_tokens SET deleted_at = NOW() WHERE deleted_at IS NULL AND scopes != "bot"

1. What is CVE-2025-57813? CVE-2025-57813 is a medium-severity security vulnerability in github.com/traPtitech/traQ (go), affecting versions < 3.25.0. It is fixed in 3.25.0.
2. How severe is CVE-2025-57813? CVE-2025-57813 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/traPtitech/traQ are affected by CVE-2025-57813? github.com/traPtitech/traQ (go) versions < 3.25.0 is affected.
4. Is there a fix for CVE-2025-57813? Yes. CVE-2025-57813 is fixed in 3.25.0. Upgrade to this version or later.
5. Is CVE-2025-57813 exploitable, and should I be worried? Whether CVE-2025-57813 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-57813 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-57813? Upgrade github.com/traPtitech/traQ to 3.25.0 or later.