How to Fix CVE-2026-22351: Missing authorization in WP FullCalendar

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

CVE-2026-22351 is a missing authorization in Marcus (aka @msykes) WP FullCalendar. The fix is to apply the vendor patch noted below.

What is CVE-2026-22351?

Missing Authorization vulnerability in Marcus (aka @msykes) WP FullCalendar wp-fullcalendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP FullCalendar: from n/a through <= 1.6. The CVSS base score is 7.5 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://patchstack.com/database/Wordpress/Plugin/wp-fullcalendar/vulnerability/wordpress-wp-fullcalendar-plugin-1-6-broken-access-control-vulnerability?_s_id=cve.

Am I affected?

Check the version of WP FullCalendar you are running and compare it against the Affected row above (WP FullCalendar 0 to <=1.6). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

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

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

How to fix CVE-2026-22351

Upgrade WP FullCalendar 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 wp-fullcalendar
dpkg -s wp-fullcalendar | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

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

SUSE / openSUSE

sudo zypper refresh
sudo zypper update wp-fullcalendar
rpm -q wp-fullcalendar

Node.js / npm

# Update the affected package in your project
npm install WP FullCalendar@latest
npm ls WP FullCalendar
npm audit fix

WordPress

# Update via WP-CLI
wp plugin update --all
wp core update

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-22351 affecting WP FullCalendar
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

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

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

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

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

Disable the affected service (Linux)

sudo systemctl stop wp-fullcalendar 2>/dev/null || true
sudo systemctl disable wp-fullcalendar 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 wp-fullcalendar 2>/dev/null | grep -i ^Version
rpm -q wp-fullcalendar 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 "*WP FullCalendar*" | 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-5630: gpt-researcher (Bundle Sibling) — gpt-researcher (Bundle Sibling)
• How to Fix CVE-2026-1731: OS Command Injection in Remote Support(RS) & Privileged Remote Access(PRA) — OS Command Injection in Remote Support(RS) & Privileged Remote Access(PRA)
• How to Fix CVE-2026-1343: Verify Identity Access Container (Bundle Sibling) , Verify Identity Access Container (Bundle Sibling)
• How to Fix CVE-2026-6604: Server-side request forgery in agentscope , Server-side request forgery in agentscope
• How to Fix CVE-2026-8425: Cross-Site Request Forgery in Notify Odoo , Cross-Site Request Forgery in Notify Odoo

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

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

7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

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

The vendor advisory is at https://patchstack.com/database/Wordpress/Plugin/wp-fullcalendar/vulnerability/wordpress-wp-fullcalendar-plugin-1-6-broken-access-control-vulnerability?_s_id=cve. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-22351.

References

• Official vendor advisory: https://patchstack.com/database/Wordpress/Plugin/wp-fullcalendar/vulnerability/wordpress-wp-fullcalendar-plugin-1-6-broken-access-control-vulnerability?_s_id=cve
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22351
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

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