CVE-2026-40284
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. In versions prior to 3.6.10, a Stored Cross-Site Scripting (XSS) vulnerability allows an authenticated user to inject malicious JavaScript via the "Destinatário" field. The payload is stored and later executed when viewing the dispatch page, impacting other users. Version 3.6.10 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 confidenceA stored Cross-Site Scripting (XSS) vulnerability in WeGIA versions prior to 3.6.10 allows authenticated users to inject malicious JavaScript through the 'Destinatário' (recipient) field. The payload is persisted in the database and executes when other users view the dispatch page, enabling attack chaining against multiple users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
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.
-
Check WeGIA versionLocate the version file or about page in the WeGIA installation directory, typically found in a version.php file, configuration file, or the admin dashboard under 'Sobre' or 'Informações do Sistema'. Compare the displayed version number to the affected range (prior to 3.6.10).Affected if The installed version is 3.6.9 or earlier.
-
Identify dispatch module usageDetermine if the dispatch (envio) or notification functionality is actively used or enabled in the WeGIA instance. This is typically found in the menu under 'Despacho' or 'Envio de Documentos'.Affected if The dispatch module is accessible to authenticated users.
-
Verify 'Destinatário' field handlingAs an authenticated user with dispatch privileges, navigate to the dispatch creation or editing page and locate the 'Destinatário' (recipient) input field. Submit a test payload containing HTML script tags (such as <script>alert(1)</script>) in this field and save the dispatch.Affected if The payload is saved without validation errors and executes when the dispatch page is viewed by another user.
-
Inspect database for unsanitized inputQuery the database table that stores dispatch records (commonly named 'despacho', 'envio', or similar). Examine the 'destinatario' column for any stored JavaScript or HTML tags that were submitted through the 'Destinatário' field.Affected if Raw HTML or JavaScript code is stored directly in the database without encoding or sanitization.
-
Review application output encodingExamine the PHP files responsible for rendering the dispatch view page, specifically the code that outputs the 'Destinatário' field value. Look for use of htmlspecialchars() or equivalent encoding functions before outputting user-supplied data.Affected if The 'Destinatário' field value is output directly to HTML without proper encoding, allowing stored scripts to execute.
The environment is affected if WeGIA version is 3.6.9 or earlier and the dispatch module with the 'Destinatário' field is in use, as the injected payload will execute without sanitization.
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 · scopedUpgrade to WeGIA version 3.6.10 or later. Until patched, implement output encoding when rendering the 'Destinatário' field content and add input validation to sanitize special characters.
3.6.10
- Identify the current version of WeGIA currently deployed
- Download WeGIA version 3.6.10 from the official repository or release source
- Create a backup of the current WeGIA installation and database
- Deploy version 3.6.10 following the standard upgrade procedure
- Verify the upgrade was successful by checking the application version
- Test the 'Destinatário' field to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40284 — 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-40284 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