CVE-2025-61037: Sevencs Ec2007 Kernel privilege escalation (CVSS 7.0)

Description

A local privilege escalation vulnerability exists in SevenCs ORCA G2 2.0.1.35 (EC2007 Kernel v5.22). The flaw is a Time-of-Check Time-of-Use (TOCTOU) race condition in the license management logic. The regService process, which runs with SYSTEM privileges, creates a fixed directory and writes files without verifying whether the path is an NTFS reparse point. By exploiting this race condition, an attacker can replace the target directory with a junction pointing to a user-controlled path. This causes the SYSTEM-level process to drop binaries in a location fully controlled by the attacker, allowing arbitrary code execution with SYSTEM privileges. The vulnerability can be exploited by any standard user with only a single UAC confirmation, making it highly practical and dangerous in real-world environments.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityHigh

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Sevencs Ec2007 Kernel5.22

Sevencs Orca G22.0.1.35

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://gist.github.com/jc0818/233462416579661e4e2795f96457a6bfExploitThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-61037 being actively exploited?

CVE-2025-61037 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.15%.

How severe is CVE-2025-61037?

CVE-2025-61037 has a CVSS 3.1 base score of 7.0, rated high. EPSS estimates a 0.15% probability of exploitation.

Which products are affected by CVE-2025-61037?

Affected products include Sevencs Ec2007 Kernel, Sevencs Orca G2.

How do I fix CVE-2025-61037?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-61037 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo