VulnerabilityPublished 1 Dec 2025

CVE-2025-13807: orionsec orion-ops · Improper Authorization

Affects orionsec orion-opsSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Restrict network access to the orion-ops API endpoints, especially the MachineKeyController, using firewalls, VPNs, or network segmentation to limit exposure to trusted hosts only. 2) Deploy Web Application Firewalls (WAFs) or API gateways with custom rules to detect and block unauthorized API calls targeting the vulnerable controller. 3) Implement additional authorization checks at the application or proxy level to enforce strict access controls beyond the vulnerable component. 4) Monitor logs and network traffic for unusual or unauthorized access attempts to the orion-ops API, focusing on the MachineKeyController endpoints. 5) Conduct internal audits of orion-ops usage and permissions to identify and reduce unnecessary privileges. 6) Prepare incident response plans specific to orion-ops compromise scenarios. 7) Engage with the vendor or community for updates or unofficial patches and consider alternative solutions if the vendor remains unresponsive. 8) Educate relevant IT and security teams about the vulnerability and the importance of rapid detection and containment. These measures will help reduce the attack surface and limit potential exploitation until an official patch is available.

Description

A vulnerability was detected in orionsec orion-ops up to 5925824997a3109651bbde07460958a7be249ed1. Affected is the function MachineKeyController of the file orion-ops-api/orion-ops-web/src/main/java/cn/orionsec/ops/controller/MachineKeyController.java of the component API. The manipulation results in improper authorization. The attack can be executed remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of CVE-2025-13807 could lead to unauthorized access to orion-ops API functions, potentially compromising operational management systems that rely on this software. This could result in unauthorized disclosure of sensitive configuration or operational data, unauthorized changes to machine keys or related credentials, and potential lateral movement within the network. While the confidentiality impact is limited, the improper authorization could undermine trust in system integrity and operational continuity. Organizations in critical infrastructure sectors, manufacturing, or IT service providers using orion-ops may face increased risk of operational disruption or data leakage. The availability impact is minimal, but unauthorized access could facilitate further attacks or privilege escalation. The medium severity rating suggests a moderate risk that should not be ignored, especially given the public availability of exploits and lack of vendor patching. European entities with regulatory obligations around data protection and operational security must address this vulnerability promptly to avoid compliance issues and potential reputational damage.

Summary

CVE-2025-13807 is an improper authorization vulnerability identified in the orionsec orion-ops product, specifically within the MachineKeyController function of the orion-ops-api component. The vulnerability arises due to insufficient authorization validation, allowing remote attackers to execute unauthorized actions via the API without requiring authentication or user interaction. The affected version is up to commit 5925824997a3109651bbde07460958a7be249ed1. The CVSS 4.0 vector indicates the attack can be performed remotely over the network with low complexity and no privileges required, but the impact on confidentiality is limited, and there is no impact on integrity or availability. The vulnerability could allow attackers to access or manipulate machine key-related operations, potentially leading to unauthorized access or control over system components managed by orion-ops. The lack of vendor response and patch availability necessitates immediate defensive measures by users of the product. The vulnerability affects the API layer, which is often exposed to internal or external networks, increasing the attack surface. Organizations relying on orion-ops for operational management should assess their exposure and implement compensating controls.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Dec 2025, 05:32 UTC

Technical details

References

Community reviews

Related threats