dbcve.org
Innovaphone PbxApplication · Innovaphone

CVE-2024-24721

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-27
Fix available
A fix is available. Upgrade to 14r1 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered on Innovaphone PBX before 14r1 devices. The password form, used to authenticate, allows a Brute Force Attack through which an attacker may be able to access the administration panel

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 confidence

The Innovaphone PBX admin login page contains a vulnerability where the password authentication form lacks adequate brute force protections, allowing attackers to systematically guess passwords without account lockout or rate limiting. This affects all versions prior to 14r1, potentially granting unauthorized administrative access to the PBX system.

MitigationUpgrade to Innovaphone PBX version 14r1 or later, which contains the security fix. Additionally, implement network-level rate limiting or IP blocking for repeated failed authentication attempts as a compensating control until the upgrade is applied.

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
Innovaphone PbxApplication
Affected:< 14r1

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Innovaphone PBX version
    Access the admin interface or system information page, typically at /admin or /pbxadmin, and locate the version number displayed in the system settings or about page. Alternatively, check the installation files or system logs for the version string.
    Affected if The installed version is any release prior to 14r1 (for example, 13r3, 13r2, 13r1, 12r1, etc.)
  2. Verify admin login page accessibility
    Attempt to access the Innovaphone PBX admin login endpoint - common paths include /admin, /pbxadmin, or the default gateway IP with /admin suffix. Confirm the login form loads without authentication.
    Affected if The admin login page is accessible and displays a password authentication form without any redirect to a login prompt.
  3. Test for rate limiting on failed login attempts
    Send multiple consecutive failed authentication requests to the admin login page (using curl or similar tool), observing whether the server returns HTTP 429 (Too Many Requests), locks the session, or imposes any delay between attempts.
    Affected if No rate limiting, account lockout, or delay is observed after multiple failed login attempts - requests are processed normally each time.
  4. Confirm no IP-based protection at network level
    Inspect any upstream firewall, WAF, or reverse proxy configuration to determine if external rate limiting is applied to the admin login endpoint.
    Affected if No network-level rate limiting or IP blocking is configured, leaving the login endpoint unprotected from brute force attacks.

A system is affected if it runs any Innovaphone PBX version prior to 14r1 with the admin login page exposed and no external rate limiting protecting against brute force password guessing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 14r1 or later
Fixed in 14r1
Interim mitigation

Upgrade to Innovaphone PBX version 14r1 or later, which contains the security fix. Additionally, implement network-level rate limiting or IP blocking for repeated failed authentication attempts as a compensating control until the upgrade is applied.

Recommended fix Moderate confidence

14r1

  1. 1. Schedule a maintenance window for the Innovaphone PBX upgrade
  2. 2. Backup the current PBX configuration and user data
  3. 3. Download the firmware/installer for version 14r1 from the official Innovaphone download portal
  4. 4. Follow Innovaphone's standard upgrade procedure for the PBX appliance
  5. 5. After upgrade, verify the administration interface is accessible and functioning
  6. 6. Confirm the password authentication mechanism now has brute force protection enabled
  7. 7. Test that administrative login works correctly with existing credentials
Caveat Review Innovaphone 14r1 release notes for any feature changes or migration requirements specific to your configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Innovaphone Pbx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-24721 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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