dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-40285

HIGH · 8.8 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
WeGIA is a web manager for charitable institutions. Versions prior to 3.6.10 contain a SQL injection vulnerability in dao/memorando/UsuarioDAO.php. The cpf_usuario POST parameter overwrites the session-stored user identity via extract($_REQUEST) in DespachoControle::verificarDespacho(), and the attacker-controlled value is then interpolated directly into a raw SQL query, allowing any authenticated user to query the database under an arbitrary identity. Version 3.6.10 fixes the issue.

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 confidence

WeGIA versions before 3.6.10 have a SQL injection in dao/memorando/UsuarioDAO.php where the cpf_usuario POST parameter is processed through extract($_REQUEST), which overwrites the session-stored user identity. This attacker-controlled value is then directly interpolated into a raw SQL query without parameterization, allowing any authenticated user to manipulate SQL and query the database under arbitrary identities.

MitigationUpgrade to WeGIA version 3.6.10 or later, which contains the fix for this SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify WeGIA installation
    Locate the WeGIA web application directory on the server. Common paths include /var/www/html/, /www/, or the web root. Look for directories containing WeGIA files or the application's index.php.
    Affected if WeGIA is not found on the system - the CVE does not apply.
  2. Determine installed WeGIA version
    Search for a version file or check version strings within the WeGIA source code. Common locations include a VERSION file, version.php, or check the header comments in main PHP files. Compare your version to the affected range (before 3.6.10).
    Affected if The installed version is 3.6.10 or later - the vulnerability has been patched.
  3. Verify vulnerable file exists
    Check if the file dao/memorando/UsuarioDAO.php exists within the WeGIA installation directory.
    Affected if The file does not exist - the vulnerable code path may have been removed or renamed.
  4. Inspect vulnerable code pattern
    Examine dao/memorando/UsuarioDAO.php for the presence of 'extract($_REQUEST)' combined with the 'cpf_usuario' parameter, and look for raw SQL query construction (non-parameterized queries) using this value.
    Affected if The code contains extract($_REQUEST) with cpf_usuario in raw SQL queries - the vulnerability is present.
  5. Confirm authentication is enabled
    Verify that the application requires authentication for the memorando functionality. Check if session-based authentication is active and that the vulnerable endpoint is accessible to authenticated users.
    Affected if Authentication is disabled or the memorando module is not accessible - the attack surface may be reduced but the code flaw remains.

A user is affected if WeGIA version is below 3.6.10 AND the vulnerable file dao/memorando/UsuarioDAO.php contains the extract($_REQUEST) pattern with cpf_usuario in raw SQL queries, and the memorando module is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to WeGIA version 3.6.10 or later, which contains the fix for this SQL injection vulnerability.

Recommended fix High confidence

3.6.10

  1. 1. Identify the current version of WeGIA installed in your environment
  2. 2. Navigate to the official WeGIA GitHub repository (github.com) to obtain version 3.6.10
  3. 3. Create a complete backup of the current WeGIA installation including database and configuration files
  4. 4. Download the version 3.6.10 release package from the repository
  5. 5. Replace the existing WeGIA files with the new version 3.6.10 files, preserving configuration files where possible
  6. 6. Verify that the file dao/memorando/UsuarioDAO.php has been updated in the new version
  7. 7. Test the application to ensure functionality is maintained
  8. 8. Verify the SQL injection vulnerability is resolved by confirming cpf_usuario parameter is no longer directly interpolated into queries

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40285 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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