CVE-2025-5230
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 vulnerability classified as critical has been found in PHPGurukul Online Nurse Hiring System 1.0. This affects an unknown part of the file /admin/bwdates-report-details.php. The manipulation of the argument fromdate/todate leads to sql injection. It is possible to initiate 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 confidenceSQL injection vulnerability in PHPGurukul Online Nurse Hiring System 1.0 allows remote attackers to inject malicious SQL queries via the fromdate and todate parameters in /admin/bwdates-report-details.php. The lack of input sanitization or parameterized queries enables complete database compromise.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm PHPGurukul Online Nurse Hiring System is installedLocate the application files on the web server. Check for the presence of typical nurse hiring system files and directories.Affected if The application is running PHPGurukul Online Nurse Hiring System on the server.
-
Identify the installed versionCheck version files, README files, or the application admin panel for version information. Compare against the affected version 1.0.Affected if The installed version is exactly 1.0.
-
Verify the vulnerable script existsCheck if the file /admin/bwdates-report-details.php exists in the web root or admin directory.Affected if The file /admin/bwdates-report-details.php is present on the server.
-
Confirm admin access to the vulnerable endpointVerify the /admin/ directory is accessible and authentication is configured for admin access.Affected if The admin panel and bwdates-report-details.php endpoint are accessible without additional access controls.
-
Test for SQL injection in date parametersSubmit a request to /admin/bwdates-report-details.php with SQL syntax in the fromdate and todate parameters (such as a single quote) and observe the application response for SQL errors or unexpected behavior.Affected if The application returns database errors or exhibits unusual behavior when special characters are submitted in fromdate or todate parameters.
A user is affected if they are running PHPGurukul Online Nurse Hiring System version 1.0 with the /admin/bwdates-report-details.php script accessible and the application exhibits SQL error messages or unexpected behavior when malformed input is provided in the fromdate or todate parameters.
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 dataImplement prepared statements/parameterized queries for all SQL operations involving user input. Additionally, apply strict input validation on date parameters and consider deploying a WAF as a defensive layer.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5230 — 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-2025-5230 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