Sensitive data disclosure via public transaction logs
Published Jan 1, 2024 · Updated Jan 9, 2026
Sensitive information exposure in PayHere Payment Gateway before 2.2.12 allows remote attackers to read transaction log data. The payhere_log() function automatically writes transaction data to files reachable through the web server without access control. Exploitation requires a transaction to create a log; the reported consequence is unauthenticated disclosure of logged sensitive data.
Summary
What happened
Sensitive information exposure in PayHere Payment Gateway before 2.2.12 allows remote attackers to read transaction log data. The payhere_log() function automatically writes transaction data to files reachable through the web server without access control. Exploitation requires a transaction to create a log; the reported consequence is unauthenticated disclosure of logged sensitive data.
The record
- CVE
- CVE-2023-6064
- Published
- Jan 1, 2024
- Updated
- Jan 9, 2026
- Vendor
- PayHere
- Product
- PayHere Payment Gateway
- Classifications
- CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2024CVE publishedPublication date reported by the CVE source.
- Jan 9, 2026Record 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=0 <2.2.12
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- WPScan log-file disclosure proof of conceptproof of concept · unverified
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