How to Fix CVE-2026-5837: PHPGurukul News Portal Project news-details.php sql injection

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-5837 is a phpgurukul news portal project news-details.php sql injection in Phpgurukul News Portal Project. The fix is to upgrade to see vendor advisory and apply the runnable commands below.

What is CVE-2026-5837?

A vulnerability was found in PHPGurukul News Portal Project 4.1. This affects an unknown part of the file /news-details.php. The manipulation of the argument Comment results in sql injection.

In practical terms, a successful attacker gets SQL injection that can read or modify the backing database. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You are affected if you run Phpgurukul News Portal Project at a version listed in the Affected row above. Probe your installed build with the commands below.

php --version

How to fix CVE-2026-5837

The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu/Debian)

sudo apt-get update
sudo apt-get install --only-upgrade php php-cli php-fpm
sudo systemctl restart php*-fpm
php --version

PowerShell script (Windows): detect, back up, upgrade, verify, log

# Vendor advisory: https://vuldb.com/vuln/356293
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\NewsPortalProject-Patch-CVE-2026-5837.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-5837 remediation for Phpgurukul News Portal Project"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*News*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'<patched-version>') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\NewsPortalProject-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Phpgurukul\News Portal Project"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer
$installer = "$env:TEMP\NewsPortalProject-<patched-version>.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*News*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
    Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux): detect, back up, upgrade, verify, log

# Vendor advisory: https://vuldb.com/vuln/356293
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/news-portal-project-patch-cve-2026-5837.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-5837 remediation for Phpgurukul News Portal Project"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s news-portal-project >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' news-portal-project)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q news-portal-project >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' news-portal-project)
    PKG_MGR=dnf
else
    log "news-portal-project not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: news-portal-project=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/news-portal-project-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/news-portal-project /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y news-portal-project
else
    sudo dnf upgrade --security -y news-portal-project
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' news-portal-project)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' news-portal-project)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against <patched-version> and restart the affected service if needed."

If you cannot patch immediately

These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.

Block obvious SQL injection patterns with a WAF rule

# ModSecurity / OWASP CRS-style rule
SecRule ARGS "@rx (?i)(union(.|\n)+?select|select(.|\n)+?from|insert(.|\n)+?into)" \
  "id:900100,phase:2,deny,log,msg:'SQLi pattern blocked'"

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.

dpkg -l | grep -i "news"   # Debian/Ubuntu
rpm -qa | grep -i "news"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed the patched build.

Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-5837 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Related CVEs in the same advisory bundle

This advisory covers multiple CVE IDs. The same patched build closes every entry below:

• CVE-2026-5838
• CVE-2026-5839
• CVE-2026-5840

Frequently asked questions

Is CVE-2026-5837 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-5837?

CVSS rates it 6.9 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take News Portal Project offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-5837 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://vuldb.com/vuln/356293
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-5837
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://vuldb.com/vuln/356293/cti
• Additional reference: https://vuldb.com/submit/789775
• Additional reference: https://github.com/f1rstb100d/CVE/issues/25

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Sourced from the official vendor advisory, the NVD record, and the CISA KEV listing. Always confirm against the vendor advisory before applying changes in production.*