Account profile modification via tokenless update request
Published Aug 4, 2024 · Updated Aug 7, 2024
Cross-site request forgery in Siamonhasan Warehouse Inventory System 1.0 and 2.0 allows remote attackers to alter a user's account profile. The edit_account.php update handler accepts posted name and username values and writes them to the logged-in user's database record without validating an anti-CSRF token. A targeted user must be authenticated and induced to submit the crafted request; the demonstrated consequence is unauthorized profile-name and username modification.
Summary
What happened
Cross-site request forgery in Siamonhasan Warehouse Inventory System 1.0 and 2.0 allows remote attackers to alter a user's account profile. The edit_account.php update handler accepts posted name and username values and writes them to the logged-in user's database record without validating an anti-CSRF token. A targeted user must be authenticated and induced to submit the crafted request; the demonstrated consequence is unauthorized profile-name and username modification.
The record
- CVE
- CVE-2024-7459
- Published
- Aug 4, 2024
- Updated
- Aug 7, 2024
- Vendor
- Siamonhasan
- Product
- Warehouse Inventory System
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 7, 2024Record 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
- Affected versionversion=2.0
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
- edit_account.php CSRF 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