dbcve.org
Ncp FirmwareOperating system · Slican

CVE-2025-14577

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 1.24.0190 / 6.61.0010 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Slican NCP/IPL/IPM/IPU devices are vulnerable to PHP Function Injection. An unauthenticated remote attacker is able to execute arbitrary PHP commands by sending specially crafted requests to /webcti/session_ajax.php endpoint. This issue was fixed in version 1.24.0190 (Slican NCP) and 6.61.0010 (Slican IPL/IPM/IPU).

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 confidence

Slican NCP/IPL/IPM/IPU devices contain a PHP function injection vulnerability in the /webcti/session_ajax.php endpoint. An unauthenticated remote attacker can send specially crafted requests to execute arbitrary PHP commands on the affected device, achieving full remote code execution without any authentication credentials.

MitigationApply the vendor-supplied patches by upgrading Slican NCP devices to version 1.24.0190 and IPL/IPM/IPU devices to version 6.61.0010. If immediate patching is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to the /webcti/ endpoint from untrusted networks.

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
Ncp FirmwareOperating system
Affected:< 1.24.0190
Ipl 256 FirmwareOperating system
Affected:< 6.61.0010
Ipm 032 FirmwareOperating system
Affected:< 6.61.0010
Ipu 14 FirmwareOperating system
Affected:< 6.61.0010

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
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 checks

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

  1. Identify the Slican device model
    Access the device admin interface or check the device label/documentation to determine if it is an NCP, IPL 256, IPM 032, or IPU 14 model.
    Affected if The device is any of these four models and the model cannot be determined.
  2. Check the installed firmware version
    Log into the device web interface or use the device's admin panel to locate the firmware version information. For NCP devices, look for version under system settings. For IPL/IPM/IPU devices, check the firmware version in the device status or about section.
    Affected if The firmware version is below 1.24.0190 for NCP devices, or below 6.61.0010 for IPL/IPM/IPU devices.
  3. Verify if the webcti endpoint is exposed
    Attempt to access http://[device-ip]/webcti/ or http://[device-ip]/webcti/session_ajax.php from a browser or using curl. A 403 or 200 response indicates the endpoint is reachable.
    Affected if The /webcti/ endpoint responds with HTTP 200 or 403 (not a connection timeout or refused error), meaning it is accessible on the network.
  4. Confirm web interface authentication status
    Access the main login page of the device (typically / or /index.php) without providing credentials to see if authentication is required or if the interface is accessible.
    Affected if The web interface does not require authentication or allows unauthenticated access to certain endpoints including /webcti/.

A user is affected if they have a Slican NCP, IPL 256, IPM 032, or IPU 14 device running firmware below the specified version thresholds AND the /webcti/session_ajax.php endpoint is accessible from the network without authentication.

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 1.24.0190 / 6.61.0010 or later
Fixed in 1.24.01906.61.0010
Interim mitigation

Apply the vendor-supplied patches by upgrading Slican NCP devices to version 1.24.0190 and IPL/IPM/IPU devices to version 6.61.0010. If immediate patching is not feasible, implement network segmentation or firewall rules to restrict unauthorized access to the /webcti/ endpoint from untrusted networks.

Recommended fix High confidence

Slican NCP firmware >= 1.24.0190 | Slican IPL/IPM/IPU firmware >= 6.61.0010

  1. Identify the specific Slican device model (NCP, IPL-256, IPM-032, or IPU-14)
  2. Check the current firmware version on the device
  3. For NCP devices: Upgrade firmware to version 1.24.0190 or later
  4. For IPL-256, IPM-032, or IPU-14 devices: Upgrade firmware to version 6.61.0010 or later
  5. After upgrading, verify the /webcti/session_ajax.php endpoint requires authentication

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

Fix this in Ncp Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14577 — 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-2025-14577 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