CVE-2026-28411
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, an unsafe use of the `extract()` function on the `$_REQUEST` superglobal allows an unauthenticated attacker to overwrite local variables in multiple PHP scripts. This vulnerability can be leveraged to completely bypass authentication checks, allowing unauthorized access to administrative and protected areas of the WeGIA application. 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 uses the PHP extract() function unsafely on the $_REQUEST superglobal in multiple scripts. This imports request parameters directly into the local variable scope, allowing attackers to overwrite application variables including those controlling authentication state. By supplying specific variable names as request parameters, unauthenticated users can bypass login checks and access administrative functions.
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 check the version identifier in the WeGia installation. Common locations include a version.php file, config file, or the administrative interface About page.Affected if The installed version is less than 3.6.5
-
Search for unsafe extract() usage on superglobalsSearch the WeGia PHP source files for patterns: extract($_REQUEST), extract($_GET), extract($_POST), or extract($_SERVER). Use grep or a file search tool across the web root directory.Affected if Any PHP file contains extract() called directly on superglobals without the EXTR_SKIP or EXTR_PREFIX_ALL flags
-
Identify variable overwrite potentialExamine the extracted variables in context. Look for authentication-related variables such as $login, $authenticated, $user, $is_admin, or session variables that control access. Check if these can be supplied as HTTP request parameters.Affected if Variables controlling authentication state or session can be overwritten via request parameters
-
Verify application accessibilityConfirm the WeGia application is accessible over HTTP/HTTPS and the login/management interface is reachable.Affected if The WeGia web interface is exposed and accepts user requests containing arbitrary parameter names
A user is affected if WeGia version is below 3.6.5 AND the codebase contains extract() applied to $_REQUEST or other superglobals without proper sanitization, allowing authentication bypass via parameter 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 replaces the unsafe extract() usage with secure input handling. If immediate upgrade is not possible, audit all PHP files using extract() on superglobals and replace with explicit variable assignment or filter_input().
WeGIA version 3.6.5
- 1. Back up the current WeGIA installation including all files and the database
- 2. Download WeGIA version 3.6.5 from the official GitHub repository (github.com)
- 3. Replace all existing WeGIA PHP files with the new version 3.6.5 files
- 4. Verify the extract() function is no longer used unsafely on $_REQUEST superglobal in the new version
- 5. Test that authentication and authorization mechanisms function correctly after upgrade
- 6. Verify the application functions normally with standard workflows
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28411 — 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-28411 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