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

CVE-2026-42872

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.0, a reflected Cross-Site Scripting (XSS) vulnerability exists in lista_arquivos_etapa.php due to improper handling of user-supplied input. The id_processo parameter is directly embedded into the HTML without sanitization, allowing attackers to inject arbitrary JavaScript. This can lead to session hijacking, credential theft, or execution of malicious actions in the context of the victim's browser. This vulnerability is fixed in 3.7.0.

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 reflected Cross-Site Scripting (XSS) vulnerability exists in WeGIA's lista_arquivos_etapa.php file. The id_processo parameter is directly echoed into HTML output without any sanitization or encoding, allowing attackers to inject arbitrary JavaScript code via crafted URLs.

MitigationUpgrade WeGIA to version 3.7.0 or later, which contains the fix. Alternatively, implement proper input validation and output encoding for the id_processo parameter before embedding it in HTML.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Locate WeGIA installation directory
    Search for the WeGIA web application files on the server. Look for directories containing WeGIA or check common web root locations where PHP applications are deployed.
    Affected if WeGIA is not installed on the server (not affected).
  2. Identify lista_arquivos_etapa.php file
    Locate the file lista_arquivos_etapa.php within the WeGIA installation. Check in the web-accessible directories, typically under a path like /wegia/ or similar.
    Affected if The file lista_arquivos_etapa.php exists in the WeGIA installation.
  3. Check WeGIA version
    Look for version information in WeGIA's source files, such as version.php, a config file, or the main index file. Compare the installed version to the fixed version 3.7.0.
    Affected if Installed version is earlier than 3.7.0.
  4. Verify id_processo parameter handling
    Inspect the lista_arquivos_etapa.php file and search for the id_processo parameter. Check if it is directly echoed into HTML output without using htmlspecialchars(), htmlentities(), or similar encoding functions.
    Affected if The id_processo parameter is directly output without sanitization or encoding.

The environment is affected if WeGIA is installed with a version earlier than 3.7.0 and the lista_arquivos_etapa.php file contains the vulnerable code that echoes the id_processo parameter without sanitization.

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.7.0 or later, which contains the fix. Alternatively, implement proper input validation and output encoding for the id_processo parameter before embedding it in HTML.

Recommended fix High confidence

3.7.0

  1. 1. Backup the current WeGIA installation and database
  2. 2. Obtain WeGIA version 3.7.0 from the official source
  3. 3. Upgrade the existing installation to version 3.7.0 following the standard upgrade procedure
  4. 4. Verify that lista_arquivos_etapa.php is updated and the id_processo parameter is now properly sanitized

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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