How to Fix CVE-2026-2897: Cross-site scripting in funadmin
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-2897 is a cross-site scripting in n/a funadmin. The fix is to apply the vendor patch noted below.
| Severity | 4.8 (Medium) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | funadmin 7.1.0-rc1; funadmin 7.1.0-rc2; funadmin 7.1.0-rc3; funadmin 7.1.0-rc4 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-79: Cross Site Scripting |
What is CVE-2026-2897?
A security vulnerability has been detected in funadmin up to 7.1.0-rc4. This vulnerability affects unknown code of the file app/backend/view/index/index.html of the component Backend Interface. The manipulation of the argument Value leads to cross site scripting. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way. The CVSS base score is 4.8 (Medium). The official advisory is at https://vuldb.com/?id.347208.
Am I affected?
Check the version of funadmin you are running and compare it against the Affected row above (funadmin 7.1.0-rc1; funadmin 7.1.0-rc2; funadmin 7.1.0-rc3; funadmin 7.1.0-rc4). If your build sits inside the affected range, you must patch.
Run the version check that fits your platform:
# Linux package check
dpkg -s funadmin 2>/dev/null | grep -i ^Version
rpm -q funadmin 2>/dev/null
command -v funadmin >/dev/null && funadmin --version 2>/dev/null
# Windows (PowerShell)
Get-Package -Name "*funadmin*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "funadmin" 2>$null
How to fix CVE-2026-2897
Upgrade funadmin to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade funadmin
dpkg -s funadmin | grep -i ^Version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --refresh funadmin -y
# or for older releases:
sudo yum update funadmin -y
rpm -q funadmin
SUSE / openSUSE
sudo zypper refresh
sudo zypper update funadmin
rpm -q funadmin
Node.js / npm
# Update the affected package in your project
npm install funadmin@latest
npm ls funadmin
npm audit fix
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-2897 affecting funadmin
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-2897-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] Detect installed version"
$pkg = Get-Package -Name "*funadmin*" -ErrorAction SilentlyContinue
if ($pkg) { $pkg | Format-Table Name, Version }
else { Write-Host "Not detected via Get-Package; try winget list" }
Write-Host "[2/4] Backup configuration"
$backup = "C:\Backup\funadmin-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\funadmin" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Apply the upgrade to See vendor advisory"
winget upgrade --name "funadmin" --silent --accept-source-agreements --accept-package-agreements
if ($LASTEXITCODE -ne 0) {
# Fallback: pull latest via OS update channel
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verify the patched build"
winget list --name "funadmin"
Write-Host "Patch 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-2897 affecting funadmin
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-2897-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
dpkg -s funadmin 2>/dev/null | grep -i ^Version || echo "funadmin not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q funadmin || echo "funadmin not installed via rpm"
fi
echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-2897-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/funadmin /etc/funadmin.d /etc/funadmin.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y funadmin
elif command -v dnf >/dev/null; then
dnf upgrade --refresh -y funadmin
elif command -v yum >/dev/null; then
yum update -y funadmin
elif command -v zypper >/dev/null; then
zypper --non-interactive update funadmin
fi
echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
dpkg -s funadmin 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
rpm -q funadmin
fi
echo "Done. Restart any service that loaded the old library."
If you can't patch immediately
Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.
Restrict exposure with nftables (Linux)
# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Block at the host firewall (Windows)
New-NetFirewallRule -DisplayName "Block-CVE-2026-2897" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-2897"
Disable the affected service (Linux)
sudo systemctl stop funadmin 2>/dev/null || true
sudo systemctl disable funadmin 2>/dev/null || true
If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.
How to verify the fix worked
After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.
# Linux
dpkg -s funadmin 2>/dev/null | grep -i ^Version
rpm -q funadmin 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true
# Windows
Get-Package -Name "*funadmin*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-31027: n/a (Bundle Sibling) — n/a (Bundle Sibling)
- How to Fix CVE-2026-27948: Cross-site scripting in copyparty — Cross-site scripting in copyparty
- How to Fix CVE-2026-42924: Command Injection in BIG-IP , Command Injection in BIG-IP
- How to Fix CVE-2026-26056: Code Injection RCE in yoke , Code Injection RCE in yoke
- How to Fix CVE-2026-34838: CWE-502: Deserialization of Untrusted Data in groupoffice , CWE-502: Deserialization of Untrusted Data in groupoffice
Is CVE-2026-2897 actively exploited?
There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.
Do I need to reboot after patching CVE-2026-2897?
For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.
What is the CVSS score for CVE-2026-2897?
4.8 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P.
Where is the official advisory for CVE-2026-2897?
The vendor advisory is at https://vuldb.com/?id.347208. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-2897.
References
- Official vendor advisory: https://vuldb.com/?id.347208
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2897
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://vuldb.com/?ctiid.347208
- Additional reference: https://vuldb.com/?submit.753975
- Additional reference: https://github.com/I4m6da/CVE/issues/4
*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.*