Document renaming via forged authenticated browser requests
Published Aug 3, 2021 · Updated Aug 4, 2024
Cross-site request forgery in SeedDMS 5.1.x before 5.1.23 and 6.0.x before 6.0.16 allows remote attackers to rename documents. The /op/op.Ajax.php endpoint accepts a state-changing document-name request from an authenticated browser without verifying that the user intended it. Exploitation requires an authenticated user to visit attacker-controlled content, and the bounded consequence is unauthorized document-name modification.
Summary
What happened
Cross-site request forgery in SeedDMS 5.1.x before 5.1.23 and 6.0.x before 6.0.16 allows remote attackers to rename documents. The /op/op.Ajax.php endpoint accepts a state-changing document-name request from an authenticated browser without verifying that the user intended it. Exploitation requires an authenticated user to visit attacker-controlled content, and the bounded consequence is unauthorized document-name modification.
The record
- CVE
- CVE-2021-35343
- Published
- Aug 3, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- 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.
Weakness, pattern, technique
Public exploit references
- CyberDivision CVE-2021-35343 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