CVE-2025-6967
Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:NSummary
CVE-2025-6967 is a high-severity EAR (CWE-698) vulnerability in Gov (inferred from references). Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
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-2025-6967 is an Execution After Redirect (EAR) vulnerability in the CMS product from Sarman Soft Software and Technology Services Industry and Trade Ltd. Co. The flaw enables JSON Hijacking (also known as JavaScript Hijacking) and Authentication Bypass. It affects all versions of the CMS through 10022026. The vulnerability is associated with CWE-698 and has a CVSS v3.1 base score of 8.7 (AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N).
A remote attacker with no required privileges or user interaction can exploit this vulnerability over the network, though it requires high attack complexity. Successful exploitation allows the attacker to perform JSON hijacking and bypass authentication, resulting in high impacts to confidentiality and integrity with a changed scope but no availability impact.
Mitigation details are provided in the advisory at https://www.usom.gov.tr/bildirim/tr-26-0050. The vendor was contacted early regarding this disclosure but did not respond. No patches or vendor fixes are mentioned.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207357
Vulnerability Data
Execution After Redirect (EAR) vulnerability in Sarman Soft Software and Technology Services Industry and Trade Ltd. Co. CMS allows JSON Hijacking (aka JavaScript Hijacking), Authentication Bypass. This issue affects CMS: through 10022026. NOTE: The vendor was contacted early about this…
more
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.
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.