Skip to main content
VulnerabilityPublished

CVE-2025-53531: LabRedesCefetRJ WeGIA · Unthrottled Resource Allocation

Affects LabRedesCefetRJ WeGIASource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High : upgrade to 3.3.0 soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade labredescefetrj/WeGIA to 3.3.0.

Affected software

ProductAffectedFixed in
GitHublabredescefetrj/WeGIApkg:github/labredescefetrj/WeGIAOther threatsAffected
  • <3.3.0
Fixed in
  • 3.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should prioritize upgrading WeGIA installations to version 3.3.0 or later, where the vulnerability is fixed. Until patching is possible, implementing web application firewall (WAF) rules to detect and block excessively long HTTP GET requests targeting the 'fid' parameter can mitigate exploitation attempts. Rate limiting and request size restrictions at the network perimeter or reverse proxy level should be enforced to prevent resource exhaustion. Monitoring server logs for abnormal request patterns and latency spikes can provide early warning signs of attempted DoS attacks. Additionally, deploying DoS protection services or solutions that can absorb or filter malicious traffic will enhance resilience. It is also advisable to conduct regular security assessments and update incident response plans to include scenarios involving application-layer DoS attacks. Finally, organizations should engage with the vendor for timely updates and security advisories.

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

References

Community reviews

Loading reviews…