CVE-2026-5813
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA weakness has been identified in PHPGurukul Online Course Registration 3.1. This vulnerability affects unknown code of the file /check_availability.php. Executing a manipulation of the argument cid can lead to sql injection. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in PHPGurukul Online Course Registration 3.1's /check_availability.php file. The 'cid' parameter accepts user input that is directly concatenated into SQL queries without proper sanitization or parameterized statements, allowing attackers to manipulate database queries and potentially extract, modify, or delete data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm PHPGurukul Online Course Registration is installedLocate the application web root directory and verify the presence of the Online Course Registration PHP application filesAffected if The application is present in the web server's document root or a subdirectory
-
Identify the installed versionCheck for a version file, README, or any file containing '3.1' as the version number within the application directoryAffected if The installed version matches 3.1 exactly
-
Locate check_availability.phpFind the check_availability.php file within the application directory structure, typically in the root or an include folderAffected if The file check_availability.php exists in the application
-
Verify the cid parameter is used unsanitizedOpen check_availability.php and inspect the code for any SQL queries that incorporate the 'cid' parameter directly without using prepared statements, parameter binding, or input sanitization functions like mysqli_real_escape_string or htmlspecialcharsAffected if The code shows the 'cid' parameter is used directly in SQL queries without prepared statements or escaping functions
-
Confirm the file is web-accessibleAttempt to access check_availability.php via HTTP/HTTPS request to the server or verify the file is within a publicly accessible web directoryAffected if The file can be reached via web request, allowing an attacker to send malicious input
A defender is affected if PHPGurukul Online Course Registration version 3.1 is installed, check_availability.php exists and is web-accessible, and the 'cid' parameter is processed in SQL queries without prepared statements or input sanitization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace direct SQL query construction with prepared statements/parameterized queries in check_availability.php, perform input validation on the cid parameter, and conduct a broader security audit of the application for similar injection flaws.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5813 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5813 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data