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

> Unauthenticated attackers can exploit SQL injection in the password reset function to access sensitive information in ESIC Livre.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-jq3j-49mj-6p88

## What is CVE-2026-30655?

CVE-2026-30655 is a medium-severity SQL injection vulnerability in n/a, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection in Solicitante::resetaSenha() in esiclivre/esiclivre v0.2.2 and earlier allows unauthenticated remote attackers to gain unauthorized access to sensitive information via the cpfcnpj parameter in /reset/index.php

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

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

It affects 1 product.


Products: Esiclivre Esiclivre.

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

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

## Is CVE-2026-30655 being exploited?

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

Public exploit code:

- Security advisory for CVE-2026-30655: unauthenticated SQL injection in esiclivre (/reset/index.php). (github_poc): https://github.com/brynax/CVE-2026-30655

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30655 is a medium-severity SQL injection vulnerability in n/a, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-30655 in the wild and no public exploit code.

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

## Sources

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

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