CVE-2025-6967: Authentication Bypass in Sarman Soft's CMS
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 disclosure but did not respond in any way.
Sarman Soft CMS has a reported authentication bypass weakness. An attacker may be able to reach protected data or functions without signing in, despite a redirect being issued. The issue is high severity, but the sources do not confirm active exploitation or a vendor fix.
Executive priority
Prioritize inventory and exposure reduction now. This is high severity and affects authentication boundaries, but evidence for exploitation and fixes is incomplete. Treat internet-facing deployments as the main business risk until authoritative remediation guidance is available.
Technical view
The CVE describes an Execution After Redirect issue mapped to CWE-698 in Sarman Soft CMS through 10022026. The record says it can allow JSON Hijacking and authentication bypass. CVSS 3.1 is 8.7 with network access, no privileges, no user interaction, high confidentiality and integrity impact, and high attack complexity.
Likely exposure
Exposure is most likely where Sarman Soft CMS is internet-accessible, especially admin, API, or JSON endpoints. The affected version data is imprecise in the CVE record, so teams should treat any deployment through 10022026 as potentially affected until vendor or government guidance clarifies scope.
Exploitation context
The source bundle does not show KEV listing or active exploitation. The vulnerability is remotely reachable and requires no privileges or user interaction, but the CVSS vector marks attack complexity as high. No public exploit details are provided in the supplied sources.
Researcher notes
The CVE record is sparse: affected version formatting is unclear, one listed government reference is marked broken, and no patch is named. Avoid assuming product branches, exploit availability, or remediation specifics beyond validating EAR behavior and authentication enforcement.
Mitigation direction
Identify all Sarman Soft CMS deployments and their versions.
Restrict public access to admin, API, and JSON endpoints where feasible.
Require upstream authentication or VPN access for management interfaces.
Monitor vendor and Turkish government advisories for confirmed fixes.
Review logs for unauthenticated access to protected CMS resources.
Validation and detection
Confirm whether any deployed Sarman Soft CMS version is through 10022026.
Map exposed CMS routes, especially admin, API, and JSON endpoints.
Verify protected responses stop processing after redirects.
Check whether JSON endpoints enforce authentication and authorization server-side.
Review access logs for suspicious unauthenticated requests to protected routes.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-698: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-698 · source CWE mapping
Execution After Redirect (EAR)
Execution After Redirect (EAR) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.