● Medium · CVSS 5.1

How to Fix CVE-2026-24350: Cross-site scripting in PluXml CMS

Q: Is CVE-2026-24350 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.

Q: Do I need to reboot after patching CVE-2026-24350?

For kernel and OS-level updates, yes. For most userland packages a `systemctl restart ` 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.

Q: What is the CVSS score for CVE-2026-24350?

5.1 (Medium). Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`.

Q: Where is the official advisory for CVE-2026-24350?

The vendor advisory is at [https://pluxml.org/](https://pluxml.org/). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-24350.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-24350 is a cross-site scripting in PluXml PluXml CMS. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	5.1 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	PluXml CMS 5.9.0-rc7; PluXml CMS 5.8.21
Fixed in	See vendor advisory
Type (CWE)	CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting')

What is CVE-2026-24350?

PluXml CMS is vulnerable to Stored XSS in file uploading functionality. An authenticated attacker can upload an SVG file containing a malicious payload, which will be executed when a victim clicks the link associated with the uploaded image.

In version 5.9.0-rc7 clicking the link associated with the uploaded image doesn't execute malicious code but directly accessing the file will still execute the embedded payload.

The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only versions 5.8.21 and 5.9.0-rc7 were tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable. The CVSS base score is 5.1 (Medium). The official advisory is at https://pluxml.org/.

Am I affected?

Check the version of PluXml CMS you are running and compare it against the Affected row above (PluXml CMS 5.9.0-rc7; PluXml CMS 5.8.21). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s pluxml-cms 2>/dev/null | grep -i ^Version
rpm -q pluxml-cms 2>/dev/null
command -v pluxml-cms >/dev/null && pluxml-cms --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*PluXml CMS*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "PluXml CMS" 2>$null

How to fix CVE-2026-24350

Upgrade PluXml CMS 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 pluxml-cms
dpkg -s pluxml-cms | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh pluxml-cms -y
# or for older releases:
sudo yum update pluxml-cms -y
rpm -q pluxml-cms

SUSE / openSUSE


sudo zypper refresh
sudo zypper update pluxml-cms
rpm -q pluxml-cms

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-24350 affecting PluXml CMS
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-24350-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 "*PluXml CMS*" -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\pluxml-cms-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\PluXml CMS" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "PluXml CMS" --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 "PluXml CMS"
    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-24350 affecting PluXml CMS
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-24350-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 pluxml-cms 2>/dev/null | grep -i ^Version || echo "pluxml-cms not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q pluxml-cms || echo "pluxml-cms not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-24350-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/pluxml-cms /etc/pluxml-cms.d /etc/pluxml-cms.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 pluxml-cms
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y pluxml-cms
elif command -v yum >/dev/null; then
    yum update -y pluxml-cms
elif command -v zypper >/dev/null; then
    zypper --non-interactive update pluxml-cms
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s pluxml-cms 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q pluxml-cms
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-24350" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-24350"

Disable the affected service (Linux)


sudo systemctl stop pluxml-cms 2>/dev/null || true
sudo systemctl disable pluxml-cms 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 pluxml-cms 2>/dev/null | grep -i ^Version
rpm -q pluxml-cms 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 "*PluXml CMS*" | 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

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-28479: Broken cryptography in OpenClaw — Broken cryptography in OpenClaw
How to Fix CVE-2026-8276: Integer Coercion Error in bettercap — Integer Coercion Error in bettercap
How to Fix CVE-2026-3300: Everest Forms Pro <= 1.9.12 - Unauthenticated Remote Code Execution via Calculation Field , Everest Forms Pro <= 1.9.12 - Unauthenticated Remote Code Execution via Calculation Field
How to Fix CVE-2026-7079: Buffer Overflow in F456 , Buffer Overflow in F456
How to Fix CVE-2026-35053: oneuptime (Bundle Sibling) , oneuptime (Bundle Sibling)

Is CVE-2026-24350 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-24350?

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-24350?

5.1 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N.

Where is the official advisory for CVE-2026-24350?

The vendor advisory is at https://pluxml.org/. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-24350.

References

Official vendor advisory: https://pluxml.org/
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24350
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://cert.pl/posts/2026/03/CVE-2026-24350

*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.*