CVE-2026-3999: Pointsharp ID Server · Insecure Direct Object Reference
Affects Pointsharp ID ServerSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 9.0.0 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.0.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Upgrade Pointsharp ID Server to 9.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PointsharpID Server | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2026-3999, organizations should first identify if their Pointsharp ID Server deployments are running affected configurations. Since no patches are currently linked, immediate steps include reviewing and tightening access control policies, especially those involving user-controlled keys or parameters. Implement strict input validation and parameter sanitization to prevent manipulation of authorization keys. Employ network segmentation and least privilege principles to limit the impact of potential horizontal escalations. Monitor authentication and authorization logs for unusual access patterns indicative of privilege abuse. Engage with Pointsharp support or vendor advisories for forthcoming patches or workarounds. Consider deploying compensating controls such as multi-factor authentication (MFA) to reduce the risk of compromised accounts being leveraged for exploitation. Regularly update and audit identity management configurations to ensure adherence to security best practices. Finally, prepare incident response plans to quickly address any detected exploitation attempts.
Description
A broken access control may allow an authenticated user to perform a horizontal privilege escalation. The vulnerability only impacts specific configurations.