dbcve.org
Online Course RegistrationApplication · Phpgurukul

CVE-2025-9307

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A flaw has been found in PHPGurukul Online Course Registration 3.1. This affects an unknown function of the file /admin/session.php. This manipulation of the argument sesssion causes sql injection. The attack can be initiated remotely. The exploit has been published and may be used.

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 · high confidence

SQL injection vulnerability in PHPGurukul Online Course Registration 3.1 allows remote attackers to inject malicious SQL queries via the 'sesssion' parameter in /admin/session.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.

MitigationReplace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation on the 'sesssion' parameter. Additionally, ensure the admin page has proper authentication and authorization controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Online Course RegistrationApplication
Affected:= 3.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the PHPGurukul Online Course Registration installation
    Locate the web application directory on the server. Common paths include /var/www/html/, /www/, or the document root configured in the web server. Look for files such as index.php, admin/index.php, or session.php.
    Affected if The application directory contains PHPGurukul Online Course Registration files.
  2. Confirm the installed version is 3.1
    Check for a version file, README, or version information in the source code. Often version details are found in files like version.php, about.php, or in comments within PHP files. Compare the version number to the affected range.
    Affected if The installed version is exactly 3.1.
  3. Locate the affected session.php file in the admin directory
    Navigate to the /admin/ subdirectory within the application root and verify the presence of session.php. This file handles the 'sesssion' parameter that is vulnerable to SQL injection.
    Affected if The file /admin/session.php exists in the application.
  4. Verify the application has an accessible admin interface
    Attempt to access the admin login page or session.php directly via HTTP/HTTPS. Check if authentication is required or if the endpoint is exposed without proper access controls.
    Affected if The /admin/session.php endpoint is accessible without authentication or with weak authorization.
  5. Inspect the session.php code for the vulnerable parameter
    Examine the source code of admin/session.php and locate the usage of the 'sesssion' parameter (note the double 's'). Check if the parameter is directly used in SQL queries without prepared statements, parameter binding, or input sanitization.
    Affected if The 'sesssion' parameter is used in dynamic SQL queries without parameterized queries or sanitization functions.

A user is affected if they are running PHPGurukul Online Course Registration version 3.1 with the /admin/session.php file accessible and the 'sesssion' parameter used in unsanitized SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with prepared statements/parameterized queries and implement proper input validation on the 'sesssion' parameter. Additionally, ensure the admin page has proper authentication and authorization controls.

Fix this in Online Course Registration Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9307 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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