dbcve.org
WegiaApplication

CVE-2025-55167

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 3.4.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 an open source web manager with a focus on the Portuguese language and charitable institutions. Prior to version 3.4.8, a SQL Injection vulnerability was identified in the /html/funcionario/dependente_remover.php endpoint, specifically in the id_dependente parameter. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the database. This issue has been patched in version 3.4.8.

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

WeGIA versions prior to 3.4.8 contain a SQL Injection vulnerability in the /html/funcionario/dependente_remover.php endpoint. The id_dependente parameter is not properly sanitized, allowing attackers to inject arbitrary SQL commands and potentially compromise the database's confidentiality, integrity, and availability.

MitigationUpgrade to WeGIA version 3.4.8 or later. Alternatively, implement parameterized queries (prepared statements) for the id_dependente parameter in the affected endpoint to neutralize SQL injection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WegiaApplication
Affected:< 3.4.8

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Identify WeGIA version
    Locate the version file or check the application header/admin panel for the installed WeGIA version number
    Affected if The installed version is below 3.4.8
  2. Locate vulnerable script
    Check if the file /html/funcionario/dependente_remover.php exists in the web root directory
    Affected if The file exists and is accessible via the web server
  3. Verify endpoint is reachable
    Attempt to access the affected PHP script via HTTP/HTTPS to confirm it responds
    Affected if The endpoint returns a valid response (200 OK) rather than a 404 error
  4. Check for SQL injection parameters
    Inspect the dependent_remover.php script to confirm it accepts the id_dependente parameter without parameterized query usage
    Affected if The script directly uses the id_dependente parameter in SQL queries without prepared statements

You are affected if running WeGIA version less than 3.4.8 with the /html/funcionario/dependente_remover.php endpoint accessible and using the id_dependente parameter unsafely in SQL queries.

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
Upgrade available Upgrade to 3.4.8 or later
Fixed in 3.4.8
Vendor patch github.com →
Interim mitigation

Upgrade to WeGIA version 3.4.8 or later. Alternatively, implement parameterized queries (prepared statements) for the id_dependente parameter in the affected endpoint to neutralize SQL injection attacks.

Recommended fix High confidence

WeGIA version 3.4.8

  1. Backup your current WeGIA database and application files before proceeding with any changes
  2. Download WeGIA version 3.4.8 from the official GitHub repository (https://github.com/LabRedesCefetRJ/WeGIA)
  3. Replace the existing application files with the files from version 3.4.8, ensuring the /html/funcionario/dependente_remover.php file is updated
  4. Verify that the patch commit cb7f5e2b98ef6087b80659627f368612e3c535f3 is included in your installation
  5. Test the application to ensure it functions correctly after the upgrade
  6. Review application logs for any suspicious SQL injection attempts that may have occurred prior to patching
Caveat Review release notes for any configuration or database changes between your current version and 3.4.8 before upgrading

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

Fix this in Wegia Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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