VulnerabilityPublished 9 Jun 2025

CVE-2025-30183: CyberData 011209 SIP Emergency Intercom · CWE-522

Affects CyberData 011209 SIP Emergency IntercomSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CyberData 011209 SIP Emergency Intercom	Affected =0	Fixed in–

AI-suggested

To mitigate this vulnerability, European organizations should immediately assess their deployment of CyberData 011209 SIP Emergency Intercom devices. Specific recommendations include: 1) Isolate the intercom devices on segmented, secured network zones with strict access controls to limit exposure to untrusted networks. 2) Implement network-level protections such as firewalls and intrusion detection systems to monitor and restrict access to the device's web interface. 3) If possible, disable web administration interfaces or restrict them to trusted IP addresses only. 4) Change default credentials and use strong, unique passwords for admin accounts, even though the vulnerability relates to credential storage, this reduces risk from other attack vectors. 5) Monitor vendor communications closely for patches or firmware updates addressing this vulnerability and apply them promptly once available. 6) Conduct regular security audits and penetration testing focused on these devices to detect unauthorized access attempts. 7) Consider deploying compensating controls such as VPN access for administrative functions to add an additional authentication layer. 8) Document and train relevant personnel on the risks and response procedures related to this vulnerability.

Description

CyberData 011209 Intercom does not properly store or protect web server admin credentials.

Impact

For European organizations, especially those in public safety, healthcare, transportation, and critical infrastructure sectors, this vulnerability poses a substantial risk. The CyberData 011209 SIP Emergency Intercom is likely deployed in facilities requiring reliable emergency communication systems. Unauthorized access to the device's admin interface could allow attackers to intercept or manipulate emergency announcements, disable alarms, or cause misinformation during critical incidents, potentially endangering lives and property. Confidentiality compromise of admin credentials could also lead to lateral movement within networks if these devices are connected to broader enterprise systems. Given the device's role in safety-critical environments, the impact extends beyond data loss to physical safety risks and regulatory compliance issues under European laws such as NIS2 and GDPR if personal data or safety is compromised.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

cisa.gov/news-events/ics-advisories/icsa-25-155-01 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 23:48 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats