Skip to main content
Menu
CVEs

Church Admin broken access control in WordPress plugin

CVE-2026-125792EUVD-2026-125512GHSA-G68H-P56G-V4HWPublished November 13, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 5.1.9
Who is exposed
Not reported

Summary

The Church Admin plugin for WordPress, made by Andy Moyle, has a missing authorization flaw that lets an attacker exploit incorrectly configured access control levels. It can be reached remotely over the network without logging in, and the attacker can gain limited access to the plugin's functions.

Written by a model

Original description

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

What to do

Upgrade to a fixed version: 5.1.9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125792 (WordPress Church Admin plugin <= 5.1.8 - Broken Access Control vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125792 (entry last updated 2026-11-13):
Affected:
- Andy Moyle Church Admin: fixed in 5.1.9
Fixed versions: 5.1.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125792 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125792 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/church-admin/vulnerability/wordpress-church-admin-plugin-5-1-8-broken-access-control-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125792
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125792"}.

Affected versions

cve.now Index

25of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Public exploit activity

100%0Nov 13Nov 20
  • EPSS: 0.35%

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

Questions about CVE-2026-125792

Is CVE-2026-125792 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-125792?

church-admin: through 5.1.8 (fixed in 5.1.9).

Source: cve.now feed data

How do I fix CVE-2026-125792?

Upgrade to a fixed version: 5.1.9.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.