dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-42871

MEDIUM · 6.9 CVSS v4.0 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 →
78/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.7.0, atendido/familiar_docfamiliar.php displays an overly descriptive error message, including database-related details. This verbosity leads to information disclosure, which could assist a potential attacker in mapping the backend infrastructure and expanding the attack surface. 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 · moderate confidence

WeGIA versions prior to 3.7.0 contain an information disclosure vulnerability in the file atendido/familiar_docfamiliar.php. The script returns overly descriptive error messages that expose database-related details such as table names, query structure, or connection information. This information can help attackers map the backend infrastructure and identify further attack vectors.

MitigationUpgrade WeGIA to version 3.7.0 or later to obtain the fix for this vulnerability. As a temporary measure, ensure custom error handlers are configured to suppress detailed database errors in production environments.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 file 'atendido/familiar_docfamiliar.php' or 'atendimento/familiar_docfamiliar.php' in your web server document root or common application directories. Common paths may include /var/www/, /opt/, or C:\inetpub\wwwroot\ on Windows servers.
    Affected if The file exists in your environment, indicating WeGIA is installed and the vulnerable script is present.
  2. Determine installed WeGIA version
    Look for a version file, CHANGELOG, or configuration file in the WeGIA root directory. Common version indicators include a 'version' file, 'VERSION' constant in PHP files, or entries in a config file. Check files like 'index.php', 'config.php', or a 'VERSION' file in the application root.
    Affected if The installed version is lower than 3.7.0, or if no version can be determined and the vulnerable file is present.
  3. Verify the vulnerable script exists
    Confirm the file 'atendido/familiar_docfamiliar.php' (or 'atendimento/familiar_docfamiliar.php') exists in your WeGIA installation. Access the file via a web browser or check the filesystem directly.
    Affected if The file exists in your installation and the version is prior to 3.7.0.
  4. Check PHP error display configuration
    Review your PHP configuration (php.ini) or check for runtime error reporting settings in the application. Look for 'display_errors = On' or 'error_reporting' set to high verbosity (such as E_ALL). You can also create a simple PHP info page to check this.
    Affected if PHP display_errors is enabled (set to On or 1), which would allow the overly descriptive error messages to be rendered in the browser.

You are affected if WeGIA version is lower than 3.7.0 AND the file atendimento/familiar_docfamiliar.php exists AND PHP error display is enabled, allowing database details to be exposed in error messages.

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 to obtain the fix for this vulnerability. As a temporary measure, ensure custom error handlers are configured to suppress detailed database errors in production environments.

Recommended fix Moderate confidence

3.7.0

  1. Backup the current WeGIA installation and database before upgrading
  2. Obtain WeGIA version 3.7.0 from the official source (github.com or vendor repository)
  3. Replace the existing WeGIA files with the version 3.7.0 files, ensuring theberto/familiar_docfamiliar.php is updated to the fixed version
  4. Verify the fix by testing atendidos/familiar_docfamiliar.php to confirm error messages no longer expose database details
  5. Confirm the application functions normally after the upgrade

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-42871 — 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-42871 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