# CVE-2026-41462: ProjeQtor < 12.4.4 Unauthenticated SQL Injection via Login

> Unauthenticated attackers can inject SQL via the login field to create admin accounts, read data, or execute OS commands in ProjeQtor.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-rrf3-x3xf-m69q

## What is CVE-2026-41462?

CVE-2026-41462 is a critical SQL injection vulnerability in ProjeQtor, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ProjeQtor versions 7.0 through 12.4.3 contain an unauthenticated SQL injection vulnerability in the login functionality where the login variable is directly concatenated into a SQL query without parameterization or sanitization. Attackers can inject arbitrary SQL expressions through the username field at the authentication endpoint to create privileged accounts, read sensitive data, and execute operating system commands if the database user has elevated permissions.

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

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


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

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

## Is CVE-2026-41462 being exploited?

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

Public exploit code:

- CVE-2026-41462 (github_poc): https://github.com/0xredash/CVE-2026-41462

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41462 is a critical SQL injection vulnerability in ProjeQtor, published on 27 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-41462 exists.

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

## Sources

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

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