Skip to main content
VulnerabilityPublished Updated

CVE-2024-40465: beego · Weak Cryptography

Affects beegoSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% 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 31 Jul 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
Gogithub.com/beego/beegopkg:golang/github.com/beego/beegoOther threatsAffected
  • <=2.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-40465 effectively, organizations should implement the following specific measures: 1) Immediately audit and restrict access to beego applications, ensuring that only trusted users have privileges that could be leveraged for escalation. 2) Employ network-level controls such as firewalls and intrusion prevention systems to limit exposure of vulnerable endpoints to untrusted networks. 3) Monitor application logs and system behavior for unusual access patterns or privilege escalation attempts, using anomaly detection tools where possible. 4) Review and harden cryptographic configurations and cache handling mechanisms in the application to reduce the risk of exploitation related to cryptographic weaknesses. 5) Engage with the beego community or maintainers to track the release of official patches or updates addressing this vulnerability and plan for immediate deployment once available. 6) Consider implementing application-layer security controls such as Web Application Firewalls (WAFs) with custom rules to detect and block exploitation attempts targeting the getCacheFileName function. 7) Conduct internal code reviews and penetration testing focused on privilege escalation vectors within beego-based applications to identify and remediate similar weaknesses proactively. These steps go beyond generic advice by focusing on access control, monitoring, cryptographic hygiene, and proactive engagement with the software vendor.

Description

An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the getCacheFileName function in file.go file

References

Community reviews

Loading reviews…