CVE-2026-3264
Go2Ismail Free-Crm ≤ 2025-09-21
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-3264 is a medium-severity EAR (CWE-698) vulnerability in Go2Ismail Free-Crm. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-3264 is a vulnerability in go2ismail Free-CRM up to commit b83c40a90726d5e58f0cc680ffdcaa28a03fb5d1, affecting some unknown functionality of the Administrative Interface component. The issue enables execution after redirect, associated with CWE-698 and CWE-705, and carries a CVSS 3.1 base score of 6.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L).
A remote attacker with low privileges can exploit this vulnerability in an attack scenario requiring low complexity and no user interaction. Successful exploitation leads to low-level impacts on confidentiality, integrity, and availability, with the exploit publicly disclosed and potentially utilizable in the wild.
Advisories, including a GitHub entry on privilege escalation via client-side redirect authorization bypass and VulDB reports, indicate no patches or updated releases are available due to the product's rolling release model, which lacks version information for affected or fixed instances. The vendor was contacted early but provided no response.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8924
Vulnerability Data
A vulnerability was determined in go2ismail Free-CRM up to b83c40a90726d5e58f0cc680ffdcaa28a03fb5d1. Affected by this issue is some unknown functionality of the component Administrative Interface. Executing a manipulation can lead to execution after redirect. The attack can be executed remotely. The exploit…
more
has been publicly disclosed and may be utilized. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The vendor was contacted early about this disclosure but did not respond in any way.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover execution paths that continue after a redirect.
Proper access enforcement reduces the impact of continued execution after a redirect by limiting what the remaining code can do.
Requiring a documented secure development process and standards can mandate exiting immediately after issuing redirects.
Security engineering principles can require structured control-flow constructs and explicit state transitions that avoid improper scoping after tasks or errors.
Failing to a known state on indicated failures limits damage from control-flow errors without preventing the underlying scoping mistake.
Fail-safe procedures reduce the consequences of unhandled or mis-scoped control flow on failure but do not correct the scoping defect itself.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent improper redirect handling via code review and static analysis, but eliminating only this flaw covers a narrow slice of the control's broader intent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect EAR flaws before deployment.
Secure development lifecycle requires proper handling of redirects and exit logic, reducing EAR risk.
Application security requirements can mandate safe redirect patterns and post-redirect termination.
Secure architecture principles discourage continued execution after redirects.
Secure coding standards directly address proper redirect handling and flow termination.