CVE-2025-63667
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 · uneditedIncorrect access control in SIMICAM v1.16.41-20250725, KEVIEW v1.14.92-20241120, ASECAM v1.14.10-20240725 allows attackers to access sensitive API endpoints without authentication.
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 vulnerability allows unauthenticated attackers to access sensitive API endpoints in SIMICAM, KEVIEW, and ASECAM camera management software due to incorrect access control. The CVSS 7.5 score indicates high severity, likely due to exposed sensitive operations or data without requiring authentication.
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.16.41= 1.14.92= 1.14.10CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 camera firmware versionAccess the camera web interface or use the manufacturer's discovery tool to retrieve the firmware version. For web interface, log in and navigate to Settings > System > Firmware or About page. For command line, use ONVIF or manufacturer-specific SDK tools like gSOAP or the camera's API (e.g., GET /cgi-bin/login.cgi?action=getSystemInfo).Affected if The installed firmware version is exactly 1.16.41 (Simicam), 1.14.92 (Keview), or 1.14.10 (Asecam).
-
Confirm product identificationVerify the camera model and brand name matches Simicam, Keview, or Asecam. Check the device info page on the web interface or query the device via ONVIF (GetDeviceInformation request).Affected if The product is identified as Simicam, Keview, or Asecam IP camera.
-
Test API endpoint authenticationSend unauthenticated HTTP requests to common API endpoints such as /api/, /cgi-bin/, /sdk/, or /webs/ without providing any login credentials or session cookies. Use curl: curl -s http://<camera-ip>/cgi-bin/config.cgi?action=getConfig or similar endpoints. Check if the response returns sensitive data (device info, user list, configuration) instead of an HTTP 401/403 error.Affected if API endpoints return sensitive data or functional responses without requiring authentication (HTTP 200 OK with data instead of 401/403).
You are affected if your camera runs Simicam firmware 1.16.41, Keview firmware 1.14.92, or Asecam firmware 1.14.10, and API endpoints are accessible without authentication.
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 proper authentication and authorization checks on all API endpoints, particularly sensitive endpoints, and validate user sessions before granting access to protected resources.
- 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-2025-63667 — 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-63667 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