CVE-2020-23972 in the critical feed json
In Joomla Component GMapFP Version J3.5 and J3.5free, an attacker can access the upload function without authenticating to the application…
published 6y ago modified 4mo ago also EUVD-2020-16708
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 31.4%
- EPSS 31.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB, plus a Nuclei check
Summary
In Joomla Component GMapFP Version J3.5 and J3.5free, an attacker can access the upload function without authenticating to the application and can also upload files which due to issues of unrestricted file uploads which can be bypassed by changing the content-type and name file too double extensions.
Is CVE-2020-23972 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 FencerTimeline
- Published
- First public exploit (EDB-49129)
Exploit prediction
31.44% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-49129 Joomla! Component GMapFP 3.5 - Unauthenticated Arbitrary File Upload webapps, 2020-12-01
- Nuclei template Joomla! Component GMapFP 3.5 - Arbitrary File Upload nuclei detection template
- raw.githubusercontent.com https://raw.githubusercontent.com/me4yoursecurity/Reports/master/README.md 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 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
raw.githubusercontent.com
/me4yoursecurity/Reports/master/README.md
exploit, third-party-advisory
-
packetstormsecurity.com
/files/159072/Joomla-GMapFP-J3.5-J3.5F-Arbitrary-File-Upload.html
third-party-advisory
Sources
- CVE List CVE-2020-23972
- NVD CVE-2020-23972
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.