dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-61983

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

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
Missing Authorization vulnerability in andy_moyle Church Admin church-admin allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Church Admin: from n/a through <= 5.0.30.

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 confidence

Missing authorization vulnerability in the Church Admin WordPress plugin allows exploitation due to incorrectly configured access control security levels, potentially enabling unauthorized users to access functionality or data beyond their intended permission scope.

MitigationImplement and enforce proper role-based access control (RBAC) checks throughout the application to verify user permissions before allowing access to sensitive operations or data.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify Church Admin plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Church Admin. Note the version number displayed, or check the plugin header in wp-content/plugins/church-admin/includes/plugin.php for the Version field.
    Affected if The plugin is installed and the version cannot be verified as patched against CVE-2026-61983, or no patch version is available.
  2. Review user role capabilities
    Use a user role editor plugin or query the wp_usermeta table directly to examine what capabilities are assigned to each role (subscriber, contributor, author, editor, administrator) specifically related to church_admin_* capabilities.
    Affected if Lower-privileged roles (such as subscriber or contributor) have capabilities that should be restricted to higher-privileged roles.
  3. Test access control on sensitive functions
    Using a test account with subscriber-level access, attempt to access Church Admin plugin pages directly via URL or check if menu items for admin functions appear. Inspect the plugin code for capability checks (like current_user_can) before sensitive operations.
    Affected if A lower-privileged user can access admin-level plugin pages, menus, or functions without proper authorization checks.
  4. Inspect plugin security configuration
    Navigate to Church Admin > Settings > Security (or similar) and check the Access Level or Security Level dropdown/configuration to see which user roles are permitted access.
    Affected if The security level is set to allow all users or low-privilege roles (such as subscribers) to access sensitive functionality.
  5. Audit capability checks in plugin code
    Review PHP files in the church-admin plugin directory for functions handling data access or modifications (e.g., attendance, donations, people records). Search for current_user_can() calls and verify they enforce appropriate minimum roles.
    Affected if Sensitive functions lack capability checks or use weak/incorrect capability checks that allow unauthorized access.

A user is affected if the Church Admin plugin is installed and lower-privileged accounts can access plugin functionality or data intended for higher-privileged roles due to missing or inadequate authorization checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement and enforce proper role-based access control (RBAC) checks throughout the application to verify user permissions before allowing access to sensitive operations or data.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61983 — 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-2026-61983 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