Transaction disclosure via unauthorized receipt identifier
Published Nov 20, 2024 · Updated Dec 3, 2024
Incorrect access control in eSoft Planner 3.24.08271-USA allows remote authenticated users to view all company transactions. The view_receipt2.php endpoint accepts an unauthorized oid transaction identifier and returns the tenant's complete transaction list instead of rejecting it. Access to a tenant-specific SaaS instance is required; the exposed data includes balances and, through view_receipt.php, notes or special instructions.
Summary
What happened
Incorrect access control in eSoft Planner 3.24.08271-USA allows remote authenticated users to view all company transactions. The view_receipt2.php endpoint accepts an unauthorized oid transaction identifier and returns the tenant's complete transaction list instead of rejecting it. Access to a tenant-specific SaaS instance is required; the exposed data includes balances and, through view_receipt.php, notes or special instructions.
The record
- CVE
- CVE-2024-48536
- Published
- Nov 20, 2024
- Updated
- Dec 3, 2024
- Vendor
- PPC Communications
- Product
- eSoft Planner
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 20, 2024CVE publishedPublication date reported by the CVE source.
- Dec 3, 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=3.24.08271-USA
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
- Unauthorized receipt identifier 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