Password changes via forged cross-site requests
Published Apr 25, 2023 · Updated Feb 3, 2025
Cross-site request forgery in ChurchCRM 4.5.3 allows remote attackers to change another user's password through a crafted web request. The public record does not identify the password-change endpoint, but it states that the handler accepts a cross-site request that updates another account. A victim must be logged in and induced to load attacker-controlled content; the currently logged-in user's password cannot be changed.
Summary
What happened
Cross-site request forgery in ChurchCRM 4.5.3 allows remote attackers to change another user's password through a crafted web request. The public record does not identify the password-change endpoint, but it states that the handler accepts a cross-site request that updates another account. A victim must be logged in and induced to load attacker-controlled content; the currently logged-in user's password cannot be changed.
The record
- CVE
- CVE-2023-26841
- Published
- Apr 25, 2023
- Updated
- Feb 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 3, 2025Record 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
- 10splayaSec ChurchCRM CSRF disclosureproof 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