● High · CVSS 7.6

How to Fix CVE-2026-35534: ChurchCRM has Stored XSS in PersonView.php via Facebook Field Attribute Injection

Q: Is CVE-2026-35534 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-35534?

CVSS rates it 7.6 (High). Use that score to set your patch priority alongside the other items in your queue.

Q: Do I have to take CRM offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-35534 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance


Severity	CVSS 7.6, High
Actively exploited?	No
Affected	Churchcrm CRM (< 7.1.0)
Fixed in	7.1.0
Type (CWE)	CWE-79: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CVE-2026-35534 is a churchcrm has stored xss in personview.php via facebook field attribute injection in Churchcrm CRM. The fix is to upgrade to 7.1.0 and apply the runnable commands below.

What is CVE-2026-35534?

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.

In practical terms, a successful attacker gets execution of attacker-controlled JavaScript in a victim's browser. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You are affected if you run Churchcrm CRM at a version listed in the Affected row above. Probe your installed build with the commands below.


# Confirm the installed version via your package manager
dpkg -l | grep -i crm   # Debian/Ubuntu
rpm -qa | grep -i crm   # RHEL/CentOS/Rocky

How to fix CVE-2026-35534

The primary fix is to upgrade to the patched build listed in the Fixed in row above (7.1.0). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


sudo apt-get update
sudo apt-get install --only-upgrade crm
# Confirm the installed version meets or exceeds 7.1.0
dpkg -s crm | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security crm -y
rpm -q crm

Windows (PowerShell, admin)


winget upgrade --id 'Churchcrm.CRM' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\CRM-7.1.0.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows): detect, back up, upgrade, verify, log


# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\CRM-Patch-CVE-2026-35534.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-35534 remediation for Churchcrm CRM"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*CRM*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'7.1.0') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\CRM-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Churchcrm\CRM"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer
$installer = "$env:TEMP\CRM-7.1.0.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*CRM*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'7.1.0') {
    Write-Log "SUCCESS: now at $verify (>= 7.1.0)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux): detect, back up, upgrade, verify, log


#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/crm-patch-cve-2026-35534.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-35534 remediation for Churchcrm CRM"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s crm >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' crm)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q crm >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' crm)
    PKG_MGR=dnf
else
    log "crm not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: crm=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/crm-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/crm /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y crm
else
    sudo dnf upgrade --security -y crm
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' crm)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' crm)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against 7.1.0 and restart the affected service if needed."

If you cannot patch immediately

These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.


add_header Content-Security-Policy "default-src 'self'; script-src 'self'" always;
add_header X-Frame-Options DENY always;
add_header X-Content-Type-Options nosniff always;

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


dpkg -l | grep -i "crm"   # Debian/Ubuntu
rpm -qa | grep -i "crm"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed 7.1.0.

Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-35534 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

This advisory covers multiple CVE IDs. The same patched build closes every entry below:

Frequently asked questions

Is CVE-2026-35534 being actively exploited?