Skip to main content
VulnerabilityPublished Updated

CVE-2024-44625: Path Traversal

Source CVE Database V5

0

Not known to be exploited · 16% EPSS · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Nov 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

AI-suggested

To mitigate CVE-2024-44625, organizations should first verify if they are running Gogs versions up to 0.13.0 and plan immediate upgrades once a patched version is released. In the absence of an official patch, administrators should restrict repository editing permissions strictly to trusted users and enforce the principle of least privilege. Implement network-level access controls to limit exposure of the Gogs instance to internal or trusted networks only. Enable detailed logging and monitoring of file access and modification events within Gogs to detect suspicious activity early. Conduct regular audits of repository contents and server file systems to identify unauthorized changes. Consider deploying web application firewalls (WAFs) with custom rules to detect and block directory traversal attempts targeting the editFilePost endpoint. Additionally, isolate the Gogs server in a hardened environment with minimal privileges and ensure underlying operating system security best practices are followed to reduce the impact of potential exploitation.

Description

Gogs <=0.13.0 is vulnerable to Directory Traversal via the editFilePost function of internal/route/repo/editor.go.

References

Community reviews

Loading reviews…