CVE-2025-62173
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## Summary Authenticated SQL Injection Vulnerability in Endpoint Module Rest API
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 · moderate confidenceThis is an authenticated SQL injection vulnerability in the REST API endpoint module. An attacker with valid credentials can inject malicious SQL queries through API parameters, potentially allowing data exfiltration, modification, or database compromise.
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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify REST API endpoint module deploymentLocate the REST API endpoint module in your environment by searching for API-related services, endpoints, or web application modules that handle REST requestsAffected if The REST API endpoint module is deployed and accessible in your environment
-
Determine installed software versionQuery your package manager, software inventory, or application metadata to find the version of the software containing the REST API endpoint moduleAffected if The installed version falls within any affected version range for this vulnerability (compare your version to known affected releases)
-
Verify API authentication is configuredReview API configuration files, authentication settings, and access control policies to confirm whether user authentication is required for the vulnerable endpointAffected if Authentication is enabled but relies on user-supplied credentials that could be exploited for SQL injection
-
Inspect API parameter handlingExamine the API endpoint code or configuration to identify parameters that accept user input and are passed to database queries without proper sanitizationAffected if User-controllable parameters are passed directly to database operations without parameterized query handling
-
Review database query implementationAnalyze the endpoint module's database interaction code to check if queries use parameterized statements or prepared statements vs string concatenationAffected if Database queries are constructed using string concatenation or dynamic SQL with user input
Your environment is affected if the REST API endpoint module is deployed with a vulnerable version and accepts user input in API parameters that are not handled via parameterized queries.
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 parameterized queries or prepared statements for all database operations in the endpoint module API. Apply strict input validation and principle of least privilege for database accounts used by the API.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62173 — 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-62173 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