How to Fix CVE-2026-40483: Cross-site scripting in CRM
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 5.4 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | ChurchCRM < 7.2.0 |
| Fixed in | CRM 7.2.0 |
| Type (CWE) | CWE-79: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') |
What is CVE-2026-40483?
ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the Pledge Editor renders donation comment values directly into HTML input value attributes without escaping via htmlspecialchars(). An authenticated user with Finance permissions can inject HTML attribute-breaking characters and event handlers into the comment field, which are stored in the database and execute in the browser of any user who subsequently opens the pledge record for editing, resulting in stored XSS. This issue has been fixed in version 7.2.0.
Am I affected?
Run the version check that matches your platform:
# Windows
winget list | findstr /I "crm"
Get-WmiObject Win32_Product | Where-Object { $_.Name -like "*CRM*" } | Select-Object Name, Version
Compare what you see against the Affected row above (ChurchCRM < 7.2.0). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-40483
The primary fix is to upgrade CRM to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: CRM 7.2.0.
Windows (PowerShell, run as administrator)
# Check installed version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
# Apply latest Microsoft security updates (Windows Update)
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck
Import-Module PSWindowsUpdate
Get-WindowsUpdate -MicrosoftUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -AutoReboot
# Or via winget for application-level patches
winget upgrade --all --accept-source-agreements --accept-package-agreements
If the affected component is a third-party application, identify the package and run:
winget upgrade --id <vendor.product>
Replace <vendor.product> with the actual winget identifier (run winget search CRM to find it).
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-40483 affecting CRM
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-40483-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append
try {
Write-Host "[1/4] Detecting installed version of CRM"
$pkg = winget list --id "CRM" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\CRM-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\CRM" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to CRM 7.2.0"
winget upgrade --id "CRM" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "CRM"
Write-Host "Fix applied. Reboot if prompted."
exit 0
} catch {
Write-Error "Patch failed: $_"
exit 1
} finally {
Stop-Transcript
}
Complete Bash remediation script (Linux)
#!/usr/bin/env bash
# Fix script for CVE-2026-40483 affecting CRM
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-40483-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s crm 2>/dev/null | grep -i version || echo "crm not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q crm || echo "crm not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-40483-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/crm /etc/crm.d /etc/crm.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: CRM 7.2.0)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y crm
elif command -v dnf >/dev/null; then
dnf upgrade --security -y crm
elif command -v yum >/dev/null; then
yum update -y crm
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s crm 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q crm
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Windows firewall isolation
# Allow only management subnet to reach the vulnerable service
New-NetFirewallRule -DisplayName "Restrict CRM" `
-Direction Inbound -Action Block -RemoteAddress Any `
-Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Allow Mgmt CRM" `
-Direction Inbound -Action Allow -RemoteAddress 10.0.0.0/8 `
-Protocol TCP -LocalPort 443
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop crm
sudo systemctl disable crm
How to verify the fix worked
# Linux
crm --version 2>/dev/null || dpkg -s crm | grep -i version
rpm -q crm 2>/dev/null || true
# Windows
winget list | findstr /I "crm"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above CRM 7.2.0. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-22493: Critical Vulnerability in Gaspard — Critical Vulnerability in Gaspard
- How to Fix CVE-2026-3059: CVE-2026-3059 in SGLang — CVE-2026-3059 in SGLang
- How to Fix CVE-2026-0608: Critical Vulnerability in Head Meta Data , Critical Vulnerability in Head Meta Data
- How to Fix CVE-2026-2640: CWE-269: Improper Privilege Management in PC Manager , CWE-269: Improper Privilege Management in PC Manager
- How to Fix CVE-2026-36438: Critical Vulnerability in n/a , Critical Vulnerability in n/a
Is CVE-2026-40483 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
5.4 (medium). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://github.com/ChurchCRM/CRM/security/advisories/GHSA-wjmf-w8gj-rx7g
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40483
- https://github.com/ChurchCRM/CRM/pull/8609
- https://github.com/ChurchCRM/CRM/commit/b3da72a2b35f9c600e340a9dfd35e7792ff4f899
*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*