Skip to main content
CVE-2026-23731VulnerabilityPublished

CVE-2026-23731: LabRedesCefetRJ WeGIA · Clickjacking

Affects LabRedesCefetRJ WeGIASource CVE Database V5

0

Not known to be exploited · CVSS 4.3 Medium : upgrade to 3.6.2 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.6.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade WeGIA and labredescefetrj/WeGIA to 3.6.2.

Affected software

ProductAffectedFixed in
LabRedesCefetRJWeGIAAffected
  • <3.6.2
Fixed in
  • 3.6.2
GitHublabredescefetrj/WeGIApkg:github/labredescefetrj/WeGIAOther threatsAffected
  • <3.6.2
Fixed in
  • 3.6.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade WeGIA installations to version 3.6.2 or later, where the vulnerability is patched. In addition to upgrading, organizations should implement HTTP response headers to enforce frame restrictions: specifically, configure the X-Frame-Options header with the value DENY or SAMEORIGIN, and/or set the Content-Security-Policy header with a frame-ancestors directive that restricts framing to trusted domains. Web application firewalls (WAFs) can be configured to detect and block suspicious framing attempts. User awareness training should emphasize the risks of interacting with suspicious links or embedded content. Regular security audits and penetration testing should verify that frame protection headers are correctly applied and effective. For organizations unable to immediately upgrade, temporary mitigations include deploying reverse proxies or security gateways that inject the necessary headers. Monitoring for unusual user activity or workflow anomalies can help detect potential exploitation attempts.

Description

CVE-2026-23731 is a medium-severity clickjacking vulnerability affecting versions of the WeGIA web manager prior to 3.6.2. The application lacks critical HTTP headers such as X-Frame-Options and Content-Security-Policy frame-ancestors, allowing attackers to embed WeGIA pages within malicious frames. This enables overlaying deceptive UI elements to trick users into unintended interactions, potentially compromising sensitive workflows. The vulnerability does not impact confidentiality or availability directly but can lead to integrity issues through unauthorized actions. Exploitation requires user interaction but no authentication or complex attack vectors. The issue is fixed in version 3.6.2.

References

Community reviews

Loading reviews…