Summary
Idno Vulnerable to Remote Code Execution via Chained Import File Write and Template Path Traversal
Impact
- Confidentiality: Full read access to files accessible by the web server user
- Integrity: Arbitrary command execution as the web server user
- Availability: Complete compromise of the host running Idno
An attacker who obtains a web application admin account (via credential theft, weak password, or other means) can escalate to OS-level code execution. The RCE trigger itself requires only a standard authenticated session, meaning the admin account is needed only for the file write stage.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-28507? CVE-2026-28507 is a high-severity OS command injection vulnerability in idno/known (composer), affecting versions < 1.6.4. It is fixed in 1.6.4. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- Which versions of idno/known are affected by CVE-2026-28507? idno/known (composer) versions < 1.6.4 is affected.
- Is there a fix for CVE-2026-28507? Yes. CVE-2026-28507 is fixed in 1.6.4. Upgrade to this version or later.
- Is CVE-2026-28507 exploitable, and should I be worried? Whether CVE-2026-28507 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-28507 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-28507? Upgrade
idno/knownto 1.6.4 or later.