User-record disclosure via forged database-selection cookie
Published Mar 2, 2025 · Updated Mar 3, 2025
Improper authorization in pbrong hrms 1.0.0 through 1.0.1 allows remote attackers to read user records through a crafted cookie. HrmsDB splits the attacker-controlled user_cookie value and trusts its embedded database name when selecting the branch database for PasswordQuery. No authentication is required; a forged cookie sent to /password/query/all exposes records for non-root and non-admin users.
Summary
What happened
Improper authorization in pbrong hrms 1.0.0 through 1.0.1 allows remote attackers to read user records through a crafted cookie. HrmsDB splits the attacker-controlled user_cookie value and trusts its embedded database name when selecting the branch database for PasswordQuery. No authentication is required; a forged cookie sent to /password/query/all exposes records for non-root and non-admin users.
The record
- CVE
- CVE-2025-1815
- Published
- Mar 2, 2025
- Updated
- Mar 3, 2025
- Vendor
- pbrong
- Product
- hrms
- Classifications
- CWE-285, CWE-266, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 2025CVE publishedPublication date reported by the CVE source.
- Mar 3, 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=1.0.0
- Affected versionversion=1.0.1
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.
Weakness, pattern, technique
Public exploit references
- CVE-2025-1815 forged user_cookie HTTP proof of conceptproof of concept · demonstrated
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