dbcve.org
WegiaApplication

CVE-2025-55168

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/saude/aplicar_medicamento.php endpoint, specifically in the id_fichamedica 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

A SQL Injection vulnerability exists in WeGIA versions prior to 3.4.8 within the /html/saude/aplicar_medicamento.php endpoint, specifically via the id_fichamedica parameter. Attackers can inject arbitrary SQL commands to read, modify, or delete database contents, potentially compromising the entire application and underlying system.

MitigationUpgrade WeGIA to version 3.4.8 or later to remediate this vulnerability. If immediate patching is not feasible, disable or restrict access to the affected endpoint at the network or application firewall level until the patch can be applied.

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 configuration within the WeGIA installation directory. Common locations include a version.php file, CHANGELOG, or the administration panel where version info is displayed. Compare your installed version against 3.4.8.
    Affected if The installed WeGIA version is lower than 3.4.8
  2. Verify vulnerable endpoint exists
    Check if the file /html/saude/aplicar_medicamento.php exists in the web root of the WeGIA application. This can be done by inspecting the source directory structure or attempting to access the file via HTTP request (if direct access is allowed by the server).
    Affected if The file exists and is accessible via the web server
  3. Confirm parameter usage
    Review application logs, web server access logs, or conduct a traffic capture to observe if the id_fichamedica parameter is being passed to the vulnerable endpoint in incoming requests.
    Affected if The id_fichamedica parameter is being processed by the aplicar_medicamento.php endpoint without evidence of input sanitization or parameterized queries
  4. Check database user privileges
    Examine the database configuration file used by WeGIA to determine what privileges the application database user has. Verify if the database user has permissions beyond what is minimally required for the application to function.
    Affected if The database user has broad privileges (such as DROP, DELETE, or FILE privileges) that could be exploited through SQL injection

You are affected if WeGIA version is below 3.4.8 AND the /html/saude/aplicar_medicamento.php endpoint is accessible and processes the id_fichamedica parameter without proper SQL injection protection.

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 WeGIA to version 3.4.8 or later to remediate this vulnerability. If immediate patching is not feasible, disable or restrict access to the affected endpoint at the network or application firewall level until the patch can be applied.

Recommended fix High confidence

version 3.4.8

  1. Backup the current WeGIA installation and database before upgrading
  2. Download version 3.4.8 from the official GitHub repository (https://github.com/LabRedesCefetRJ/WeGIA)
  3. Replace the existing installation files with the new version 3.4.8 files
  4. Verify the fix by checking that /html/saude/aplicar_medicamento.php now properly sanitizes the id_fichamedica parameter
  5. Test the application functionality to ensure the upgrade did not introduce regressions
  6. Ensure the web server has appropriate file permissions set after the upgrade

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

Fix this in Wegia Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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