CVE-2018-18942 json
RCE in baserCMS before 4.1.4
published 8y ago modified last mo. also GHSA-rjc2-x53r-6c9r , EUVD-2022-5187
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
In baserCMS before 4.1.4, lib\Baser\Model\ThemeConfig.php allows remote attackers to execute arbitrary PHP code via the admin/theme_configs/form data[ThemeConfig][logo] parameter.
Patch / fix
- packagist baserproject/basercms 4.1.4
- basercms basercms 4.1.4
Is CVE-2018-18942 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.40% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- sunu11.com http://sunu11.com/2018/10/31/baserCMS/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| GitHub | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | baserproject/basercms | <4.1.4 |
4.1.4 |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
sunu11.com
/2018/10/31/baserCMS/
exploit, third-party-advisory
-
basercms.net
/release/4_1_4
release-notes, vendor-advisory
-
github.com
/baserproject/basercms/issues/959
web, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-18942
advisory
-
web.archive.org
/web/20200130073341/https://basercms.net/release/4_1_4
web
-
web.archive.org
/web/20211209034642/http://sunu11.com/2018/10/31/baserCMS
web
Sources
- CVE List CVE-2018-18942
- GitHub Advisory GHSA-rjc2-x53r-6c9r
- NVD CVE-2018-18942
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.