CVE-2018-7528
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 · uneditedAn SQL injection vulnerability has been identified in Geutebruck G-Cam/EFD-2250 Version 1.12.0.4 and Topline TopFD-2125 Version 3.15.1 IP cameras, which may allow an attacker to alter stored data.
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 Geutebruck G-Cam/EFD-2250 (v1.12.0.4) and Topline TopFD-2125 (v3.15.1) IP cameras allows remote attackers to inject malicious SQL statements through unsanitized input parameters, potentially enabling unauthorized data alteration in the camera's underlying database.
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.12.0.4= 3.15.1CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 camera modelAccess the camera's web interface or check the device label/sticker to confirm whether it is a Geutebruck G-Cam/EFD-2250 or Topline TopFD-2125 model.Affected if The model is not G-Cam/EFD-2250 or TopFD-2125, then this CVE does not apply.
-
Check the firmware versionLog into the camera's web management interface and navigate to the System or About section to view the firmware version. Alternatively, use the camera's API or SNMP to query the firmware version.Affected if The firmware version is exactly 1.12.0.4 for G-Cam/EFD-2250, or exactly 3.15.1 for TopFD-2125.
-
Verify web interface accessibilityDetermine if the camera's HTTP/HTTPS management interface is reachable from the network. Attempt to access the login page via the camera's IP address.Affected if The camera's web interface is exposed and accessible to network users.
-
Confirm SQL injection parameters existInspect the camera's web application parameters, particularly those handling user input such as login, search, or configuration fields, using a proxy to capture and analyze HTTP requests.Affected if The web interface accepts unsanitized user input that could be manipulated with SQL statements.
The camera is affected if it is a Geutebruck G-Cam/EFD-2250 running firmware 1.12.0.4 or a Topline TopFD-2125 running firmware 3.15.1, and its web management interface is accessible and processes user input without proper sanitization.
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 vendor firmware updates when available; if no update exists, implement web application firewall (WAF) rules or network segmentation to restrict access to camera management interfaces.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7528 — 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-2018-7528 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