CVE-2025-60736
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 · uneditedcode-projects Online Medicine Guide 1.0 is vulnerable to SQL Injection in /login.php via the upass parameter.
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 the login page (/login.php) of Online Medicine Guide 1.0 in the 'upass' parameter. Attackers can inject malicious SQL queries to bypass authentication, extract sensitive data, or potentially execute commands on the underlying database system.
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 Online Medicine Guide version 1.0 is installedSearch the application files for version identifiers in source code comments, version files, or footer/about pages. Check if the application is the Anisha Online Medicine Guide.Affected if The installed version is exactly 1.0 (Anisha Online Medicine Guide)
-
Verify the login.php endpoint existsAccess the /login.php URL in the application to confirm the login page is present and accessible.Affected if The login.php file exists and handles user authentication
-
Inspect the upass parameter handling in login.phpOpen login.php and locate the code that processes the 'upass' parameter during login. Search for SQL queries that incorporate this parameter.Affected if The 'upass' parameter is used directly in SQL queries without prepared statements or parameter binding
-
Check for absence of parameterized queriesReview the database query code in login.php. Verify whether database calls use prepare() or parameterized methods, or if they concatenate the upass value directly into the SQL string.Affected if SQL queries related to authentication concatenate user input directly rather than using parameterized queries
-
Review database logs for suspicious authentication queriesCheck database logs for anomalous SQL patterns in authentication-related queries, especially those containing SQL operators, UNION statements, or unusual characters in the password field.Affected if Database logs show SQL injection patterns in login-related queries
If the application is Online Medicine Guide 1.0 and the login.php page uses direct string concatenation for the 'upass' parameter in SQL queries, the environment is affected by this SQL injection vulnerability.
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 database operations, especially authentication-related queries. Apply input validation and use least-privilege database accounts.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60736 — 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-60736 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