CVE-2022-0833

Church Admin <= 3.4.134 - Cross-Site Request Forgery leading to Plugin Backup Disclosure

2022-03-07 00:00
cydave

Strategic Overview

Status
Patched in 3.4.135
Affected Plugin
Church Admin
Affected Version
< 3.4.135
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-0833
View all Church Admin vulnerabilities

At a glance

CVE-2022-0833 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Church Admin WordPress plugin, affecting versions < 3.4.135. 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 3.4.135; sites on affected versions should update now. Disclosed March 2022, reported by cydave.

Vulnerability Overview

The Church Admin plugin for WordPress is vulnerable to Unauthenticated Backup Disclosure in versions up to, and including, 3.4.134. Attackers can repeatedly request the "refresh-backup" action and simultaneously request a publicly accessible temporary file generated by the plugin in order to disclose the final backup filename. Once obtaining that backup name, the plugin lacks sufficient protections to prevent accessing those files externally. This makes it possible for unauthenticated attackers to download the backup of the plugin's data once they conduct this attack, which requires 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 Admin < 3.4.135 carries this weakness at refresh-backup, 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 Admin the fix is 3.4.135: builds < 3.4.135 are affected, anything from 3.4.135 onward is not.

Remediation

Update to version 3.4.135, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Church Admin: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Church Admin 3.4.135 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C