CVE-2024-57238
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 · uneditedProlink 4G LTE Mobile Wi-Fi DL-7203E V4.0.0B05 is vulnerable to SQL Injection in in the /reqproc/proc_get endpoint. The vulnerability allows an attacker to manipulate SQL queries by injecting malicious SQL code into the order_by 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 · moderate confidenceSQL injection vulnerability in Prolink 4G LTE Mobile Wi-Fi DL-7203E V4.0.0B05 allows remote attackers to inject malicious SQL code through the order_by parameter in the /reqproc/proc_get endpoint, potentially enabling unauthorized database access or data exfiltration.
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.
-
Identify the device modelAccess the web management interface or check the device label for the model number DL-7203EAffected if The device is a Prolink 4G LTE Mobile Wi-Fi DL-7203E
-
Determine the firmware versionLog into the web interface and navigate to the status or system settings page to view the firmware version, typically displayed as V4.0.0B05 or similarAffected if The firmware version is V4.0.0B05 or falls within the affected version range
-
Confirm web interface accessibilityAttempt to access the device login page via HTTP on the default gateway IP (commonly 192.168.1.1 or 192.168.0.1)Affected if The web management interface is reachable on the local network
-
Test the vulnerable endpointSend a GET request to /reqproc/proc_get with the order_by parameter, for example: GET /reqproc/proc_get?order_by=1' OR '1'='1Affected if The endpoint responds without proper error handling or returns unexpected database-related errors
-
Inspect for SQL injection indicatorsObserve the HTTP response for SQL error messages, unusual database output, or changes in expected behavior when injecting SQL syntax into the order_by parameterAffected if SQL syntax produces database errors, unexpected data, or the application fails to sanitize the order_by input
If the device is a Prolink DL-7203E running firmware V4.0.0B05 with an accessible web interface, and the /reqproc/proc_get endpoint accepts unsanitized input in the order_by parameter, the environment is affected by CVE-2024-57238.
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 dataApply available firmware updates from Prolink; if unavailable, implement input validation and use parameterized queries for the order_by parameter in the affected web application code.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57238 — 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-2024-57238 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