CVE-2025-14192
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 was found in RashminDungrani online-banking up to 2337ad552ea9d385b4e07b90e6f32d011b7c68a2. This affects an unknown part of the file /site/dist/auth_login.php. Performing manipulation of the argument Username results in sql injection. The attack can be initiated remotely. The exploit has been made public and could be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.
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 form (auth_login.php) allows remote attackers to manipulate the Username parameter to inject arbitrary SQL queries, potentially bypassing authentication or exfiltrating database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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.
-
Locate the login scriptSearch the web root directory for the file auth_login.php. Common paths include /auth/, /includes/, or the application root.Affected if The file auth_login.php exists in the deployment
-
Inspect SQL query constructionOpen auth_login.php and examine how the Username parameter from the login form is used in SQL queries. Look for patterns like: $sql = "SELECT * FROM users WHERE username = '" . $_POST['username'] . "'" or similar string concatenation/interpolation.Affected if The code builds SQL queries by directly concatenating or interpolating the username parameter without using prepared statements
-
Verify parameter binding is absentSearch the auth_login.php file for prepare(), bindParam(), bindValue(), or $stmt->prepare(). If these are absent from the login query logic, the vulnerability is present.Affected if No prepared statement or parameter binding is used for the login query
-
Confirm database connectivityCheck if the application connects to a SQL database (MySQL, PostgreSQL, SQL Server, SQLite, etc.) and the login function queries user credentials from that database.Affected if The login function queries a database using the vulnerable SQL construction
-
Assess accessibilityDetermine if the login form at auth_login.php is accessible over the network (HTTP/HTTPS) to remote attackers.Affected if The login form is exposed and reachable remotely
If auth_login.php exists, uses direct string concatenation for the username parameter in SQL queries without prepared statements, and the login form is network-accessible, the environment is vulnerable to CVE-2025-14192.
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 dataReplace dynamic SQL queries in auth_login.php with parameterized queries/prepared statements to neutralize the injection vector; audit other files for similar SQL injection patterns.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2025-14192 — 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-14192 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