# CVE-2025-14577: PHP Function Injection in Slican NPC/IPL/IPM/IPU

> Unauthenticated remote attackers can execute arbitrary PHP commands on Slican network devices via a vulnerable endpoint.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-266v-99c5-7x8c

## What is CVE-2025-14577?

CVE-2025-14577 is a critical code injection vulnerability in Slican IPL, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-14577?

It affects 4 products.


Products: Slican Ipl-256 Firmware, Slican Ipm-032 Firmware, Slican Ipu-14 Firmware, Slican Ncp Firmware.

## How do I fix CVE-2025-14577?

No fix has been published for CVE-2025-14577 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14577 being exploited?

There is no known exploitation of CVE-2025-14577 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14577 and fix it if it is affected.

What it is: CVE-2025-14577 is a critical code injection vulnerability in Slican IPL, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14577 in the wild and no public exploit code.

Affected product: Slican IPL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14577/ (Markdown: https://insights.sbomify.com/CVE-2025-14577/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14577
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14577
- OSV: https://osv.dev/vulnerability/CVE-2025-14577

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14577/
Summaries are generated and may contain mistakes; the official description above is the record.