CVE-2024-53795
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 · uneditedMissing Authorization vulnerability in andy_moyle Church Admin church-admin allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Church Admin: from n/a through <= 5.0.8.
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 · moderate confidenceThe Church Admin WordPress plugin (versions <= 5.0.8) contains a missing authorization vulnerability where certain functionality is not properly constrained by access control lists (ACLs), allowing users to access sensitive operations without proper authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed Church Admin plugin versionIn the WordPress admin dashboard, go to Plugins > Installed Plugins and locate the Church Admin plugin to view its current version numberAffected if The installed version is 5.0.8 or lower (any version up to and including 5.0.8)
-
Confirm WordPress user accounts existNavigate to Users > All Users in the WordPress admin panel to see if any user accounts are registeredAffected if There is at least one user account in the WordPress installation
-
Inspect plugin authorization logicExamine the church-admin plugin files in wp-content/plugins/church-admin/ for capability checks before sensitive operations - look for current_user_can() or role-based validation functionsAffected if The plugin code does not perform proper capability or role checks before executing sensitive functions
-
Test access to sensitive operations with limited privilegesUsing a low-privilege user account (such as Subscriber or Contributor), attempt to access any administrative functions or data within the Church Admin pluginAffected if A user without administrator role can access or modify sensitive church data or plugin settings
The environment is affected if the Church Admin plugin version is 5.0.8 or lower AND sensitive operations can be accessed without proper authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement proper authorization checks (capability checks, nonce verification, role-based access control) on all sensitive functions and update to the latest patched version of the plugin.
Version 5.0.9 or latest available release of Church Admin plugin
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Church Admin
- Check if version 5.0.9 or later is available
- If available, update the Church Admin plugin to the latest version
- If no update is available, consider temporarily disabling the plugin until a fix is released
- Verify the update was successful and test the site's functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-53795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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