dbcve.org
ChurchcrmApplication

CVE-2026-35534

HIGH · 7.6 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 7.1.0 or later.
See remediation →
80/100
Remediation priority · High
Remotely reachable

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
ChurchCRM is an open-source church management system. Prior to 7.1.0, a stored cross-site scripting vulnerability exists in PersonView.php due to incorrect use of sanitizeText() as an output sanitizer for HTML attribute context. The function only strips HTML tags, it does not escape quote characters allowing an attacker to break out of the href attribute and inject arbitrary JavaScript event handlers. Any authenticated user with the EditRecords role can store the payload in a person's Facebook field. The XSS fires against any user who views that person's profile page, including administrators, enabling session hijacking and full account takeover. This vulnerability is fixed in 7.1.0.

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 · high confidence

A stored XSS vulnerability in ChurchCRM's PersonView.php allows authenticated users with EditRecords permission to inject malicious JavaScript via the Facebook field. The sanitizeText() function only strips HTML tags without escaping quote characters, enabling attackers to break out of the href attribute and inject arbitrary event handlers that execute when any user views the person's profile.

MitigationUpgrade to ChurchCRM version 7.1.0 or later which implements proper quote escaping. Until patched, restrict EditRecords role to highly trusted users and monitor for suspicious profile modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChurchcrmApplication
Affected:< 7.1.0

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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/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 ChurchCRM version
    Locate the version file or check the admin dashboard for the installed ChurchCRM version number
    Affected if The installed version is lower than 7.1.0 (e.g., 7.0.x, earlier releases)
  2. Verify EditRecords permission exists
    Check user role definitions or permission configuration files for the presence of EditRecords capability
    Affected if EditRecords permission is defined and assignable to users in the system
  3. Confirm PersonView.php is present
    Locate the PersonView.php file in the ChurchCRM web directory and verify the Facebook field handling exists
    Affected if PersonView.php exists and contains code handling a Facebook field input
  4. Inspect sanitizeText() function implementation
    Search the codebase for the sanitizeText() function definition and examine whether it escapes quote characters (single and double) when processing input
    Affected if The sanitizeText() function only strips HTML tags but does not escape quote characters (e.g., no use of htmlspecialchars() with ENT_QUOTES)
  5. Check if Facebook field is publicly viewable
    Review PersonView.php to confirm that the Facebook field value is rendered in an href attribute without additional escaping when any user views a person profile
    Affected if The Facebook field renders inside an HTML attribute (such as href) without proper quote escaping

A user is affected if their ChurchCRM version is below 7.1.0, the sanitizeText() function does not escape quotes, and the Facebook field can be rendered in an unsafe manner within HTML attributes.

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
Upgrade available Upgrade to 7.1.0 or later
Fixed in 7.1.0
Interim mitigation

Upgrade to ChurchCRM version 7.1.0 or later which implements proper quote escaping. Until patched, restrict EditRecords role to highly trusted users and monitor for suspicious profile modifications.

Recommended fix High confidence

7.1.0

  1. Upgrade ChurchCRM to version 7.1.0 or later to obtain the fixed version of PersonView.php with proper output escaping for HTML attribute contexts
  2. After upgrading, verify that the Facebook field correctly escapes quote characters to prevent breaking out of the href attribute
  3. Audit user sessions, particularly those with EditRecords role, as a precaution against potential session hijacking

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

Fix this in Churchcrm 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 the upgrade done

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-35534 — 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-35534 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