Department modification via missing CSRF protection
Published Mar 12, 2020 · Updated Aug 4, 2024
CSRF in admin/manage-departments.php in Chadha PHPKB Standard Multi-Language 9 allows attackers to edit a department by ID. The endpoint accepts a state-changing department update without validating an anti-CSRF token, allowing a crafted request to carry the victim's authenticated session. A logged-in superuser must visit attacker-controlled content; successful exploitation changes department names or visibility settings within that account's authority.
Summary
What happened
CSRF in admin/manage-departments.php in Chadha PHPKB Standard Multi-Language 9 allows attackers to edit a department by ID. The endpoint accepts a state-changing department update without validating an anti-CSRF token, allowing a crafted request to carry the victim's authenticated session. A logged-in superuser must visit attacker-controlled content; successful exploitation changes department names or visibility settings within that account's authority.
The record
- CVE
- CVE-2020-10501
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2020CVE 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
- PHPKB v9 department-editing 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