CVE-2026-28408
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.5, the script in adicionar_tipo_docs_atendido.php does not go through the project's central controller and does not have its own authentication and permission checks. A malicious user could make a request through tools like Postman or the file's URL on the web to access features exclusive to employees. The vulnerability allows external parties to inject unauthorized data in massive quantities into the application server's storage. Version 3.6.5 fixes the issue.
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 confidenceWeGIA prior to v3.6.5 contains a broken access control vulnerability in adicionar_tipo_docs_atendido.php. This script bypasses the central authentication controller entirely, allowing unauthenticated external attackers to inject arbitrary data into the application's storage through direct HTTP requests.
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.5CVSS 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.
-
Identify WeGIA versionLocate the version file or version indicator in the WeGIA installation directory and determine the installed version numberAffected if The installed version is below 3.6.5
-
Locate vulnerable scriptSearch for the file adicionar_tipo_docs_atendido.php within the WeGIA web root directoryAffected if The script exists in the installation
-
Verify script accessibilityAttempt an HTTP request to adicionar_tipo_docs_atendido.php without providing any authentication credentials or session cookiesAffected if The script responds without requiring authentication (returns 200 OK instead of redirecting to login)
-
Confirm data injection is possibleSend a crafted HTTP POST request to adicionar_tipo_docs_atendido.php with arbitrary parameter data, observing whether the application accepts and stores the input without authenticationAffected if The application accepts and processes the request without any authentication token or valid session
The environment is affected if WeGIA version is below 3.6.5 and the script adicionar_tipo_docs_atendido.php is accessible without authentication, allowing unauthenticated data injection.
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.5
Upgrade WeGIA to version 3.6.5 or later, which implements proper authentication and authorization checks for the affected script.
3.6.5
- Obtain the WeGIA version 3.6.5 release from the official GitHub repository
- Back up the current WeGIA installation including all configuration files and database
- Download the version 3.6.5 release package
- Replace the existing WeGIA files with the new version 3.6.5 files, preserving any local configuration if needed
- Verify that adicionar_tipo_docs_atendido.php is now properly routed through the central controller
- Confirm authentication and permission checks are enforced on the affected script
- Test that unauthorized requests to adicionar_tipo_docs_atendido.php are now rejected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28408 — 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-28408 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