Directory traversal vulnerability in the yccms 3.3 project.

published 2021-02-01 5y ago modified 2026-06-17 4mo ago also EUVD-2020-13077

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

Directory traversal vulnerability in the yccms 3.3 project. The delete, deletesite, and deleteAll functions' improper judgment of the request parameters, triggers a directory traversal vulnerability.

Is CVE-2020-20290 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

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

Exploits and checks

blog.jiguang.xyz https://blog.jiguang.xyz/posts/yccms-directory-traversal-vulnerability-report/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	6.4	AV:N/AC:L/Au:N/C:N/I:P/A:P

Classification

Weakness

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

References

blog.jiguang.xyz /posts/yccms-directory-traversal-vulnerability-report/
exploit, third-party-advisory

Sources

CVE List CVE-2020-20290
NVD CVE-2020-20290

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.