{"answers":{"affected":"3 open source packages ship an affected version, including github.com/traPtitech/traQ.","exploited":"There is no known exploitation of CVE-2025-57813 in the wild and no public exploit code.","fix":"Upgrade github.com/traPtitech/traQ to 3.25.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-57813 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2025-57813 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/traPtitech/traQ (Go): affected all versions; no fix listed\n- github.com/traPtitech/traQ (Go): affected all versions; fixed in 3.25.0\n- github.com/traPtitech/traQ (Go): affected all versions; fixed in 3.25.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-57813/ (Markdown: https://insights.sbomify.com/CVE-2025-57813/index.md)","id":"CVE-2025-57813","markdown":"https://insights.sbomify.com/CVE-2025-57813/index.md","name":"CVE-2025-57813","record":{"aliases":["GHSA-27r7-3m9x-r533","GO-2025-3913"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"traQ messenger","requires_auth":"high_privilege","summary":"Attackers can trigger SQL errors to leak OAuth tokens into logs, allowing log-accessing attackers to steal sensitive credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insertion of Sensitive Information into Log File in github.com/traPtitech/traQ","id":"CVE-2025-57813","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"request-filtering-agent SSRF Bypass via HTTPS Requests","id":"CVE-2025-57814"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/traPtitech/traQ","purl":"pkg:golang/github.com/traPtitech/traQ","source":"GO-2025-3913"},{"ecosystem":"Go","fixed":["3.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/traPtitech/traQ","purl":null,"source":"GHSA-27r7-3m9x-r533"},{"ecosystem":"Go","fixed":["3.25.0"],"introduced":["0"],"last_affected":[],"package":"github.com/traPtitech/traQ","purl":"pkg:golang/github.com/traPtitech/traQ","source":"GHSA-27r7-3m9x-r533"}],"prev":{"headline":"[BIGSLEEP-434612419] CUPS-Filters has heap-buffer-overflow write in `cfImageLut()`","id":"CVE-2025-57812"},"products":["traQ"],"published":"2025-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-08-26","vendors":["traPtitech"]},"summary":"Attackers can trigger SQL errors to leak OAuth tokens into logs, allowing log-accessing attackers to steal sensitive credentials.","url":"https://insights.sbomify.com/CVE-2025-57813/"}