CVE-2026-1517VulnerabilityPublished 5 Feb 2026Updated 23 Feb 2026

CVE-2026-1517: iomad · SQL Injection

Affects iomadSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
iomad	Affected =3.1 =3.2 =3.3 =3.4 =3.5 =3.6 =3.7 =3.8 =3.9 =3.10 =3.11 =4.0 =4.1 =4.2 =4.3 =4.4 =4.5 =5.0	Fixed in–
GitHubiomad/iomad`pkg:github/iomad/iomad`Other threats	Affected =3.1 =3.2 =3.3 =3.4 =3.5 =3.6 =3.7 =3.8 =3.9 =3.10 =3.11 =4.0 =4.1 =4.2 =4.3 =4.4 =4.5 =5.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately monitor for updates and apply official patches from iomad once released to remediate CVE-2026-1517. Until patches are available, restrict access to the Company Admin Block component to trusted administrators only and enforce the principle of least privilege on user accounts to minimize the risk of privilege escalation. Conduct thorough input validation and sanitization on all user-supplied data within customizations or integrations related to iomad. Implement database-level protections such as limiting database user permissions to only necessary operations and employing prepared statements or parameterized queries if custom code is used. Enable detailed logging and monitoring of database queries and application logs to detect anomalous or suspicious activity indicative of SQL injection attempts. Regularly audit user privileges and remove unnecessary high-level access. Consider deploying web application firewalls (WAFs) with SQL injection detection rules tailored to iomad traffic patterns. Educate administrators and developers on secure coding practices to prevent similar vulnerabilities. Finally, maintain up-to-date backups of iomad databases and configurations to enable rapid recovery in case of compromise.

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.

Impact

The potential impact of CVE-2026-1517 includes unauthorized access to or modification of database contents within iomad installations. Although exploitation requires high privileges, successful SQL injection could lead to data leakage, corruption, or unauthorized changes to learning management data such as user information, course content, or administrative settings. This could disrupt educational or corporate training operations, compromise user privacy, and damage organizational reputation. The medium severity score reflects limited but non-negligible risks to confidentiality, integrity, and availability. Organizations worldwide using iomad, especially in sectors where learning management systems are critical, may face operational disruptions and compliance risks if the vulnerability is exploited. The absence of known exploits currently reduces immediate risk but does not eliminate the threat, as attackers could develop exploits given the vulnerability details. The broad version range affected increases the scope of vulnerable systems, potentially impacting many organizations that have not updated to patched versions. The requirement for high privileges limits exploitation to insiders or attackers who have already compromised accounts, but this still represents a significant risk in environments with multiple users and administrative roles.

References

Community reviews

Loading reviews…