# CVE-2026-4614: itsourcecode sanitize or validate this input Parameter subjects.php sql injection

> Remote attackers can exploit SQL injection in the subject_code parameter of subjects.php to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-4x24-3v7p-2g45

## What is CVE-2026-4614?

CVE-2026-4614 is a medium-severity SQL injection vulnerability in itsourcecode sanitize or validate this input, published on 23 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in itsourcecode sanitize or validate this input 1.0. This issue affects some unknown processing of the file /admin/subjects.php of the component Parameter Handler. This manipulation of the argument subject_code causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

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-4614?


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

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

## Is CVE-2026-4614 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4614 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4614 is a medium-severity SQL injection vulnerability in itsourcecode sanitize or validate this input, published on 23 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4614 exists.

Affected product: itsourcecode sanitize or validate this input. 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-4614/ (Markdown: https://insights.sbomify.com/CVE-2026-4614/index.md)
```

## Sources

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

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