LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23723: WeGIA has a Critical SQL Injection in Atendido_ocorrenciaControle via id_memorando parameter

WeGIA is a web manager for charitable institutions. Prior to 3.6.2, an authenticated SQL Injection vulnerability was identified in the Atendido_ocorrenciaControle endpoint via the id_memorando parameter. This flaw allows for full database exfiltration, exposure of sensitive PII, and potential arbitrary file reads in misconfigured environments. This vulnerability is fixed in 3.6.2.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

WeGIA versions before 3.6.2 have an authenticated SQL injection flaw that can expose the application database. For charitable institutions, this may mean sensitive beneficiary, staff, or operational data could be accessed by a malicious authenticated user.

Executive priority

Prioritize remediation for any internet-accessible or broadly used WeGIA deployment. The issue is authenticated, but potential database exposure makes it important for privacy, trust, and operational continuity.

Technical view

CVE-2026-23723 is CWE-89 SQL injection in WeGIA’s Atendido_ocorrenciaControle endpoint through the id_memorando parameter. The advisory states it can enable full database exfiltration, sensitive PII exposure, and possible arbitrary file reads in misconfigured environments. Fixed in WeGIA 3.6.2.

Likely exposure

Exposure is limited to organizations running LabRedesCefetRJ WeGIA before version 3.6.2. The CVSS vector requires network access and high privileges, with no user interaction required.

Exploitation context

The source bundle does not report public exploitation or CISA KEV listing. Risk remains significant because successful exploitation can compromise confidentiality, integrity, and availability of the database.

Researcher notes

Assessment is based on the CVE record, GitHub security advisory, pull request, and 3.6.2 release. Sources identify the vulnerable parameter and impact but do not provide evidence of active exploitation in the supplied material.

Mitigation direction

  • Upgrade WeGIA to version 3.6.2 or later.
  • Review the GitHub advisory and release notes for vendor guidance.
  • Restrict administrative access to trusted users and networks where feasible.
  • If compromise is suspected, review database access logs and application audit records.

Validation and detection

  • Inventory WeGIA deployments and confirm installed version.
  • Verify affected systems are not running versions earlier than 3.6.2.
  • Confirm the 3.6.2 release or later is deployed in production.
  • Review logs for unusual authenticated access to Atendido_ocorrenciaControle.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23723 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2026-23723Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LabRedesCefetRJWeGIA< 3.6.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.