CVE-2026-45026
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.7.3, a Stored Cross-Site Scripting (XSS) vulnerability allows an authenticated user to inject malicious JavaScript into the Processo de Aceitação (html/atendido/processo_aceitacao.php) page, which is executed when user access the the page, enabling session hijacking and account takeover. This vulnerability is fixed in 3.7.3.
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 versions prior to 3.7.3 contain a stored XSS vulnerability in the Processo de Aceitação page (html/atendido/processo_aceitacao.php). An authenticated attacker can inject malicious JavaScript that executes when other users view the page, enabling session hijacking and account takeover.
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.
-
Confirm WeGIA is installedLook for the WeGIA application directory on the server, typically in web root paths like /var/www/html/, /www/html/, or C:\inetpub\wwwroot\. Search for files named processo_aceitacao.php within the html/atendido/ subdirectory.Affected if The WeGIA application directory and the file html/atendido/processo_aceitacao.php are present on the server.
-
Identify the installed WeGIA versionCheck for a version file in the WeGIA root directory, or access the application and look for a version identifier in the footer, about page, or administrative settings panel. Common version file locations include version.php, config.php, or a version constant in the main index file.Affected if The installed version is lower than 3.7.3 (e.g., 3.7.2, 3.7.1, 3.6.x, etc.).
-
Verify the Processo de Aceitação page is accessibleAttempt to access the URL path /html/atendido/processo_aceitacao.php through the web server. If the application is behind authentication, verify that the page loads (even if login is required to reach it).Affected if The page exists and responds, indicating the vulnerable component is exposed.
-
Check for existing XSS payloads in the databaseInspect the database tables that store processo_aceitacao data (such as aceitacao, processo, or atendimento tables) for suspicious script tags, javascript: URIs, or event handler attributes in input fields. Use SQL queries like: SELECT * FROM aceitacao WHERE campo LIKE '%<script%' OR campo LIKE '%onerror%'.Affected if Malicious scripts or event handlers are found stored in the database, confirming active exploitation.
The environment is affected if WeGIA is installed with a version prior to 3.7.3 and the processo_aceitacao.php file exists and is accessible, regardless of whether the vulnerability has been exploited yet.
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.7.3 or later. If immediate upgrade is not possible, implement input validation and output encoding on the processo_aceitacao.php page to neutralize malicious script payloads.
3.7.3
- Obtain the WeGIA version 3.7.3 release from the official GitHub repository
- Backup the current WeGIA installation and database before proceeding
- Replace the existing WeGIA files with the version 3.7.3 files
- Verify that the processo_aceitacao.php file has been updated as part of the new version
- Test the Processo de Aceitação page to confirm the XSS vulnerability is no longer present
- Ensure all other components of WeGIA function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45026 — 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-45026 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