dbcve.org
WegiaApplication

CVE-2025-53091

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-27
Fix available
A fix is available. Upgrade to 3.4.0 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 Time-Based Blind SQL Injection vulnerability was discovered in version 3.3.3 the almox parameter of the `/controle/getProdutosPorAlmox.php` endpoint. This issue allows any unauthenticated attacker to inject arbitrary SQL queries, potentially leading to unauthorized data access or further exploitation depending on database configuration. Version 3.4.0 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

WeGIA version 3.3.3 contains a time-based blind SQL injection vulnerability in the almox parameter of the /controle/getProdutosPorAlmox.php endpoint. An unauthenticated attacker can inject arbitrary SQL queries via this parameter, potentially allowing full database compromise including exfiltration of sensitive data.

MitigationUpgrade to WeGIA version 3.4.0 which contains the fix. As a temporary measure, disable or restrict access to the vulnerable endpoint until the upgrade can be performed.

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.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 web application files, typically found in web server document roots. Look for files such as 'getProdutosPorAlmox.php' or configuration files containing 'WeGIA' branding.
    Affected if The WeGIA application files are present on the system.
  2. Identify WeGIA version
    Examine version information in WeGIA source files, commonly found in a 'versao.php', 'version.php', 'config.php', or similar configuration file within the WeGIA installation directory.
    Affected if The installed version is less than 3.4.0 (e.g., 3.3.3 or earlier).
  3. Verify vulnerable endpoint exists
    Check for the presence of the file /controle/getProdutosPorAlmox.php within the WeGIA installation directory.
    Affected if The file getProdutosPorAlmox.php exists and is accessible via the web server.
  4. Confirm endpoint is reachable
    Attempt to access the URL path /controle/getProdutosPorAlmox.php via HTTP/HTTPS request to the web server hosting WeGIA. Observe if the endpoint responds (even with an error).
    Affected if The endpoint is accessible over the network without authentication.
  5. Check for almox parameter usage
    Inspect the getProdutosPorAlmox.php source code to verify it accepts and processes an 'almox' parameter in GET or POST requests.
    Affected if The code processes the 'almox' parameter without proper input sanitization or parameterized queries.

A user is affected if WeGIA version is below 3.4.0 and the /controle/getProdutosPorAlmox.php endpoint with the almox parameter is accessible without authentication.

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.0 or later
Fixed in 3.4.0
Interim mitigation

Upgrade to WeGIA version 3.4.0 which contains the fix. As a temporary measure, disable or restrict access to the vulnerable endpoint until the upgrade can be performed.

Recommended fix High confidence

3.4.0

  1. Obtain version 3.4.0 of WeGIA from the official repository or distribution channel
  2. Replace the existing WeGIA installation files with the version 3.4.0 files
  3. Verify that the /controle/getProdutosPorAlmox.php endpoint is updated to the fixed version
  4. Test that the almox parameter properly handles input and no longer allows SQL injection
  5. Confirm database connectivity and application functionality after upgrade

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 upgrade done

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-53091 — 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-53091 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