Authenticated access to ACL-protected functionality
Published Jul 18, 2024 · Updated Jun 3, 2026
Broken access control in PruvaSoft Informatics Apinizer Management Console before 2024.05.1 allows authenticated users to bypass ACLs. The public advisory identifies incorrect permissions on a critical resource but does not disclose the affected endpoint, function, or failed authorization check. A low-privileged network account is required, and successful access grants protected functionality with confidentiality, integrity, and availability impact.
Summary
What happened
Broken access control in PruvaSoft Informatics Apinizer Management Console before 2024.05.1 allows authenticated users to bypass ACLs. The public advisory identifies incorrect permissions on a critical resource but does not disclose the affected endpoint, function, or failed authorization check. A low-privileged network account is required, and successful access grants protected functionality with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2024-5618
- Published
- Jul 18, 2024
- Updated
- Jun 3, 2026
- Vendor
- PruvaSoft Informatics
- Product
- Apinizer Management Console
- Classifications
- CWE-732, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 18, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 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 <2024.05.1
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