AtomXCMS 2.0 is affected by Arbitrary File Read via admin/dump.php

published 2020-10-22 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-19192

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

Exploit prediction

1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/Drunyacoder/AtomXCMS-2/issues/20 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory
CWE-668 Exposure of Resource to Wrong Sphere

References

github.com /Drunyacoder/AtomXCMS-2/issues/20
exploit, issue-tracking, third-party-advisory

Sources

CVE List CVE-2020-26650
NVD CVE-2020-26650

Fencer Vulns 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.

Summary