Credential disclosure via third-party login debug logging
Published Jul 23, 2025 · Updated Jul 23, 2025
Sensitive-data exposure in PCL Community Edition 2.12.0-beta.5 through 2.12.0-beta.9 allows attackers to read login credentials from local logs. Debug output in the third-party login path writes the credentials supplied during authentication into the application’s local log file. Disclosure requires a user to manually share that log, after which its recipient can obtain the recorded credentials.
Summary
What happened
Sensitive-data exposure in PCL Community Edition 2.12.0-beta.5 through 2.12.0-beta.9 allows attackers to read login credentials from local logs. Debug output in the third-party login path writes the credentials supplied during authentication into the application’s local log file. Disclosure requires a user to manually share that log, after which its recipient can obtain the recorded credentials.
The record
- CVE
- CVE-2025-54120
- Published
- Jul 23, 2025
- Updated
- Jul 23, 2025
- Vendor
- PCL Community
- Product
- PCL Community Edition
- Classifications
- CWE-532
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2025CVE publishedPublication date reported by the CVE source.
- Jul 23, 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=>= 2.12.0-beta.5, < 2.12.0-beta.10
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