Unauthenticated sensitive-data disclosure via exposed log
Published Aug 28, 2025 · Updated Apr 28, 2026
Sensitive-data exposure in Hesabfa Accounting 2.2.5 and earlier allows remote attackers to read plugin log contents without authentication. Patchstack identifies a log file as the exposure point but does not disclose the code path, failed access-control operation, request route, or logged fields. No account or user interaction is required, and the reported consequence is limited to reading sensitive data from the log.
Summary
What happened
Sensitive-data exposure in Hesabfa Accounting 2.2.5 and earlier allows remote attackers to read plugin log contents without authentication. Patchstack identifies a log file as the exposure point but does not disclose the code path, failed access-control operation, request route, or logged fields. No account or user interaction is required, and the reported consequence is limited to reading sensitive data from the log.
The record
- CVE
- CVE-2025-48361
- Published
- Aug 28, 2025
- Updated
- Apr 28, 2026
- Vendor
- Saeed Sattar Beglou
- Product
- Hesabfa Accounting
- Classifications
- CWE-201, CAPEC-37, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 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.5
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