Document locking via forged authenticated requests
Published Aug 3, 2021 · Updated Aug 4, 2024
CSRF in SeedDMS 5.1.x before 5.1.23 and 6.0.x before 6.0.16 allows remote attackers to lock documents through a victim's session. The /op/op.LockDocument.php endpoint accepts a document-locking request without verifying that the authenticated user intended to submit it. A victim must be signed in and visit an attacker-controlled page; exploitation changes only the document's lock state.
Summary
What happened
CSRF in SeedDMS 5.1.x before 5.1.23 and 6.0.x before 6.0.16 allows remote attackers to lock documents through a victim's session. The /op/op.LockDocument.php endpoint accepts a document-locking request without verifying that the authenticated user intended to submit it. A victim must be signed in and visit an attacker-controlled page; exploitation changes only the document's lock state.
The record
- CVE
- CVE-2021-36542
- Published
- Aug 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Public exploit references
- CyberDivision SeedDMS 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