Authenticated data disclosure via user-controlled identifier
Published Sep 16, 2025 · Updated Sep 16, 2025
IDOR in Beefull before 24.07.2025 allows remote authenticated users to read other users' data by changing a trusted identifier. The published record identifies a user-controlled key but does not disclose the affected request, parameter, object, or missing ownership check. A low-privileged account and network access are required; exploitation crosses user boundaries to disclose data without changing it or interrupting service.
Summary
What happened
IDOR in Beefull before 24.07.2025 allows remote authenticated users to read other users' data by changing a trusted identifier. The published record identifies a user-controlled key but does not disclose the affected request, parameter, object, or missing ownership check. A low-privileged account and network access are required; exploitation crosses user boundaries to disclose data without changing it or interrupting service.
The record
- CVE
- CVE-2025-7355
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- Beefull Enerji Teknolojileri A.Ş.
- Product
- Beefull
- Classifications
- CWE-639, CAPEC-21
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=0 <24.07.2025
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