CVE-2026-31896
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 · uneditedWeGIA is a web manager for charitable institutions. Prior to version 3.6.6, a critical SQL injection vulnerability exists in the WeGIA application. The remover_produto_ocultar.php script uses extract($_REQUEST) to populate local variables and then directly concatenates these variables into a SQL query executed via PDO::query. This allows an authenticated (or auth-bypassed) attacker to execute arbitrary SQL commands. This can be used to exfiltrate sensitive data from the database or, as demonstrated in this PoC, cause a time-based delay (denial of service). This vulnerability is fixed in 3.6.6.
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 confidenceA critical SQL injection vulnerability in WeGIA prior to 3.6.6 exists in remover_produto_ocultar.php, where extract($_REQUEST) populates variables that are directly concatenated into a SQL query executed via PDO::query without parameterization, allowing authenticated or auth-bypassed attackers to execute arbitrary SQL commands.
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< 3.6.6CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm WeGIA installationLook for the WeGIA application directory on the server. Check common paths such as /var/www/html/, /www/, or the web root. The application is typically identified by the presence of WeGIA-specific files and directory structure.Affected if WeGIA is not installed on the server.
-
Check WeGIA versionLocate the version file or header within the WeGIA installation. Check files like version.php, README, or the main index file for a version number. Compare the installed version against the vulnerable range: versions prior to 3.6.6.Affected if The installed WeGIA version is lower than 3.6.6.
-
Locate the vulnerable scriptSearch for the file remover_produto_ocultar.php within the WeGIA installation directory. This file is the specific location of the SQL injection vulnerability.Affected if The file remover_produto_ocultar.php exists in the WeGIA installation.
-
Verify vulnerable code patternExamine the content of remover_produto_ocultar.php. Look for the use of extract($_REQUEST) followed by direct variable insertion into SQL queries executed via PDO::query without prepared statements or parameter binding.Affected if The file contains extract($_REQUEST) and uses PDO::query with concatenated variables in SQL statements.
A server is affected if it runs WeGIA version lower than 3.6.6 and has the file remover_produto_ocultar.php containing the extract($_REQUEST) with unparameterized PDO::query calls.
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.
dbcve · scoped3.6.6
Upgrade to WeGIA version 3.6.6 or later. If immediate patching is not possible, disable the affected script and implement input validation with prepared statements for any database queries.
3.6.6
- Upgrade WeGIA to version 3.6.6 or later to remediate the SQL injection vulnerability in remover_produto_ocultar.php
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31896 — 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-31896 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