A RCE vulnerability exists in Raysync below 3.3.3.8.

published 2020-12-23 5y ago modified 2026-06-17 4mo ago also EUVD-2020-23046

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 7.8%; EPSS 7.8% chance of exploitation in 30 days, percentile 94%
public exploits: 0; none known

A RCE vulnerability exists in Raysync below 3.3.3.8. An unauthenticated unauthorized attacker sending a specifically crafted request to override the specific file in server with malicious content can login as "admin", then to modify specific shell file to achieve remote code execution(RCE) on the hosting server.

Patch / fix

fixed in 1

raysync raysync 3.3.3.8

Is CVE-2020-35370 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

7.79% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

exploit-db.com https://www.exploit-db.com/exploits/49265 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

exploit-db.com /exploits/49265
exploit, third-party-advisory, vdb-entry

Sources

CVE List CVE-2020-35370
NVD CVE-2020-35370

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.