dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-57896

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-22
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

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.26.

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

The Church Admin WordPress plugin versions through 5.0.26 contains a missing authorization vulnerability where incorrectly configured access control security levels allow authenticated users to access functionality beyond their intended permissions. This is a broken access control issue where the plugin fails to properly enforce authorization checks for certain operations.

MitigationUpdate Church Admin to the latest version which should contain proper authorization enforcement, or review and correct the access control configuration to ensure capability checks are properly implemented before sensitive operations.

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. Verify Church Admin plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Church Admin' in the list, or check the file /wp-content/plugins/church-admin/ folder exists
    Affected if The Church Admin plugin is present in the WordPress installation
  2. Determine installed plugin version
    Check the plugin version in the plugin header at /wp-content/plugins/church-admin/church-admin.php (look for 'Version: x.x.x' in the file header) or in WordPress admin under Plugins > Installed Plugins > Church Admin
    Affected if The version number is 5.0.26 or lower
  3. Inspect access control security level configuration
    Check WordPress database wp_options table for option_name containing 'church_admin_access' or 'church_admin_security_level', or look for plugin settings in the admin panel under Church Admin > Settings > Access Control / Security
    Affected if Security level is set to a value that permits authenticated users (subscribers, contributors, or authors) to access administrative-level operations
  4. Verify user role permissions are misaligned
    Review which user roles have access to Church Admin functionality by inspecting the capability settings in the plugin, or test by creating a low-privilege test user (subscriber level) and attempting to access Church Admin features
    Affected if Users with roles below Administrator can access or modify Church Admin data they should not be able to

You are affected if Church Admin plugin version 5.0.26 or lower is installed AND the access control settings allow non-Administrator users to perform sensitive operations beyond their intended permissions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Church Admin to the latest version which should contain proper authorization enforcement, or review and correct the access control configuration to ensure capability checks are properly implemented before sensitive operations.

Recommended fix Moderate confidence

5.0.27 or latest available version

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Church Admin plugin by andy_moyle
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it manually
  6. 6. After updating, verify the plugin is functioning correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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