dbcve.org
WegiaApplication

CVE-2025-61603

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-02
Fix available
A fix is available. Upgrade to 3.5.0 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 a Web manager for charitable institutions. Versions 3.4.12 and below include an SQL Injection vulnerability which was identified in the /controle/control.php endpoint, specifically in the descricao parameter. This vulnerability allows attackers to execute arbitrary SQL commands, compromising the confidentiality, integrity, and availability of the database. This issue is fixed in version 3.5.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

SQL injection vulnerability in WeGIA versions 3.4.12 and below allows remote attackers to execute arbitrary SQL commands via the descricao parameter in the /controle/control.php endpoint. The flaw enables complete compromise of the database affecting confidentiality, integrity, and availability.

MitigationUpgrade to WeGIA version 3.5.0 or later which contains the fix for this SQL injection vulnerability.

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

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. Locate WeGIA installation directory
    Search for the WeGIA application files, typically in web root directories. Look for files named 'control.php' under a '/controle/' path, or search for WeGIA-specific files like 'index.php', 'config.php', or files containing 'WeGIA' in headers.
    Affected if The application files cannot be found or the /controle/control.php endpoint does not exist in the environment.
  2. Identify installed WeGIA version
    Check version files or configuration within the WeGIA installation. Look for version indicators in files like 'version.php', 'config.php', 'VERSION', or within the main application header/comment blocks. The version is typically displayed in the application or can be found in release notes or changelog files.
    Affected if The installed version is below 3.5.0 (versions 3.4.12 and below are vulnerable). If version cannot be determined, assume affected.
  3. Verify descricao parameter is processed
    Inspect the /controle/control.php file to confirm it handles the 'descricao' parameter. Search for code that accepts or processes the 'descricao' GET or POST parameter.
    Affected if The vulnerable endpoint exists and the descricao parameter is processed without proper input sanitization or parameterized queries.
  4. Check database interaction in control.php
    Review the control.php file for SQL query execution that incorporates the descricao parameter directly into queries. Look for SQL statements (SELECT, INSERT, UPDATE, DELETE) where descricao is concatenated or interpolated into the query string.
    Affected if SQL queries in control.php accept the descricao parameter without using prepared statements, parameterized queries, or proper escaping.

The environment is affected if WeGIA version is below 3.5.0 and the /controle/control.php endpoint exists with the vulnerable descricao parameter handling.

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.5.0 or later
Fixed in 3.5.0
Vendor patch github.com →
Interim mitigation

Upgrade to WeGIA version 3.5.0 or later which contains the fix for this SQL injection vulnerability.

Recommended fix High confidence

3.5.0

  1. Backup the current WeGIA installation and database before proceeding with any changes
  2. Download version 3.5.0 from the official WeGIA repository or release page
  3. Replace the existing WeGIA files with the version 3.5.0 files, preserving any custom configurations
  4. Verify that the /controle/control.php endpoint now properly sanitizes the descricao parameter
  5. Test that the application functions correctly after the upgrade
  6. If using automated tools, re-scan the application to confirm the SQL Injection vulnerability is remediated
Caveat Review release notes for version 3.5.0 to check for any configuration or feature changes that may affect your deployment

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

Fix this in Wegia Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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