CVE-2025-58453

8.2 HIGH

📋 TL;DR

A SQL injection vulnerability in WeGIA versions 3.4.10 and earlier allows authenticated attackers to execute arbitrary SQL queries through the id_anexo parameter in the /WeGIA/html/memorando/exibe_anexo.php endpoint. This can lead to unauthorized access to sensitive database information. Organizations using WeGIA for charitable institution management are affected.

💻 Affected Systems

Products:
  • WeGIA
Versions: 3.4.10 and prior
Operating Systems: Any OS running WeGIA
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated access to exploit

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including exfiltration of sensitive donor data, financial records, and personal information, potentially leading to data breach, regulatory fines, and reputational damage.

🟠

Likely Case

Unauthorized access to sensitive information stored in the database, potentially including donor details, financial records, and internal communications.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permission restrictions in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

SQL injection vulnerabilities are commonly exploited and tools like sqlmap can automate exploitation

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.4.11

Vendor Advisory: https://github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-gg48-pg9f-39fx

Restart Required: Yes

Instructions:

1. Backup current installation and database. 2. Download version 3.4.11 from official repository. 3. Replace vulnerable files with patched version. 4. Restart web server. 5. Verify functionality.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy WAF rules to block SQL injection patterns targeting the vulnerable endpoint

Input Validation Filter

all

Implement server-side input validation to sanitize id_anexo parameter before processing

🧯 If You Can't Patch

  • Implement strict input validation and parameterized queries for the vulnerable endpoint
  • Restrict database user permissions to minimum required and implement network segmentation

🔍 How to Verify

Check if Vulnerable:

Check WeGIA version in admin panel or by examining version files. If version is 3.4.10 or earlier, system is vulnerable.

Check Version:

Check /WeGIA/version.txt or admin panel version display

Verify Fix Applied:

After patching, verify version shows 3.4.11 and test the vulnerable endpoint with SQL injection test payloads.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts followed by access to vulnerable endpoint
  • SQL syntax errors in web server logs

Network Indicators:

  • Unusual patterns of requests to /WeGIA/html/memorando/exibe_anexo.php with SQL injection payloads

SIEM Query:

source="web_server" AND uri="/WeGIA/html/memorando/exibe_anexo.php" AND (payload="UNION" OR payload="SELECT" OR payload="' OR '1'='1")

🔗 References

📤 Share & Export