Appcms is a focused web content-management product where vulnerabilities concentrate in application-layer input handling, particularly cross-site scripting and SQL injection flaws that reflect the risks inherent to user-supplied data processing in web platforms. The vendor's disclosures frequently acquire public exploit code, making timely patching important for deployed instances. Current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Appcms over time
Signals from CVEs in this vendor scope (6 CVEs).
6 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2021-45380MEDIUM AppCMS 2.0.101 has a XSS injection vulnerability in \templates\m\inc_head.php | Jan 23, 2022 | 6.1 | 25 | NO | YES |
CVE-2020-36007MEDIUM AppCMS 2.0.101 in /admin/template/tpl_app.php has a cross site scripting attack vulnerability which allows the attacker to obtain sensitive information of other users. | Jun 3, 2021 | 6.1 | 21 | NO | NO |
CVE-2020-36005MEDIUM AppCMS 2.0.101 in /admin/app.php has an arbitrary file deletion vulnerability which allows attackers to delete arbitrary files on the site. | Jun 3, 2021 | 6.5 | 21 | NO | NO |
CVE-2020-36006MEDIUM AppCMS 2.0.101 in /admin/info.php has an arbitrary file deletion vulnerability which allows attackers to delete arbitrary files on the site. | Jun 3, 2021 | 6.5 | 20 | NO | NO |
CVE-2020-36004MEDIUM AppCMS 2.0.101 in /admin/download_frame.php has a SQL injection vulnerability which allows attackers to obtain sensitive database information. | Jun 3, 2021 | 6.5 | 20 | NO | NO |
CVE-2019-9595MEDIUM AppCMS 2.0.101 allows XSS via the upload/callback.php params parameter. | Mar 6, 2019 | 6.1 | 17 | NO | NO |
Signals from CVEs in this vendor scope (6 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Appcms.
Media articles that mention a CVE ID that affects a product developed by Appcms — matched by CVE ID, not by vendor name.