Database disclosure via unsanitized event type identifier
Published May 4, 2023 · Updated Jan 29, 2025
SQL injection in ChurchCRM 4.5.4 allows remote authenticated users to read database contents through the EN_tyid POST parameter. EditEventTypes.php concatenates the unsanitized event-type identifier directly into an SQL query, permitting time-delay expressions to act as a data oracle. A valid ChurchCRM login is required; the published proof of concept infers database names and software versions through response timing.
Summary
What happened
SQL injection in ChurchCRM 4.5.4 allows remote authenticated users to read database contents through the EN_tyid POST parameter. EditEventTypes.php concatenates the unsanitized event-type identifier directly into an SQL query, permitting time-delay expressions to act as a data oracle. A valid ChurchCRM login is required; the published proof of concept infers database names and software versions through response timing.
The record
- CVE
- CVE-2023-29842
- Published
- May 4, 2023
- Updated
- Jan 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 4, 2023CVE publishedPublication date reported by the CVE source.
- Jan 29, 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
- Authenticated blind SQL injection proof of conceptfunctional · demonstrated
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