Skip to main content
VulnerabilityPublished Updated

CVE-2024-40464: beego · Missing Validation of OpenSSL Certificate

Affects beegoSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% 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-40464, organizations should first identify all instances of beego framework version 2.2.0 or earlier in their environments. Immediate steps include restricting access to the sendMail function and related SMTP logging components by implementing strict access controls and input validation. Developers should review and harden the code around smtp.go to ensure that only authorized users can invoke email sending functionalities. Until an official patch is released, consider disabling or isolating the SMTP logging feature if feasible, or applying custom patches to enforce privilege checks. Employ network segmentation and firewall rules to limit exposure of the affected services to untrusted networks. Monitor logs and email systems for unusual activity that could indicate exploitation attempts. Additionally, implement robust privilege management policies to minimize the number of users with elevated rights, reducing the attack surface. Stay updated with vendor advisories for patches and apply them promptly once available. Conduct thorough security testing, including penetration testing focused on email and logging components, to detect potential exploitation vectors.

Description

An issue in beego v.2.2.0 and before allows a remote attacker to escalate privileges via the sendMail function located in beego/core/logs/smtp.go file

References

Community reviews

Loading reviews…