What is the CVSS score of CVE-2025-6967?

CVE-2025-6967 has a CVSS 3.1 base score of 8.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2025-6967?

Within 24 hours: Identify all systems running Sarman Soft CMS and assess exposure to untrusted networks; isolate affected systems or restrict access if operationally feasible. Within 7 days: Implement compensating controls such as WAF rules, network segmentation, and enhanced monitoring; establish vendor communication to obtain patch timeline. Within 30 days: Deploy patch upon availability; conduct security assessment post-remediation; document all mitigations taken.

Sarman Soft Software CVE-2025-6967

HIGH

Execution After Redirect (EAR) (CWE-698)

2026-02-10 iletisim@usom.gov.tr

Authentication Bypass

8.7

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-698 OWASP Top 10:2025 A06:2021 - Vulnerable and Outdated Components ASVS 5.0 V15 - Secure Coding and Architecture Redirect without exit
Impact	CVSS 8.7 (HIGH). Attack vector: Network. Complexity: High. Privileges required: None. User interaction: None.
Exploit ScenarioDerived	An attacker could exploit this vulnerability to compromise the affected system.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Sarman Soft Software and Technology Services Industry and Trade Ltd. Co. CMS contains a security vulnerability (CVSS 8.7).

RemediationAI

Monitor vendor advisories for a patch. Restrict network access to the affected service where possible.

Affected ProductsAI

Product: Sarman Soft Software and Technology Services Industry and Trade Ltd. Co. CMS.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

affects Sarman Soft Software and Technology Services Industry and Trade Ltd. Co. 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.

Know when the next one hits your stack

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.7 HIGH

AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

None

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A high-severity vulnerability (CVSS 8.7) has been identified in Sarman Soft CMS with no available patch. This vulnerability poses a significant risk to organizations using this platform, potentially allowing unauthorized access or data compromise. Immediate mitigation measures are required to reduce exposure while awaiting a vendor patch.

Business Impact: High

Compensating Controls

Implement network segmentation to limit CMS access to trusted internal networks only; deploy Web Application Firewall (WAF) rules to block known attack patterns; enforce strict authentication and access controls; increase security monitoring and logging; disable non-essential CMS features if possible; require multi-factor authentication for administrative access; conduct regular vulnerability scanning; consider load balancer or reverse proxy hardening; maintain offline backups; establish incident response procedures.

Threat Intelligence Overview

EPSS Score

0.0%

Top 94% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.