CVE-2026-30655
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSQL 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in esiclivre v0.2.2 and earlier allows unauthenticated remote attackers to inject malicious SQL queries through the cpfcnpj parameter in the /reset/index.php endpoint via the Solicitante::resestaSenha() function, enabling unauthorized access to sensitive database information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Esiclivre versionCheck for a version file, configuration file, or meta information in the application root. Common locations include version.php, VERSION.txt, or the main configuration file. Also check the HTTP Server header or any version disclosure in error pages.Affected if The discovered version is 0.2.2 or any version lower than 0.2.2
-
Verify the /reset/index.php endpoint existsConfirm the presence of the reset directory and index.php file in the web application root directory. This endpoint handles password reset requests.Affected if The /reset/index.php file exists and is accessible via web requests
-
Confirm the cpfcnpj parameter is processed by Solicitante::resestaSenha()Locate the Solicitante class file and examine the resestaSenha() method to verify it accepts and processes the cpfcnpj parameter. Check if this parameter is passed directly to database queries without proper escaping or parameterized queries.Affected if The cpfcnpj parameter is used in SQL queries without input validation or prepared statements
-
Test for SQL injection vulnerabilitySend a crafted request to /reset/index.php with a cpfcnpj value containing SQL injection syntax (such as cpfcnpj=1' OR '1'='1). Observe if the application returns database errors or behaves differently than expected.Affected if The application responds with SQL errors or unexpected behavior indicating unsanitized input is being executed as SQL code
A system is affected if it runs Esiclivre version 0.2.2 or lower AND has the /reset/index.php endpoint accessible, where the cpfcnpj parameter is processed by the Solicitante::resestaSenha() function without SQL injection protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of esiclivre that implements proper input validation and parameterized queries for the cpfcnpj parameter. Alternatively, apply web application firewall rules to block SQL injection payloads until the code fix can be deployed.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30655 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30655 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data