Browser script execution via Event Sermon injection
Published Feb 21, 2024 · Updated Mar 28, 2025
Self-XSS in ChurchCRM 5.5.0 allows attackers to execute script in a user's browser through the Event Sermon field in EventEditor.php. EventEditor.php accepts malicious JavaScript or HTML in the Event Sermon value without sufficient validation before browser interpretation. Exploitation requires a user to submit the payload in the event editor; execution can expose data or perform actions within that user's session.
Summary
What happened
Self-XSS in ChurchCRM 5.5.0 allows attackers to execute script in a user's browser through the Event Sermon field in EventEditor.php. EventEditor.php accepts malicious JavaScript or HTML in the Event Sermon value without sufficient validation before browser interpretation. Exploitation requires a user to submit the payload in the event editor; execution can expose data or perform actions within that user's session.
The record
- CVE
- CVE-2024-25898
- Published
- Feb 21, 2024
- Updated
- Mar 28, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2024CVE publishedPublication date reported by the CVE source.
- Mar 28, 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
- Event Sermon self-XSS payloadproof of concept · 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