Church Content – Sermons, Events and More <= 2.6 - Cross-Site Request Forgery to Notice Dismissal
Strategic Overview
- Status
- Patched in 2.6.1
- Affected Plugin
- Church Content – Sermons, Events and More
- Affected Version
<= 2.6- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2024-32094
At a glance
CVE-2024-32094 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Church Content WordPress plugin, affecting versions <= 2.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.6.1; sites on affected versions should update now. Disclosed April 2024, reported by Dhabaleshwar Das.
Vulnerability Overview
The Church Content – Sermons, Events and More plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.6. This is due to missing or incorrect nonce validation on the ctc_hide_theme_support_notice() function. This makes it possible for unauthenticated attackers to hide a theme support notice via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Church Content <= 2.6 carries this weakness at ctc_hide_theme_support_notice(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Church Content the fix is 2.6.1: builds <= 2.6 are affected, anything from 2.6.1 onward is not.
Remediation
Update to version 2.6.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Church Content: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Church Content 2.6.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C