dbcve.org
WegiaApplication

CVE-2025-22133

CRITICAL · 9.9 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 3.2.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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. Prior to 3.2.8, a critical vulnerability was identified in the /WeGIA/html/socio/sistema/controller/controla_xlsx.php endpoint. The endpoint accepts file uploads without proper validation, allowing the upload of malicious files, such as .phar, which can then be executed by the server. This vulnerability is fixed in 3.2.8.

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

Unrestricted file upload vulnerability in WeGIA's /WeGIA/html/socio/sistema/controller/controla_xlsx.php endpoint allows unauthenticated attackers to upload malicious files (including .phar files) without validation, potentially achieving remote code execution on the server.

MitigationUpgrade to WeGIA version 3.2.8 immediately. Until patched, disable the file upload functionality, implement strict file type validation (whitelist approach), and ensure upload directories have no script execution permissions.

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

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 and version
    Locate the WeGIA web application directory and check the version file or metadata (such as version.php, composer.json, or a VERSION file in the WeGIA root). Compare the version number to the affected range (versions below 3.2.8).
    Affected if The installed WeGIA version is lower than 3.2.8
  2. Verify the vulnerable PHP endpoint exists
    Check if the file /WeGIA/html/socio/sistema/controller/controla_xlsx.php exists in the web server's document root.
    Affected if The file controla_xlsx.php exists in the expected path, indicating the vulnerable component is present
  3. Confirm upload directory is accessible via web
    Identify the upload directory used by the application and verify it is web-accessible (located under the web root). Check the endpoint is reachable by attempting a HEAD or GET request to /WeGIA/html/socio/sistema/controller/controla_xlsx.php.
    Affected if The upload endpoint is reachable from the network and accepts requests without authentication
  4. Check for any existing uploaded suspicious files
    Search the upload directory for file types that should not be present, such as .phar, .php, .phtml, or other executable extensions. Use file system search commands (find, ls, or similar) to list recent uploads.
    Affected if Unexpected executable files (.phar, .php) exist in upload directories, indicating possible exploitation

You are affected if WeGIA version is below 3.2.8 and the controla_xlsx.php endpoint is accessible, as this allows unauthenticated file uploads without validation.

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

Upgrade to WeGIA version 3.2.8 immediately. Until patched, disable the file upload functionality, implement strict file type validation (whitelist approach), and ensure upload directories have no script execution permissions.

Recommended fix High confidence

WeGIA 3.2.8

  1. 1. Create a complete backup of the current WeGIA installation and database
  2. 2. Download WeGIA version 3.2.8 or later from the official repository (https://github.com/nilsonLazarin/WeGIA)
  3. 3. Replace the existing WeGIA files with the new version, preserving any local configuration
  4. 4. Verify the /WeGIA/html/socio/sistema/controller/controla_xlsx.php endpoint now properly validates file uploads
  5. 5. Test that legitimate .xlsx file uploads continue to work correctly after the upgrade

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

Fix this in Wegia Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
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,736.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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