● Medium · CVSS 6.9

How to Fix CVE-2026-5575: SourceCodester/jkev Record Management System Login index.php sql injection

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

How to Fix CVE-2026-40291: Improper privilege management in chamilo-lms — Improper privilege management in chamilo-lms
How to Fix CVE-2026-34934: PraisonAI: Second-Order SQL Injection in get_all_user_threads — PraisonAI: Second-Order SQL Injection in get_all_user_threads
How to Fix CVE-2026-0865: Critical Vulnerability in CPython , Critical Vulnerability in CPython
How to Fix CVE-2026-3983: Cross Site Scripting , Cross Site Scripting
How to Fix CVE-2026-29123: Privilege escalation in SFX2100 Satellite Receiver , Privilege escalation in SFX2100 Satellite Receiver

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance


Severity	CVSS 6.9, Medium
Actively exploited?	No
Affected	Sourcecodester Record Management System (1.0); Jkev Record Management System (1.0)
Fixed in	See vendor advisory
Type (CWE)	CWE-89: SQL Injection

CVE-2026-5575 is a sourcecodester/jkev record management system login index.php sql injection in Sourcecodester Record Management System. The fix is to upgrade to see vendor advisory and apply the runnable commands below.

What is CVE-2026-5575?

A vulnerability was detected in SourceCodester/jkev Record Management System 1.0. Affected by this vulnerability is an unknown functionality of the file index.php of the component Login. The manipulation of the argument Username 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 Sourcecodester Record Management System at a version listed in the Affected row above. Probe your installed build with the commands below.


# Confirm the installed version via your package manager
dpkg -l | grep -i record   # Debian/Ubuntu
rpm -qa | grep -i record   # RHEL/CentOS/Rocky

How to fix CVE-2026-5575

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)


# Vendor advisory: https://vuldb.com/vuln/355345
sudo apt-get update
sudo apt-get install --only-upgrade record-management-system
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s record-management-system | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security record-management-system -y
rpm -q record-management-system

Windows (PowerShell, admin)


# Vendor advisory: https://vuldb.com/vuln/355345
winget upgrade --id 'Sourcecodester.RecordManagementSystem' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\RecordManagementSystem-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait

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


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

Write-Log "Starting CVE-2026-5575 remediation for Sourcecodester Record Management System"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*Record*' } |
    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\RecordManagementSystem-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Sourcecodester\Record Management System"
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\RecordManagementSystem-<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 '*Record*' } |
    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/355345
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/record-management-system-patch-cve-2026-5575.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-5575 remediation for Sourcecodester Record Management System"

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

# 2. Backup config
BACKUP=/var/backups/record-management-system-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/record-management-system /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 record-management-system
else
    sudo dnf upgrade --security -y record-management-system
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' record-management-system)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' record-management-system)
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 "record"   # Debian/Ubuntu
rpm -qa | grep -i "record"   # 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-5575 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.

Frequently asked questions

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

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 Record Management System 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-5575 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/355345
NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-5575
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://vuldb.com/vuln/355345/cti
Additional reference: https://vuldb.com/submit/783472
Additional reference: https://github.com/whatyourname12345/CVE/blob/main/PRMS/cve_SQL.md

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