Settings modification via forged cross-site requests
Published Dec 26, 2023 · Updated Sep 12, 2024
Cross-site request forgery in GROWI before 6.0.0 allows remote attackers to change an authenticated user's settings via a malicious page. The personal-settings workflow accepts external-site state-changing requests, but public advisories do not identify the handler or missing request-validation check. Exploitation requires the victim to remain logged in and view attacker-controlled content, and the demonstrated consequence is unauthorized settings modification.
Summary
What happened
Cross-site request forgery in GROWI before 6.0.0 allows remote attackers to change an authenticated user's settings via a malicious page. The personal-settings workflow accepts external-site state-changing requests, but public advisories do not identify the handler or missing request-validation check. Exploitation requires the victim to remain logged in and view attacker-controlled content, and the demonstrated consequence is unauthorized settings modification.
The record
- CVE
- CVE-2023-46699
- Published
- Dec 26, 2023
- Updated
- Sep 12, 2024
- Vendor
- WESEEK, Inc.
- Product
- GROWI
- Classifications
- CWE-352, CAPEC-62, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 26, 2023CVE publishedPublication date reported by the CVE source.
- Sep 12, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=prior to v6.0.0
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