dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-40286

HIGH · 7.5 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
WeGIA is a web manager for charitable institutions. In versions prior to 3.6.10, a Stored Cross-Site Scripting (XSS) vulnerability was identified in the 'Member Registration' (Cadastrar Sócio) function. By injecting a payload into the 'Member Name' (Nome Sócio) field, the script is persistently stored in the database. Consequently, the payload is executed whenever a user navigates to certain URL. 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 confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in WeGIA prior to version 3.6.10 within the Member Registration (Cadastrar Sócio) function. Attackers can inject malicious JavaScript into the Member Name (Nome Sócio) field, which persists in the database and executes when users navigate to affected pages.

MitigationUpgrade WeGIA to version 3.6.10 or later, which contains the fix for this stored XSS vulnerability.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed WeGIA version
    Locate the version file within the WeGIA application directory, or access the administration panel or about page to identify the current version number
    Affected if The version is prior to 3.6.10
  2. Verify Member Registration feature is enabled
    Log into WeGIA and navigate to confirm the Cadastrar Sócio (Member Registration) function is accessible and active in the system
    Affected if The Member Registration module is enabled and accessible to users
  3. Inspect database member name fields for XSS payloads
    Query the database table that stores member records (such as socio, membro, or similar) and examine the Nome Sócio field for HTML tags, script elements, event handlers, or encoded JavaScript vectors
    Affected if Any records contain script tags, javascript: URIs, or XSS payload patterns in the member name field
  4. Review browser execution of stored member data
    Access the Member Registration or member list pages in the application and examine the rendered HTML using browser developer tools to see if member names are reflected without proper encoding
    Affected if Member names render as raw HTML or execute JavaScript when viewed in the browser

The environment is affected if the installed WeGIA version is prior to 3.6.10 AND the Member Registration feature is in use, particularly if suspicious scripts are found stored in the member name database field.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WeGIA to version 3.6.10 or later, which contains the fix for this stored XSS vulnerability.

Recommended fix Moderate confidence

WeGIA version 3.6.10

  1. Identify the current version of WeGIA currently deployed in your environment
  2. Download WeGIA version 3.6.10 from the official GitHub repository
  3. Before upgrading, perform a complete backup of the database and application files
  4. Test the upgrade in a staging environment to verify functionality
  5. Apply the upgrade to the production environment
  6. Verify that the Member Registration (Cadastrar Sócio) function works correctly post-upgrade
  7. Confirm the XSS payload is no longer executable in the Member Name (Nome Sócio) field
Caveat Review release notes for version 3.6.10 to check for any breaking changes or required database migrations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40286 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40286 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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