# CVE-2026-1517: iomad Company Admin Block sql injection

> Remote attackers can exploit SQL injection in the Company Admin Block to read or modify database contents.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-2xjx-542r-phch

## What is CVE-2026-1517?

CVE-2026-1517 is a medium-severity SQL injection vulnerability in iomad, published on 5 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was identified in iomad up to 5.0. Affected is an unknown function of the component Company Admin Block. Such manipulation leads to sql injection. The attack can be executed remotely. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-1517?


## How do I fix CVE-2026-1517?

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

## Is CVE-2026-1517 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1517 and fix it if it is affected.

What it is: CVE-2026-1517 is a medium-severity SQL injection vulnerability in iomad, published on 5 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1517 in the wild and no public exploit code.

Affected product: iomad. 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-2026-1517/ (Markdown: https://insights.sbomify.com/CVE-2026-1517/index.md)
```

## Sources

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

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