dbcve.org
Student Result Management SystemApplication · Phpgurukul

CVE-2025-7534

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-13
Fix available
A fix is available. Upgrade to after 2.0 or later.
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 vulnerability was found in PHPGurukul Student Result Management System 2.0. It has been classified as critical. Affected is an unknown function of the file /notice-details.php of the component GET Parameter Handler. The manipulation of the argument nid leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public 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 Student Result Management System 2.0 allows remote attackers to execute arbitrary SQL commands via the unsanitized 'nid' GET parameter in /notice-details.php. The attack requires no authentication and can be exploited remotely using the publicly available exploit.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements to properly sanitize the nid parameter. Apply input validation and ensure the database user follows least-privilege principles.

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
Student Result Management SystemApplication
Affected:<= 2.0

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. Confirm PHPGurukul Student Result Management System is installed
    Locate the application web root directory and check for files indicating this specific product (e.g., index.php, notice-details.php, or other Phpgurukul-specific files). If using a package manager or CMS, check the installed software inventory.
    Affected if The application directory contains PHPGurukul Student Result Management System files.
  2. Check if notice-details.php exists
    Navigate to the web root and verify the presence of /notice-details.php file. This is the vulnerable script.
    Affected if The file /notice-details.php exists in the web application directory.
  3. Identify the installed version
    Check version information in the application (common locations: footer files, about page, changelog file, version constant in config files, or README file in the web root). Compare the version number against the affected range: <= 2.0.
    Affected if The installed version is 2.0 or any version lower than 2.0.
  4. Verify the vulnerable parameter is accessible
    Confirm the application is accessible over HTTP/HTTPS and the endpoint /notice-details.php is reachable. The vulnerability exists in the 'nid' GET parameter.
    Affected if The application is live and /notice-details.php is accessible without authentication.
  5. Confirm database interaction on the notice-details page
    Access /notice-details.php in a browser and observe whether the page displays notice content from the database based on the 'nid' parameter. If the page loads content from the database using this parameter, the SQL injection point is present.
    Affected if The page retrieves and displays notice data from the database using the 'nid' parameter.

The environment is affected if PHPGurukul Student Result Management System version 2.0 or lower is installed and the notice-details.php file is accessible, as the unsanitized 'nid' parameter in that file allows SQL injection without authentication.

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
Upgrade available Upgrade to a release after 2.0
Interim mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements to properly sanitize the nid parameter. Apply input validation and ensure the database user follows least-privilege principles.

Fix this in Student Result Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7534 — 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-7534 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