dbcve.org
Directory Management SystemApplication · Phpgurukul

CVE-2025-6330

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-20
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 vulnerability classified as critical has been found in PHPGurukul Directory Management System 1.0. Affected is an unknown function of the file /searchdata.php. The manipulation of the argument searchdata 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

A critical SQL injection vulnerability exists in PHPGurukul Directory Management System 1.0 at the /searchdata.php endpoint. The 'searchdata' parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in searchdata.php and implement proper input validation for all user-supplied parameters.

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
Directory Management SystemApplication
Affected:= 1.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. Verify PHPGurukul Directory Management System is installed
    Check for the presence of the application by looking for typical installation paths such as /var/www/html/, /www/, or C:\inetpub\wwwroot\. Look for directories containing PHPGurukul-related files or the file searchdata.php directly.
    Affected if The application files including searchdata.php exist on the server.
  2. Confirm the installed version is 1.0
    Locate version information in the application. Check for a README, version file, or footer/header in the application that displays the version number. Common locations include README.txt, version.php, or the main index page footer.
    Affected if The installed version is identified as 1.0.
  3. Verify searchdata.php exists and is accessible
    Check if the file searchdata.php exists in the web root or a subdirectory. Attempt to access it via HTTP request to the /searchdata.php endpoint to confirm it is reachable.
    Affected if searchdata.php is present and responds to HTTP requests.
  4. Inspect the searchdata.php source code for SQL injection vulnerability
    Open searchdata.php in a text editor or via command line. Search for occurrences of the 'searchdata' parameter being used in SQL queries. Look for patterns where $_GET['searchdata'] or $_POST['searchdata'] is directly concatenated into SQL queries without using prepared statements, parameterized queries, or sanitization functions such as mysqli_real_escape_string or htmlspecialchars.
    Affected if The code shows the 'searchdata' parameter being directly inserted into SQL queries without sanitization or prepared statements.
  5. Confirm the search functionality is enabled
    Test the searchdata.php functionality by submitting a search request via the 'searchdata' parameter (e.g., GET or POST request to searchdata.php?searchdata=test). Verify the application accepts and processes this parameter.
    Affected if The searchdata parameter is accepted and processed by the application, indicating the vulnerable code path is active.

You are affected if PHPGurukul Directory Management System version 1.0 is installed, searchdata.php exists, and the source code reveals the 'searchdata' parameter is used in SQL queries without sanitization or prepared statements.

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 parameterized queries/prepared statements in searchdata.php and implement proper input validation for all user-supplied parameters.

Fix this in Directory Management System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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