dbcve.org
WegiaApplication

CVE-2025-53529

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-07
Fix available
A fix is available. Upgrade to 3.4.3 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. An SQL Injection vulnerability was identified in the /html/funcionario/profile_funcionario.php endpoint. The id_funcionario parameter is not properly sanitized or validated before being used in a SQL query, allowing an unauthenticated attacker to inject arbitrary SQL commands. The vulnerability is fixed in 3.4.3.

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's /html/funcionario/profile_funcionario.php endpoint allows unauthenticated attackers to inject arbitrary SQL commands via the unsanitized id_funcionario parameter.

MitigationUpgrade to WeGIA version 3.4.3 or implement strict input validation and parameterized queries on the id_funcionario parameter.

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.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. Locate the affected PHP file
    Search for the file /html/funcionario/profile_funcionario.php in your web root directory
    Affected if The file exists and is accessible via the web server
  2. Confirm the application is WeGIA
    Check the application's source files for WeGIA branding or version information, typically found in a README, config, or version file
    Affected if The application is identified as WeGIA Wegia
  3. Determine the installed WeGIA version
    Find the version file or header in the WeGIA installation and compare it to the affected range (versions prior to 3.4.3)
    Affected if The installed version is lower than 3.4.3
  4. Verify the vulnerable parameter is exposed
    Attempt to access the endpoint /html/funcionario/profile_funcionario.php via HTTP and confirm the id_funcionario parameter is accepted without authentication
    Affected if The endpoint is reachable and accepts the id_funcionario parameter without requiring authentication

You are affected if WeGIA Wegia version is below 3.4.3 and the profile_funcionario.php file is present and accessible with an unauthenticated id_funcionario parameter.

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

Upgrade to WeGIA version 3.4.3 or implement strict input validation and parameterized queries on the id_funcionario parameter.

Recommended fix High confidence

3.4.3

  1. 1. Back up the current WeGIA database and application files before making any changes.
  2. 2. Navigate to the official WeGIA repository at https://github.com/LabRedesCefetRJ/WeGIA
  3. 3. Download version 3.4.3 or later from the releases page, or pull the latest code after commit 0a061bcc5024937edd18ab3e65ccc8f38deb6957
  4. 4. Replace the existing WeGIA application files with the new version from step 3
  5. 5. Verify that the fix has been applied by confirming the id_funcionario parameter is now properly sanitized in /html/funcionario/profile_funcionario.php
  6. 6. Test the profile_funcionario.php endpoint to ensure the SQL Injection vulnerability is no longer present
  7. 7. Restore the application to production after successful testing

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

Fix this in Wegia Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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