CVE-2026-0682: CWE-918 Server-Side Request Forgery (SSRF) in andy_moyle Church Admin
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.
AI Analysis
Technical Summary
CVE-2026-0682 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Church Admin plugin for WordPress, developed by andy_moyle. This vulnerability exists in all versions up to and including 5.0.28 due to inadequate validation of user-supplied URLs in the 'audio_url' parameter. SSRF vulnerabilities allow attackers to abuse the server to send crafted HTTP requests to arbitrary locations, potentially accessing internal or protected network resources that are not directly accessible from the outside. In this case, exploitation requires the attacker to have authenticated administrator-level access to the WordPress site, which limits the attack surface but still poses a significant risk if such credentials are compromised. The attacker can leverage this flaw to make the server perform requests to internal services, potentially querying or modifying sensitive information within the internal network. The vulnerability has a CVSS v3.1 base score of 2.2, reflecting low severity due to the high privileges required and the limited impact on confidentiality and availability. No public exploits or active exploitation in the wild have been reported to date. The lack of a patch link suggests that a fix may not yet be publicly available, emphasizing the need for mitigation strategies. This vulnerability falls under CWE-918, which covers SSRF issues. Given the plugin’s niche use in church administration, the affected systems are likely WordPress sites operated by religious organizations or related entities.
Potential Impact
The primary impact of CVE-2026-0682 is the potential for an authenticated administrator to leverage SSRF to interact with internal network services that are otherwise inaccessible externally. This can lead to unauthorized information disclosure or modification within internal systems, potentially exposing sensitive data or enabling further lateral movement within an organization's network. However, since exploitation requires administrator-level access, the risk is mitigated by the need to first compromise or have legitimate access to a high-privilege account. The vulnerability does not directly impact confidentiality or availability of the WordPress site itself but may expose internal infrastructure to reconnaissance or manipulation. Organizations with internal services that trust the web server or have weak internal segmentation are at higher risk. The lack of known exploits in the wild reduces immediate threat but does not eliminate future risk. Overall, the impact is limited but could be significant in environments where internal services are critical and poorly isolated.
Mitigation Recommendations
To mitigate CVE-2026-0682, organizations should: 1) Immediately restrict administrator access to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication to reduce the risk of credential compromise. 2) Monitor and audit administrator activities for suspicious behavior that could indicate exploitation attempts. 3) Implement strict input validation and sanitization for the 'audio_url' parameter or any user-supplied URLs within the plugin, ideally by applying whitelisting of allowed domains or disabling the feature if not needed. 4) Employ network segmentation and firewall rules to limit the web server’s ability to initiate requests to sensitive internal services, effectively containing SSRF exploitation potential. 5) Keep the Church Admin plugin and WordPress core updated, and monitor vendor advisories for patches addressing this vulnerability. 6) Use web application firewalls (WAFs) configured to detect and block SSRF patterns, especially those originating from authenticated sessions. 7) Conduct internal penetration testing to identify and remediate SSRF and related vulnerabilities proactively.
Affected Countries
United States, United Kingdom, Canada, Australia, Germany, France, Brazil, South Africa, Philippines, India
CVE-2026-0682: CWE-918 Server-Side Request Forgery (SSRF) in andy_moyle Church Admin
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-0682 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Church Admin plugin for WordPress, developed by andy_moyle. This vulnerability exists in all versions up to and including 5.0.28 due to inadequate validation of user-supplied URLs in the 'audio_url' parameter. SSRF vulnerabilities allow attackers to abuse the server to send crafted HTTP requests to arbitrary locations, potentially accessing internal or protected network resources that are not directly accessible from the outside. In this case, exploitation requires the attacker to have authenticated administrator-level access to the WordPress site, which limits the attack surface but still poses a significant risk if such credentials are compromised. The attacker can leverage this flaw to make the server perform requests to internal services, potentially querying or modifying sensitive information within the internal network. The vulnerability has a CVSS v3.1 base score of 2.2, reflecting low severity due to the high privileges required and the limited impact on confidentiality and availability. No public exploits or active exploitation in the wild have been reported to date. The lack of a patch link suggests that a fix may not yet be publicly available, emphasizing the need for mitigation strategies. This vulnerability falls under CWE-918, which covers SSRF issues. Given the plugin’s niche use in church administration, the affected systems are likely WordPress sites operated by religious organizations or related entities.
Potential Impact
The primary impact of CVE-2026-0682 is the potential for an authenticated administrator to leverage SSRF to interact with internal network services that are otherwise inaccessible externally. This can lead to unauthorized information disclosure or modification within internal systems, potentially exposing sensitive data or enabling further lateral movement within an organization's network. However, since exploitation requires administrator-level access, the risk is mitigated by the need to first compromise or have legitimate access to a high-privilege account. The vulnerability does not directly impact confidentiality or availability of the WordPress site itself but may expose internal infrastructure to reconnaissance or manipulation. Organizations with internal services that trust the web server or have weak internal segmentation are at higher risk. The lack of known exploits in the wild reduces immediate threat but does not eliminate future risk. Overall, the impact is limited but could be significant in environments where internal services are critical and poorly isolated.
Mitigation Recommendations
To mitigate CVE-2026-0682, organizations should: 1) Immediately restrict administrator access to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication to reduce the risk of credential compromise. 2) Monitor and audit administrator activities for suspicious behavior that could indicate exploitation attempts. 3) Implement strict input validation and sanitization for the 'audio_url' parameter or any user-supplied URLs within the plugin, ideally by applying whitelisting of allowed domains or disabling the feature if not needed. 4) Employ network segmentation and firewall rules to limit the web server’s ability to initiate requests to sensitive internal services, effectively containing SSRF exploitation potential. 5) Keep the Church Admin plugin and WordPress core updated, and monitor vendor advisories for patches addressing this vulnerability. 6) Use web application firewalls (WAFs) configured to detect and block SSRF patterns, especially those originating from authenticated sessions. 7) Conduct internal penetration testing to identify and remediate SSRF and related vulnerabilities proactively.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-01-07T18:03:26.237Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 696b0749b22c7ad868788fd3
Added to database: 1/17/2026, 3:51:37 AM
Last enriched: 2/26/2026, 6:34:57 PM
Last updated: 3/25/2026, 2:50:32 AM
Views: 104
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.