CVE-2025-10777VulnerabilityPublished 22 Sep 2025

CVE-2025-10777: JSC R7 R7-Office Document Server · Path Traversal

Affects JSC R7 R7-Office Document ServerSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 2025.3.1.923 : update JSC R7 R7-Office Document Server when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.3.1.923

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 22 Sep 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 2026-10-26.

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

Affected software

Product	Affected	Fixed in
JSC R7 R7-Office Document Server	Affected =20250820	Fixed in–

AI-suggested

European organizations should prioritize upgrading the JSC R7 R7-Office Document Server to version 2025.3.1.923 or later, where the vulnerability is patched. In addition to patching, organizations should implement strict access controls on document server endpoints, especially the /downloadas/ path, to restrict access to trusted users and networks. Deploying web application firewalls (WAFs) with rules to detect and block path traversal patterns in HTTP requests can provide an additional layer of defense. Regularly auditing server logs for unusual access patterns targeting the 'cmd' parameter or the /downloadas/ endpoint can help detect attempted exploitation. Network segmentation to isolate document servers from the broader corporate network reduces the blast radius if exploitation occurs. Finally, organizations should review file system permissions to ensure that the document server process has the minimum necessary privileges, limiting the potential impact of path traversal.

Description

A flaw has been found in JSC R7 R7-Office Document Server up to 20250820. Impacted is an unknown function of the file /downloadas/. Executing manipulation of the argument cmd can lead to path traversal. The attack can be launched remotely. Upgrading to version 2025.3.1.923 is recommended to address this issue. The affected component should be upgraded. R7-Office is a fork of OpenOffice and at the moment it remains unclear if OpenOffice is affected as well. The OpenOffice team was not able to reproduce the issue in their codebase. The vendor replied: "We confirm that this vulnerability has been verified and patched in release 2025.3.1.923. During our security testing, it was not possible to exploit the issue - the server consistently returns proper error responses to the provided scenarios."

Impact

For European organizations using the JSC R7 R7-Office Document Server, this vulnerability poses a risk of unauthorized access to sensitive files on document servers, potentially exposing confidential business documents or internal configuration files. Given that document servers often handle critical corporate data and collaborative documents, exploitation could lead to data leakage, intellectual property theft, or exposure of credentials and configuration details. The remote and unauthenticated nature of the vulnerability increases the threat, especially for publicly accessible document servers. However, the medium CVSS score and the vendor's indication that exploitation attempts return proper error responses suggest that exploitation may be somewhat limited or detectable. Still, organizations in sectors with high regulatory requirements for data protection (e.g., finance, healthcare, government) could face compliance risks if sensitive data is exposed. The impact on integrity and availability is limited, but confidentiality breaches could have reputational and operational consequences.

Summary

CVE-2025-10777 is a medium-severity path traversal vulnerability found in the JSC R7 R7-Office Document Server, specifically affecting versions up to 20250820. The vulnerability resides in an unspecified function related to the /downloadas/ file path, where manipulation of the 'cmd' argument can lead to unauthorized path traversal. This flaw allows an attacker to remotely craft requests that traverse directories on the server, potentially accessing files outside the intended directory scope. Although the exact impact on confidentiality and integrity depends on the server's file system permissions and configuration, path traversal vulnerabilities generally risk unauthorized disclosure of sensitive files or server-side information. The vendor has confirmed the vulnerability and released a patch in version 2025.3.1.923, which mitigates the issue by ensuring proper error handling and preventing exploitation. Notably, the vulnerability requires no user interaction and no authentication, increasing its risk profile. However, the attack complexity is low, and the vulnerability does not affect availability directly. The R7-Office Document Server is a fork of OpenOffice, but the OpenOffice team has not been able to reproduce this issue in their codebase, suggesting this vulnerability is specific to the JSC R7 fork. No known exploits are currently reported in the wild.

References

Community reviews

Loading reviews…