CVE-2026-0682

Church Admin <= 5.0.28 - Authenticated (Administrator+) Blind Server-Side Request Forgery via 'audio_url' Parameter

2026-01-16 14:51
Phap Nguyen Anh

Strategic Overview

Status
Patched in 5.0.29
Affected Plugin
Church Admin
Affected Version
<= 5.0.28
CVSS
2.2Low
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2026-0682
View all Church Admin vulnerabilities

At a glance

CVE-2026-0682 is a low-severity Server-Side Request Forgery (SSRF) vulnerability in the Church Admin WordPress plugin, affecting versions <= 5.0.28. It carries a CVSS score of 2.2 (reachable over the network). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 5.0.29; sites on affected versions should update now. Disclosed January 2026, reported by Phap Nguyen Anh.

Vulnerability Overview

The Church Admin plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.0.28 due to insufficient validation of user-supplied URLs in the 'audio_url' parameter. This makes it possible for authenticated attackers, with Administrator-level access, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-918: Server-Side Request Forgery (SSRF)

Church Admin <= 5.0.28 carries this weakness at audio_url, and reaching it takes an account at Administrator level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Church Admin the fix is 5.0.29: builds <= 5.0.28 are affected, anything from 5.0.29 onward is not.

Remediation

Update to version 5.0.29, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Church Admin 5.0.29 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