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

CVE-2026-45025

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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.7.3, a Stored Cross-Site Scripting (XSS) vulnerability allows an authenticated user to inject malicious JavaScript into the "Etapas de um Processo" (html/atendido/etapa_processo.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 confidence

A stored Cross-Site Scripting (XSS) vulnerability in WeGIA versions prior to 3.7.3 allows authenticated users to inject malicious JavaScript into the 'Etapas de um Processo' page (html/atendido/etapa_processo.php). The injected payload persists and executes whenever users access the page, enabling session hijacking and potential account takeover.

MitigationUpgrade to WeGIA version 3.7.3 or later. If immediate patching is not possible, implement output encoding and input validation on the etapa_processo.php page to neutralize malicious script injection.

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 checks

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

  1. Confirm WeGIA version
    Locate the version file or header in the WeGIA installation (commonly in a config file, README, or application footer) and compare it to the affected range (versions prior to 3.7.3)
    Affected if The installed version is 3.7.2 or lower
  2. Verify vulnerable file exists
    Check for the presence of html/atendido/etapa_processo.php in the WeGIA web root directory
    Affected if The file exists and the version is prior to 3.7.3
  3. Confirm authenticated access to the feature
    Log in to WeGIA and navigate to the 'Etapas de um Processo' page (typically under the atendimento or processo module)
    Affected if The page is accessible to your authenticated user account and the application version is prior to 3.7.3
  4. Inspect page for existing XSS payloads
    View the page source or interact with form fields in the 'Etapas de um Processo' section; check if user-supplied data is rendered without proper encoding
    Affected if The page accepts input and reflects it back unescaped in the browser, indicating the vulnerability is present and exploitable

You are affected if WeGIA version is prior to 3.7.3 AND you have the vulnerable etapa_processo.php file accessible to authenticated users in your environment.

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 to WeGIA version 3.7.3 or later. If immediate patching is not possible, implement output encoding and input validation on the etapa_processo.php page to neutralize malicious script injection.

Recommended fix High confidence

WeGIA version 3.7.3

  1. Backup the current WeGIA installation and database before proceeding with any changes
  2. Download WeGIA version 3.7.3 from the official GitHub repository or distribution source
  3. Replace the existing WeGIA files with the files from version 3.7.3, preserving configuration files as needed
  4. Verify that the html/atendido/etapa_processo.php file has been updated with the fix
  5. Test the 'Etapas de um Processo' page by attempting to inject a benign XSS payload (e.g., <script>alert('XSS')</script>) to confirm the vulnerability is patched
  6. Monitor the application logs for any errors following the upgrade
Caveat Review release notes for version 3.7.3 to check for any changes that may affect existing functionality or require configuration adjustments

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45025 — 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-45025 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