● High · CVSS 8.1

How to Fix CVE-2026-28062: Improper control of filename for include/require statement in php program ('php remote file inclusion') in Happy Baby

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

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

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

The vendor advisory is at [https://patchstack.com/database/Wordpress/Theme/happy-baby/vulnerability/wordpress-happy-baby-theme-1-2-12-local-file-inclusion-vulnerability?_s_id=cve](https://patchstack.com/database/Wordpress/Theme/happy-baby/vulnerability/wordpress-happy-baby-theme-1-2-12-local-file-inclusion-vulnerability?_s_id=cve). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28062.

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

CVE-2026-28062 is a improper control of filename for include/require statement in php program ('php remote file inclusion') in ThemeREX Happy Baby. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	8.1 (High)
Actively exploited?	No public listing in CISA KEV
Affected	Happy Baby 0 to <=1.2.12
Fixed in	See vendor advisory
Type (CWE)	CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

What is CVE-2026-28062?

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeREX Happy Baby happy-baby allows PHP Local File Inclusion.This issue affects Happy Baby: from n/a through <= 1.2.12. The CVSS base score is 8.1 (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/Theme/happy-baby/vulnerability/wordpress-happy-baby-theme-1-2-12-local-file-inclusion-vulnerability?_s_id=cve.

Am I affected?

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

Run the version check that fits your platform:


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


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

How to fix CVE-2026-28062

Upgrade Happy Baby 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 happy-baby
dpkg -s happy-baby | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update happy-baby
rpm -q happy-baby

Node.js / npm


# Update the affected package in your project
npm install Happy Baby@latest
npm ls Happy Baby
npm audit fix

PHP / Composer


composer update themerex/happy-baby 2>/dev/null || composer update
composer show | head -20

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-28062 affecting Happy Baby
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

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

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

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

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

Disable the affected service (Linux)


sudo systemctl stop happy-baby 2>/dev/null || true
sudo systemctl disable happy-baby 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 happy-baby 2>/dev/null | grep -i ^Version
rpm -q happy-baby 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 "*Happy Baby*" | 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-6206: Insecure Direct Object Reference in MW WP Form — Insecure Direct Object Reference in MW WP Form
How to Fix CVE-2026-7322: Memory safety bugs fixed in Firefox — Memory safety bugs fixed in Firefox
How to Fix CVE-2026-22548: Critical Vulnerability in BIG-IP , Critical Vulnerability in BIG-IP
How to Fix CVE-2026-4331: Critical Vulnerability in Blog2Social: Social Media Auto Post & Scheduler , Critical Vulnerability in Blog2Social: Social Media Auto Post & Scheduler
How to Fix CVE-2026-7262: NULL pointer dereference in PHP , NULL pointer dereference in PHP

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

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

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

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

The vendor advisory is at https://patchstack.com/database/Wordpress/Theme/happy-baby/vulnerability/wordpress-happy-baby-theme-1-2-12-local-file-inclusion-vulnerability?_s_id=cve. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28062.

References

Official vendor advisory: https://patchstack.com/database/Wordpress/Theme/happy-baby/vulnerability/wordpress-happy-baby-theme-1-2-12-local-file-inclusion-vulnerability?_s_id=cve
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28062
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.*