OAuth token disclosure via GORM SQL error logging
Published Aug 26, 2025 · Updated Aug 26, 2025
Sensitive-data logging in traPtitech traQ before 3.25.0 allows remote authenticated users with log access to read OAuth tokens. The database setup in cmd/serve.go attached a GORM zap logger that recorded failed SQL operations without silent mode, allowing query-associated secrets to enter logs. Exploitation requires triggering an SQL error, such as through database load, and permission to view the resulting logs; exposed tokens can grant access associated with human or bot accounts.
Summary
What happened
Sensitive-data logging in traPtitech traQ before 3.25.0 allows remote authenticated users with log access to read OAuth tokens. The database setup in cmd/serve.go attached a GORM zap logger that recorded failed SQL operations without silent mode, allowing query-associated secrets to enter logs. Exploitation requires triggering an SQL error, such as through database load, and permission to view the resulting logs; exposed tokens can grant access associated with human or bot accounts.
The record
- CVE
- CVE-2025-57813
- Published
- Aug 26, 2025
- Updated
- Aug 26, 2025
- Vendor
- traPtitech
- Product
- traQ
- Classifications
- CWE-532, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2025CVE publishedPublication date reported by the CVE source.
- Aug 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.25.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo