Unauthorized actions through forged authenticated requests
Published May 7, 2026 · Updated May 7, 2026
Cross-site request forgery in DivvyDrive 4.8.2.9 and later before 4.8.3.2 allows remote attackers to perform unauthorized actions. The public advisory does not identify the affected endpoint or disclose how the request handler fails to verify the origin or intent of state-changing input. Exploitation requires an authenticated user to submit an attacker-controlled request, and the published consequence is unauthorized modification under that user's privileges.
Summary
What happened
Cross-site request forgery in DivvyDrive 4.8.2.9 and later before 4.8.3.2 allows remote attackers to perform unauthorized actions. The public advisory does not identify the affected endpoint or disclose how the request handler fails to verify the origin or intent of state-changing input. Exploitation requires an authenticated user to submit an attacker-controlled request, and the published consequence is unauthorized modification under that user's privileges.
The record
- CVE
- CVE-2026-5791
- Published
- May 7, 2026
- Updated
- May 7, 2026
- Vendor
- DivvyDrive Bilişim Teknolojileri A.Ş.
- Product
- Divvy Drive
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2026CVE publishedPublication date reported by the CVE source.
- May 7, 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=4.8.2.9 <4.8.3.2
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