dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-10777

MEDIUM · 6.3 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A path traversal vulnerability exists in JSC R7 R7-Office Document Server's /downloadas/ endpoint. By manipulating the 'cmd' argument, an attacker can potentially access files outside the intended directory. The vulnerability is exploitable remotely.

MitigationUpgrade to version 2025.3.1.923 to patch the path traversal vulnerability. Until upgrade, consider restricting network access to the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm R7-Office Document Server is running
    Identify the running service by checking running processes, listening ports (commonly 8000 or 8080), or consulting your service inventory
    Affected if R7-Office Document Server is present in the environment
  2. Check installed version
    Retrieve the version from the installation directory, package manager, or API endpoint (commonly /info or /health), then compare to the fixed version 2025.3.1.923
    Affected if Installed version is lower than 2025.3.1.923
  3. Verify /downloadas/ endpoint is network accessible
    Test HTTP/HTTPS access to the /downloadas/ endpoint from external networks or confirm network exposure through firewall rules or reverse proxy configuration
    Affected if The endpoint is exposed to untrusted networks without proper access restrictions
  4. Review access logs for path traversal attempts
    Search application and web server logs for patterns like '../' or '..\' in requests to /downloadas/, particularly in the cmd parameter
    Affected if Log entries reveal suspicious path traversal patterns in /downloadas/ requests

Environment is affected if R7-Office Document Server is running with a version below 2025.3.1.923 and the /downloadas/ endpoint is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 2025.3.1.923 to patch the path traversal vulnerability. Until upgrade, consider restricting network access to the affected endpoint.

Recommended fix High confidence

2025.3.1.923

  1. 1. Identify the current version of JSC R7 R7-Office Document Server by checking the server configuration or about page
  2. 2. Create a complete backup of the server data, configuration files, and any documents stored on the server
  3. 3. Download the patched version 2025.3.1.923 from the official R7 vendor channels
  4. 4. Stop the R7-Office Document Server service before applying the upgrade
  5. 5. Install version 2025.3.1.923 following the vendor's standard upgrade procedure
  6. 6. Restart the R7-Office Document Server service
  7. 7. Verify the upgrade was successful by checking the running version number
  8. 8. Test that the /downloadas/ endpoint with manipulated 'cmd' arguments now returns proper error responses and no longer allows path traversal

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data