CVE-2025-30184
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 · uneditedCyberData 011209 Intercom could allow an unauthenticated user access to the Web Interface through an alternate path.
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 confidenceThe CyberData 011209 Intercom contains an authentication bypass vulnerability in its web interface. An unauthenticated attacker can access the administrative web interface through an alternate path or method that bypasses the normal authentication mechanisms, potentially granting full administrative access to the device.
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< 22.0.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
- 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.
-
Confirm the device modelIdentify the exact model number of the CyberData intercom device on the network or physically on the device label. Verify it is specifically the 011209 Sip Emergency Intercom model.Affected if The device is NOT a CyberData 011209 Sip Emergency Intercom, then this CVE does not apply.
-
Determine the installed firmware versionAccess the device's web interface or check the device documentation to find the firmware version. This is typically displayed in the web admin panel under a System, Status, or About section, or may be obtainable via SNMP or the device's management interface.Affected if The firmware version is 22.0.1 or higher, the device is NOT affected by this vulnerability. If the version cannot be determined or is below 22.0.1, proceed to the next check.
-
Verify the web interface is accessibleAttempt to reach the device's HTTP or HTTPS web interface from a network location. Confirm whether port 80, 443, or the device's default web ports are responding.Affected if The web administrative interface is NOT accessible from the network being tested, the device may have limited exposure but the vulnerability could still exist if the interface is reachable through other means.
-
Test for unauthenticated administrative accessWith the web interface reachable, attempt to access administrative pages or endpoints directly without providing credentials. Look for URLs or paths that grant access to configuration, status, or control panels without a login prompt.Affected if Administrative pages or device configuration can be accessed WITHOUT authentication, the device IS affected by this authentication bypass vulnerability.
The device is affected if it is a CyberData 011209 Sip Emergency Intercom with firmware version below 22.0.1 and its web administrative interface is network-accessible, allowing unauthenticated entry to admin functions.
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.
dbcve · scoped22.0.1
Restrict network access to the intercom device's management interface using firewall rules or network segmentation. If available, apply vendor firmware updates. Consider disabling the web interface if not required and implement IP-based access controls.
22.0.1
- Obtain the firmware version 22.0.1 or later from CyberData's official support channels
- Follow CyberData's standard firmware upgrade procedure for the 011209 Intercom device
- Verify the upgrade was successful and the firmware version is 22.0.1 or later
- Confirm the web interface now requires authentication
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-30184 — 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-30184 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