LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23731: WeGIA Clickjacking Vulnerability

WeGIA is a web manager for charitable institutions. Prior to 3.6.2, The web application is vulnerable to clickjacking attacks. The WeGIA application does not send any defensive HTTP headers related to framing protection. In particular, X-Frame-Options is missing andContent-Security-Policy with frame-ancestors directive is not configured. Because of this, an attacker can load any WeGIA page inside a malicious HTML document, overlay deceptive elements, hide real buttons, or force accidental interaction with sensitive workflows. This vulnerability is fixed in 3.6.2.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

WeGIA versions before 3.6.2 can be embedded inside a malicious webpage because frame-protection headers are missing. A victim could be tricked into clicking hidden or misleading controls in WeGIA. This is not described as data theft or system takeover, but it can affect sensitive workflows requiring user interaction.

Executive priority

Treat as a routine but time-bound web application fix. Prioritize environments where WeGIA supports approvals, account changes, or other sensitive actions by authenticated users. No public source here supports emergency action for active exploitation.

Technical view

CVE-2026-23731 is a CWE-1021 clickjacking issue in LabRedesCefetRJ WeGIA before 3.6.2. The application lacks X-Frame-Options and Content-Security-Policy frame-ancestors protection, allowing WeGIA pages to be framed by attacker-controlled HTML. CVSS 3.1 is 4.3: network exploitable, low complexity, no privileges, user interaction required, low integrity impact.

Likely exposure

Organizations running WeGIA below 3.6.2 are exposed, especially if authenticated users access the application through browsers. The source bundle does not specify hosted deployments, default configurations, or internet-exposure requirements.

Exploitation context

The CVE record and advisory describe a clickjacking condition requiring user interaction. The source bundle does not report active exploitation, and KEV status is false. Practical impact depends on which WeGIA workflows can be triggered through deceptive framing.

Researcher notes

The available evidence is consistent: affected versions are before 3.6.2, fixed in 3.6.2, and the weakness is missing anti-framing controls. Public sources provided do not include exploit details, affected endpoints, or proof of active exploitation.

Mitigation direction

  • Upgrade WeGIA to version 3.6.2 or later.
  • Review the GitHub security advisory and release notes before deployment.
  • If upgrade is delayed, check vendor guidance for supported temporary controls.

Validation and detection

  • Inventory WeGIA instances and record installed versions.
  • Confirm no production instance runs a version earlier than 3.6.2.
  • Check HTTP responses for framing protections after remediation.
  • Review change records for deployment of the 3.6.2 release.
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 · low confidence lookup

CWE-1021: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2026-23731 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

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

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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-23731Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-1021 · source CWE mapping

Improper Restriction of Rendered UI Layers or Frames

Improper Restriction of Rendered UI Layers or Frames represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.