CVE-2025-46828

9.8 CRITICAL

📋 TL;DR

An unauthenticated SQL injection vulnerability in WeGIA versions up to 3.3.0 allows attackers to execute arbitrary SQL commands via the /html/socio/sistema/get_socios.php endpoint. This can lead to data theft, authentication bypass, or complete database compromise. All organizations using vulnerable WeGIA installations are affected.

💻 Affected Systems

Products:
  • WeGIA
Versions: Versions up to and including 3.3.0
Operating Systems: Any OS running WeGIA
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of affected versions are vulnerable. The vulnerability requires the WeGIA application to be accessible and the vulnerable endpoint to be exposed.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to exfiltration of sensitive donor/socio data, authentication bypass allowing administrative access, and potential server takeover via SQL injection chaining.

🟠

Likely Case

Data exfiltration of sensitive charitable institution data including donor information, financial records, and personal identifiable information.

🟢

If Mitigated

Limited impact with proper network segmentation, WAF protection, and database permission restrictions preventing data modification or system compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

SQL injection vulnerabilities are commonly weaponized. The unauthenticated nature and CVSS 9.8 score make this highly attractive to attackers.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 3.3.1

Vendor Advisory: https://github.com/LabRedesCefetRJ/WeGIA/security/advisories/GHSA-5qw5-q55h-6qg7

Restart Required: Yes

Instructions:

1. Backup current installation and database. 2. Download WeGIA version 3.3.1 from official repository. 3. Replace vulnerable files with patched version. 4. Restart web server service. 5. Verify fix by testing vulnerable endpoint.

🔧 Temporary Workarounds

Web Application Firewall (WAF) Rules

all

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

# Example ModSecurity rule: SecRule REQUEST_URI "@streq /html/socio/sistema/get_socios.php" "id:1001,phase:2,deny,msg:'Block WeGIA SQLi attempt'"

Network Access Control

linux

Restrict access to the vulnerable endpoint using network controls

# Example iptables rule: iptables -A INPUT -p tcp --dport 80 -m string --string "/get_socios.php" --algo bm -j DROP

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate WeGIA from internet and sensitive internal networks
  • Deploy a web application firewall with SQL injection detection rules specifically for the vulnerable endpoint

🔍 How to Verify

Check if Vulnerable:

Test the endpoint /html/socio/sistema/get_socios.php with SQL injection payloads (e.g., adding ' OR '1'='1 to query parameters) and observe database errors or unexpected responses

Check Version:

Check WeGIA version in admin panel or review application files for version indicators

Verify Fix Applied:

After patching, attempt the same SQL injection tests and verify they are properly rejected or sanitized without database errors

📡 Detection & Monitoring

Log Indicators:

  • Unusual database query patterns in application logs
  • Multiple failed login attempts or SQL error messages in web server logs
  • Requests to /html/socio/sistema/get_socios.php with suspicious parameters

Network Indicators:

  • Unusual outbound database connections from web server
  • Large data transfers from database server following suspicious web requests

SIEM Query:

source="web_logs" AND uri="/html/socio/sistema/get_socios.php" AND (query="*OR*" OR query="*UNION*" OR query="*SELECT*" OR query="*INSERT*")

🔗 References

📤 Share & Export