# CVE-2026-36948: SQL injection in n/a

> Attackers can exploit SQL injection in the view_archive.php file to read or modify database contents in the Online Thesis Archiving System.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-mf3r-jr4m-5wv2

## What is CVE-2026-36948?

CVE-2026-36948 is a high-severity SQL injection vulnerability in n/a, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sourcecodester Online Thesis Archiving System v1.0 is vulnerale to SQL injection in the file /otas/view_archive.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-36948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36948 is a high-severity SQL injection vulnerability in n/a, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36948 exists.

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

## Sources

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

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