CVE-2025-12463
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 unauthenticated SQL Injection was discovered within the Geutebruck G-Cam E-Series Cameras through the `Group` parameter in the `/uapi-cgi/viewer/Param.cgi` script. This has been confirmed on the EFD-2130 camera running firmware version 1.12.0.19.
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 confidenceAn unauthenticated SQL injection vulnerability exists in the /uapi-cgi/viewer/Param.cgi script of Geutebruck G-Cam E-Series Cameras. The vulnerability is located in the 'Group' parameter, allowing remote attackers to execute arbitrary SQL commands without authentication. This has been confirmed on EFD-2130 cameras running firmware version 1.12.0.19.
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
- 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.
-
Identify the device modelDetermine if the target device is a Geutebruck G-Cam E-Series camera, specifically the EFD-2130 model or other E-Series variants. Check device web interface, SNMP, or manufacturer documentation.Affected if The device is a Geutebruck G-Cam E-Series or EFD-2130 camera.
-
Check the firmware versionAccess the camera web interface or use the vendor's API to retrieve the firmware version. Compare the installed version against the known affected version 1.12.0.19.Affected if The firmware version is 1.12.0.19 or earlier on E-Series models.
-
Verify the vulnerable CGI script is presentAttempt to access the /uapi-cgi/viewer/Param.cgi endpoint on the target device using HTTP/HTTPS to confirm the script exists and is reachable.Affected if The /uapi-cgi/viewer/Param.cgi endpoint responds to requests.
-
Check if the Group parameter accepts SQL injectionSend a crafted HTTP request to /uapi-cgi/viewer/Param.cgi with a SQL injection payload in the 'Group' parameter (e.g., Group=1' OR '1'='1) and observe if the application returns SQL error messages or behaves differently than expected.Affected if The application returns database errors, unexpected data, or exhibits time delays consistent with SQL injection when the Group parameter contains SQL syntax.
A user is affected if they have a Geutebruck G-Cam E-Series camera (particularly EFD-2130) running firmware version 1.12.0.19 or earlier, with the /uapi-cgi/viewer/Param.cgi script accessible and the Group parameter vulnerable to SQL injection.
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; until then, isolate affected devices on a restricted network segment and consider deploying WAF rules to filter malicious SQL injection payloads targeting the affected endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12463 — 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-12463 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