CVE-2025-30507
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 to gather sensitive information through blind SQL injections.
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 confidenceThe CyberData 011209 Intercom contains a blind SQL injection vulnerability that can be exploited by unauthenticated attackers. By injecting malicious SQL queries through input parameters, an attacker can extract sensitive data from the backend database through blind boolean-based or time-based techniques.
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
- 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 the device firmware versionAccess the intercom's web administration interface and locate the version information, typically found in System settings, About, or Status pages. Alternatively, check the boot log or system information page if available via the device's web UI or console.Affected if The firmware version is below 22.0.1 (for example, 21.x.x or earlier)
-
Verify the web interface is accessibleConfirm that the intercom's web management interface is reachable over the network on typical HTTP/HTTPS ports (80/443 or custom ports). Attempt to access the login or status page from a permitted network location.Affected if The web interface is exposed and reachable on the network, providing input fields or parameters that accept user data
-
Determine if the device is network-exposedCheck if the intercom has a publicly accessible IP address or is reachable from untrusted networks. Review firewall rules, VLAN configurations, or port forwarding settings that may expose the device.Affected if The device can be reached by unauthenticated attackers from untrusted networks (such as the internet or untrusted VLANs)
-
Identify accessible input parametersReview the web interface for any parameters that accept user input, such as search fields, configuration inputs, or API endpoints. These are the potential vectors for blind SQL injection.Affected if The device has web-facing input parameters that process user-supplied data without obvious authentication barriers
The device is affected if it is running firmware version below 22.0.1 and has its web interface network-accessible with input parameters that could accept SQL injection payloads.
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
Implement proper input validation and use parameterized queries or prepared statements to prevent SQL injection. Apply vendor patches when available.
22.0.1
- Identify the current firmware version of the CyberData 011209 Sip Emergency Intercom device
- Download firmware version 22.0.1 or later from the official CyberData vendor website
- Follow the vendor's documented firmware upgrade procedure for the intercom device
- After upgrading, verify the device is operational and running the new firmware version
- Confirm the SQL injection vulnerability is resolved by testing or consulting vendor release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-30507 — 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-30507 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