Account takeover via forged password change
Published Mar 29, 2022 · Updated Aug 3, 2024
Cross-site request forgery in Pluck CMS 4.7.15 allows remote attackers to change a user's password through an authenticated browser. The password-change feature accepts a forged cross-origin request under the victim's active session without an effective anti-CSRF check. The attack requires an authenticated user to load attacker-controlled content; success resets the selected account's password and enables account takeover.
Summary
What happened
Cross-site request forgery in Pluck CMS 4.7.15 allows remote attackers to change a user's password through an authenticated browser. The password-change feature accepts a forged cross-origin request under the victim's active session without an effective anti-CSRF check. The attack requires an authenticated user to load attacker-controlled content; success resets the selected account's password and enables account takeover.
The record
- CVE
- CVE-2022-27432
- Published
- Mar 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
- Pluck CMS 4.7.15 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