Skip to main content
VulnerabilityPublished Updated

CVE-2024-53472: WeGIA · Cross-Site Request Forgery (CSRF)

Affects WeGIASource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Dec 2024

  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

Affected software

ProductAffectedFixed in
GitHubnilsonlazarin/WeGIApkg:github/nilsonlazarin/WeGIAOther threatsAffected
  • =3.2.0
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-2024-53472, organizations should implement several specific measures beyond generic advice: 1) Employ anti-CSRF tokens in all state-changing requests to ensure that requests originate from legitimate sources. 2) Validate the HTTP Referer header as an additional check to confirm request origin. 3) Enforce SameSite cookie attributes (preferably 'Strict' or 'Lax') to limit cookie transmission in cross-site contexts. 4) Educate users about phishing risks and encourage cautious behavior when clicking on links from untrusted sources. 5) Monitor application logs for unusual or unauthorized actions that could indicate exploitation attempts. 6) If possible, restrict sensitive operations to POST requests and require explicit user confirmation for critical actions. 7) Engage with the WeGIA vendor or community to obtain patches or updates as soon as they become available. 8) Consider deploying Web Application Firewalls (WAFs) with rules designed to detect and block CSRF attack patterns. These targeted steps will reduce the likelihood and impact of exploitation while awaiting an official patch.

Description

WeGIA v3.2.0 was discovered to contain a Cross-Site Request Forgery (CSRF).

References

Community reviews

Loading reviews…