VulnerabilityPublished 1 Dec 2025

CVE-2025-13809: orionsec orion-ops · Server-Side Request Forgery

Affects orionsec orion-opsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:15 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 26% 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:L/VA:L/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: Low
Vulnerable system availability: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), 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 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

1. Immediately restrict network egress from the orion-ops server to only trusted destinations, using firewall rules or network segmentation, to limit SSRF exploitation scope. 2. Monitor and log all outbound requests originating from orion-ops to detect anomalous or unauthorized connections. 3. If possible, disable or restrict the vulnerable SSH Connection Handler functionality until a patch is available. 4. Employ web application firewalls (WAFs) or reverse proxies with SSRF detection capabilities to filter malicious requests targeting the vulnerable endpoints. 5. Conduct internal audits to identify any low-privilege accounts or services that could be leveraged to exploit this vulnerability and harden their access controls. 6. Stay alert for vendor updates or community patches and apply them promptly once released. 7. Educate operational teams about the risks of SSRF and encourage reporting of suspicious network activity related to orion-ops. 8. Consider deploying network-level DNS filtering to prevent resolution of unauthorized domains that could be targeted by SSRF attacks.

Description

A vulnerability has been found in orionsec orion-ops up to 5925824997a3109651bbde07460958a7be249ed1. Affected by this issue is some unknown functionality of the file orion-ops-api/orion-ops-web/src/main/java/cn/orionsec/ops/controller/MachineInfoController.java of the component SSH Connection Handler. Such manipulation of the argument host/sshPort/username/password/authType leads to server-side request forgery. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. A patch should be applied to remediate this issue. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, exploitation of this SSRF vulnerability could allow attackers to pivot from the compromised orion-ops server into internal networks, potentially accessing sensitive internal services, databases, or cloud metadata endpoints. This could lead to data leakage, unauthorized access, or further compromise of internal infrastructure. Given orion-ops is a tool related to SSH connection management, organizations relying on it for infrastructure operations may face disruption or risk exposure of critical operational data. The medium severity rating reflects moderate impact but ease of exploitation without user interaction. The lack of vendor response and patch availability increases risk exposure. Organizations in sectors with high reliance on secure infrastructure management, such as finance, energy, and government, may be particularly impacted. Additionally, the ability to perform SSRF attacks can facilitate reconnaissance and lateral movement within networks, increasing the overall attack surface and risk of more severe follow-on attacks.

Summary

CVE-2025-13809 is a medium severity server-side request forgery vulnerability affecting orionsec's orion-ops product up to commit 5925824997a3109651bbde07460958a7be249ed1. The vulnerability exists in the SSH Connection Handler component, specifically within the MachineInfoController.java source file. The flaw is due to insufficient validation and sanitization of input parameters—host, sshPort, username, password, and authType—used to establish SSH connections. An attacker with low privileges and no user interaction can remotely exploit this vulnerability by manipulating these parameters to coerce the server into sending crafted requests to arbitrary internal or external network resources. This can lead to unauthorized internal network scanning, access to sensitive internal services, or interaction with cloud metadata endpoints, potentially exposing confidential information or enabling further attacks. The vulnerability does not require authentication but does require low privileges, which may be achievable through other means depending on deployment. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, and low impact on confidentiality, integrity, and availability. Although no known exploits are currently in the wild, public disclosure increases the risk of exploitation. Organizations using orion-ops should monitor for updates and consider network-level controls to restrict outbound requests from the affected service.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 8 Dec 2025, 06:34 UTC

Technical details

References

Community reviews

Related threats