CVE-2025-53530: LabRedesCefetRJ WeGIA · Unthrottled Resource Allocation
Affects LabRedesCefetRJ WeGIASource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 3.3.0 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.3.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade labredescefetrj/WeGIA to 3.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublabredescefetrj/WeGIApkg:github/labredescefetrj/WeGIAOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-53530, affected organizations should prioritize upgrading WeGIA to version 3.3.0 or later, where the vulnerability has been addressed. Until patching is possible, organizations should implement network-level protections such as rate limiting and request size restrictions on web servers or reverse proxies to block excessively long HTTP GET requests, specifically targeting the 'errorstr' parameter. Web Application Firewalls (WAFs) can be configured to detect and block anomalous URL lengths or patterns indicative of exploitation attempts. Monitoring server logs for unusual spikes in request lengths or latency can provide early warning signs of attempted exploitation. Additionally, deploying DoS mitigation services or appliances can help absorb or filter malicious traffic. It is also advisable to conduct regular security assessments and penetration tests to verify that the implemented controls effectively prevent exploitation. Finally, organizations should maintain an incident response plan tailored to DoS scenarios to minimize downtime and coordinate rapid recovery.
Description
WeGIA is a web manager for charitable institutions. The Wegia server has a vulnerability that allows excessively long HTTP GET requests to a specific URL. This issue arises from the lack of validation for the length of the errorstr parameter. Tests confirmed that the server processes URLs up to 8,142 characters, resulting in high resource consumption, elevated latency, timeouts, and read errors. This makes the server susceptible to Denial of Service (DoS) attacks. This vulnerability is fixed in 3.3.0.