dbcve.org
WegiaApplication

CVE-2025-53527

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
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. A Time-Based Blind SQL Injection vulnerability was discovered in the almox parameter of the /controle/relatorio_geracao.php endpoint. This issue allows attacker to inject arbitrary SQL queries, potentially leading to unauthorized data access or further exploitation depending on database configuration. This vulnerability is fixed in 3.4.1.

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

Time-Based Blind SQL Injection in the almox parameter of /controle/relatorio_geracao.php in WeGIA versions prior to 3.4.1. The vulnerability allows unauthenticated remote attackers to inject arbitrary SQL queries through the unsanitized almox parameter, potentially extracting sensitive data from the database.

MitigationUpgrade to WeGIA version 3.4.1 or later. Implement parameterized queries/prepared statements for all database operations involving user input.

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

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 installation location
    Search for WeGIA web application files on the server. Common paths include /var/www/html/, /www/, or custom web root directories. Look for files containing 'WeGIA' or 'wegia' in the filename or header.
    Affected if WeGIA is installed and the version is below 3.4.1 (specifically version 3.3.3 is confirmed affected)
  2. Determine WeGIA version
    Check for a version file, composer.json, or any version identifier within the WeGIA installation directory. Common locations include the root directory or a config file. Compare the found version against the affected range (prior to 3.4.1).
    Affected if The installed version is 3.3.3 or any version prior to 3.4.1
  3. Verify vulnerable file exists
    Locate the file /controle/relatorio_geracao.php within the WeGIA installation directory. This is the specific file containing the SQL injection vulnerability in the almox parameter.
    Affected if The file exists in the WeGIA web root and the version is vulnerable
  4. Confirm application is network accessible
    Verify the WeGIA web application is accessible over HTTP/HTTPS. The SQL injection is exploitable remotely and unauthenticated, so the application must be reachable via network requests to the endpoint /controle/relatorio_geracao.php
    Affected if The application is exposed and the vulnerable endpoint is reachable without authentication

You are affected if WeGIA is installed with a version prior to 3.4.1 (confirmed vulnerable at 3.3.3) and the file /controle/relatorio_geracao.php exists in an accessible web directory.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to WeGIA version 3.4.1 or later. Implement parameterized queries/prepared statements for all database operations involving user input.

Recommended fix High confidence

3.4.1

  1. 1. Backup your current WeGIA installation and database
  2. 2. Download WeGIA version 3.4.1 from the official repository or release channel
  3. 3. Replace the existing WeGIA files with the new version 3.4.1 files
  4. 4. Verify the patch commit 9de9a741d1d26ae76b2215a32660817d9bd452aa is included in the new version
  5. 5. Test the application to ensure the /controle/relatorio_geracao.php endpoint no longer accepts SQL injection in the almox parameter
  6. 6. Monitor logs for any attempted SQL injection attacks

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

Fix this in Wegia Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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