dbcve.org
WegiaApplication

CVE-2025-53937

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-16
Fix available
A fix is available. Upgrade to 3.4.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 an open source web manager with a focus on the Portuguese language and charitable institutions. A SQL Injection vulnerability was identified in the `/controle/control.php` endpoint, specifically in the `cargo` parameter, of WeGIA prior to version 3.4.5. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the database. Version 3.4.5 fixes the issue.

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

SQL injection vulnerability in WeGIA prior to version 3.4.5 allows remote attackers to execute arbitrary SQL commands through the vulnerable 'cargo' parameter in the /controle/control.php endpoint. The lack of proper input sanitization or parameterized queries enables attackers to manipulate SQL queries, potentially exposing or modifying sensitive database contents.

MitigationUpgrade WeGIA to version 3.4.5 or later. If immediate patching is not possible, implement input validation and use parameterized queries for the cargo parameter as a temporary workaround.

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.5

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 installed WeGIA version
    Search for version indicators in WeGIA installation files such as version.php, a README file, or the main index/about page. Check the application header or footer for version display.
    Affected if The installed version is below 3.4.5 (e.g., 3.4.4, 3.4.3, earlier versions).
  2. Confirm control.php endpoint exists
    Locate the file /controle/control.php in the WeGIA web root directory and verify it is accessible via HTTP/HTTPS.
    Affected if The /controle/control.php file exists and is web-accessible.
  3. Inspect cargo parameter handling in control.php
    Open /controle/control.php and locate code that processes the 'cargo' parameter. Search for SQL query statements (SELECT, INSERT, UPDATE, DELETE) that include the 'cargo' variable directly without using prepared statements, parameterized queries, or input sanitization functions.
    Affected if The code passes the 'cargo' parameter directly into SQL queries without proper escaping, prepared statements, or input validation.

You are affected if WeGIA version is below 3.4.5 AND the /controle/control.php endpoint is accessible AND the 'cargo' parameter is handled in SQL queries without parameterized queries or 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
Upgrade available Upgrade to 3.4.5 or later
Fixed in 3.4.5
Interim mitigation

Upgrade WeGIA to version 3.4.5 or later. If immediate patching is not possible, implement input validation and use parameterized queries for the cargo parameter as a temporary workaround.

Recommended fix High confidence

WeGIA version 3.4.5

  1. 1. Identify the current version of WeGIA installed in your environment
  2. 2. Create a complete backup of the database and all application files
  3. 3. Download WeGIA version 3.4.5 from the official GitHub repository (github.com)
  4. 4. Install version 3.4.5 following the standard upgrade procedures documented for WeGIA
  5. 5. Verify the upgrade was successful by checking the installed version
  6. 6. Test that the /controle/control.php endpoint with the cargo parameter functions correctly after the upgrade
  7. 7. Confirm the SQL injection vulnerability is remediated by validating that arbitrary SQL commands cannot be injected through the cargo parameter

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 / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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