dbcve.org
Church AdminWordPress extension · Churchadminplugin

CVE-2023-30782

MEDIUM · 6.1 CVSS v3.1 Published 2023-08-16
Fix available
A fix is available. Upgrade to after 3.7.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Andy Moyle Church Admin plugin <= 3.7.5 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A reflected cross-site scripting (XSS) vulnerability exists in the Andy Moyle Church Admin WordPress plugin versions 3.7.5 and below. The vulnerability is unauthenticated, meaning attackers can exploit it without any login credentials by crafting malicious URLs containing JavaScript payloads that get reflected back in the application's response.

MitigationUpdate the Church Admin plugin to a version newer than 3.7.5. If no patched version is available, disable the plugin until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Church AdminWordPress extension
Affected:<= 3.7.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Church Admin plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'church-admin' or similar
    Affected if The Church Admin plugin is found in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Church Admin > View Details, or open the main plugin PHP file (e.g., church-admin.php) and look for the version comment/header, or check the plugin's readme.txt file
    Affected if The version displayed is 3.7.5 or lower, or no version information is found (assume affected)
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if Church Admin shows as 'Active'
    Affected if The plugin is active and vulnerable versions are installed
  4. Check for publicly accessible vulnerable endpoints
    Review plugin source code for $_GET, $_POST, or $_REQUEST parameters that are reflected in output without sanitization. Common XSS vectors in WordPress plugins include parameters in admin pages or public-facing shortcodes
    Affected if The plugin processes user input from URL parameters and echoes it back without proper escaping
  5. Inspect HTTP responses for reflected input
    Craft a test URL with a harmless payload (e.g., ?test=<script>alert(1)</script>) pointing to pages using the plugin, then examine the page source to see if the payload is reflected unescaped
    Affected if The payload appears literally in the response HTML without being escaped or removed

The environment is affected if the Church Admin plugin version 3.7.5 or lower is installed and active on the WordPress site, as the unauthenticated reflected XSS can be triggered via crafted URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.7.5
Interim mitigation

Update the Church Admin plugin to a version newer than 3.7.5. If no patched version is available, disable the plugin until a fix is released.

Recommended fix Moderate confidence

Update to the latest available version of Church Admin plugin (version > 3.7.5)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Church Admin plugin
  4. 4. Check if an update is available (the fixed version is greater than 3.7.5)
  5. 5. If an update is available, click 'Update Now' to apply the security patch
  6. 6. After updating, verify the plugin is running on a version newer than 3.7.5

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Church Admin Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30782 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data