Skip to main content
CVE-2026-123418VulnerabilityPublished

The Church Admin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'lat' parameter in all

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123418· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 7 Nov 2026, 13:05 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
andy_moyleChurch AdminAffected
  • <=5.1.7
Fixed in–

AI-suggested

Since the vulnerability affects all versions up to 5.1.7, users should upgrade to a fixed version if available or apply vendor-provided patches once released. In the absence of a patch, disabling the Google Maps API key configuration in Church Admin settings will prevent the vulnerable code path from being reached, mitigating exploitation risk. Monitor the vendor advisory for official fixes and updates.

Description

The Church Admin plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability via the 'lat' parameter in all versions up to and including 5.1.7. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts that execute when a user views the affected page. Exploitation requires that a Google Maps API key be configured in the plugin settings, as the vulnerable code path is only triggered under this condition.

References

Community reviews

Loading reviews…