CVE-2024-48952: Logpoint · Missing Authentication
Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium · fixed in 7.5.0 : update Logpoint when convenient.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Logpoint before 7.5.0
- Patch
- Available – fixed in 7.5.0
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
- Upgrade Logpoint SOAR to version 7.5.0 or later, where this vulnerability is addressed by eliminating the static JWT secret key usage.
- Restrict network access to SOAR API endpoints using network segmentation, firewalls, or VPNs to limit exposure to trusted hosts only.
- Monitor SOAR API access logs for anomalous or unauthorized token usage patterns indicative of forged JWT tokens.
- Implement additional authentication layers or API gateways that enforce dynamic token validation or multi-factor authentication for API access.
- Rotate any static secrets or keys if possible and audit configurations to ensure no hardcoded secrets remain.
- Conduct regular security assessments and penetration tests focusing on API authentication mechanisms.
- Educate security teams about the risks of static secrets and enforce secure development practices to avoid similar issues in future.
Description
An issue was discovered in Logpoint before 7.5.0. SOAR uses a static JWT secret key to generate tokens that allow access to SOAR API endpoints without authentication. This static key vulnerability enables attackers to create custom JWT secret keys for unauthorized access to these endpoints.