/

CVE-2026-54767

Severity:

CRITICAL RISK

(9.1)

Missing Authentication (CWE-306) in WeGIA Deletion

CVE-2026-54767

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306, CWE-798

Impact:

Unauthorized destructive data loss

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Before version 3.8.5, WeGIA exposes a destructive member-deletion endpoint without requiring an authenticated administrative session. An attacker who obtains the hardcoded key can invoke the endpoint and permanently remove records from several database tables when the database account permits table truncation.

Affected context

The vulnerability occurs in WeGIA deployments using the affected deletar_socios.php controller before version 3.8.5. The endpoint is reachable through an unauthenticated GET request, and its key check relies on a hardcoded value embedded in publicly available application source. Exploitation also depends on the referenced tables existing and the web process database account having truncation privileges.

Exploit preconditions

  • Attack surface: Publicly reachable web endpoint - Required access: Knowledge of the hardcoded chave value; no administrative

session is required

  • Trigger point: A GET request to the member-deletion controller - Authorization condition: The endpoint does not enforce application-level

authentication or administrative authorization

  • Database condition: The web process account must be able to execute

truncation operations on the affected tables

  • Why exploitation is possible: A publicly recoverable secret is treated as

an authorization control, while destructive database operations remain

reachable without a user session

Why this happens

The underlying defect combines missing authentication and hardcoded credentials. The controller performs a security-sensitive operation without first establishing an authenticated, authorized administrative identity, and it uses a fixed key embedded in source as an access check. This maps primarily to CWE-306, Missing Authentication for Critical Function, with CWE-798, Use of Hard-coded Credentials, describing the embedded secret pattern. Because the endpoint can issue table-truncation operations, the authorization failure has a destructive database impact.

Potential impact

  • An attacker may permanently destroy member and contributor records.
  • Related address and person records could be removed from the database.
  • The application could experience data integrity loss or service disruption.
  • Restoration efforts could incur operational cost and require backups.
  • Downstream reporting, workflows, and charitable-institution operations could be affected.

General mitigation guidance

Mitigation generally focuses on enforcing authentication and explicit authorization before any destructive operation. Security-sensitive endpoints should use server-side identity and role checks rather than hardcoded keys, and secrets should not be embedded in public source or treated as authorization substitutes. Destructive workflows can use secure-by-default controls such as narrowly scoped service identities, separation of duties, confirmation or approval gates, transaction safeguards, backups, and database accounts that lack unnecessary truncation privileges. Input trust should be reduced by accepting only controlled server-side actions and by restricting the endpoint's exposure where practical.

How teams detect issues like this

Detection can include static analysis and code review rules that flag unauthenticated routes performing DELETE, TRUNCATE, or other destructive database operations. Reviewers can search for hardcoded keys, passwords, or authorization tokens used in route guards, as well as controllers that perform authorization checks after database actions. Dynamic testing can verify that unauthenticated requests receive denial responses and that the application database identity lacks unnecessary destructive privileges. Policy enforcement may require authentication and authorization middleware on all administrative routes and prohibit secrets in source repositories.

Sources

SourceLink
github.comgithub.com/LabRedesCefetRJ/WeGIA/commit/84d9d0a7c66c29b238ab381ffcfb9e0ce260796a
github.comgithub.com/LabRedesCefetRJ/WeGIA/pull/1689
github.comgithub.com/LabRedesCefetRJ/WeGIA/releases/tag/3.8.5
github.comgithub.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-399w-rxhp-jh9f

Frequently asked

questions

Yes, where the affected web endpoint is reachable and the attacker can obtain

the hardcoded key. An administrative session is not required.

The attacker needs network access to the endpoint and knowledge of the

embedded key. Successful destruction also requires the web process database

account to have truncation privileges.

Require server-side authentication and role-based authorization before

reaching destructive database logic, and remove hardcoded keys as

authorization mechanisms. The database identity should also have only the

minimum required privileges.

Apply consistent authorization middleware, keep secrets out of source

repositories, test denial behavior for unauthenticated requests, and enforce

least-privilege database policies with code review and automated checks.

Find out what's already
exploitable in your codebase.