CVE-2026-16601 json
CM Map Locations <= 2.1.8 - Authenticated (Subscriber+) Arbitrary File Upload via cmloc_route_image_upload AJAX Action
published 2mo ago modified 2mo ago also EUVD-2026-65313
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
The CM Map Locations – Visualize and share your locations in a few clicks plugin for WordPress is vulnerable to Limited Arbitrary File Upload in all versions up to, and including, 2.1.8 via the uploadMedia function. This is due to insufficient file type validation in the upload handler, which performs incomplete extension filtering without MIME-type checks or upload capability verification before passing attacker-supplied files to move_uploaded_file(). This makes it possible for authenticated attackers, with subscriber-level access and above, to upload files that may be executable, which makes remote code execution possible. The required nonce is exposed to any logged-in Subscriber via the CMLOC_Editor_Images JavaScript object on the front-end location editor page.
Is CVE-2026-16601 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
1.17% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- creativemindssolutions CM Map Locations – Visualize and share your locations in a few clicks
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/41308ae8-1b3d-4658-808d-630d6e673f3f?source=cve
- plugins.trac.wordpress.org /browser/cm-map-locations/tags/2.1.8/core/controller/Controller.php#L45
- plugins.trac.wordpress.org /browser/cm-map-locations/tags/2.1.8/controller/DashboardController.php#L385
- plugins.trac.wordpress.org /browser/cm-map-locations/tags/2.1.8/model/Route.php#L362
- plugins.trac.wordpress.org /browser/cm-map-locations/tags/2.1.8/model/Attachment.php#L240
- plugins.trac.wordpress.org /browser/cm-map-locations/tags/2.1.8/controller/DashboardController.php#L105
- plugins.trac.wordpress.org /changeset?reponame=&new=3626853%40cm-map-locations%2Ftags%2F2.1.9&old=3544748%40cm-map-locations%2Ftags%2F2.1
- plugins.trac.wordpress.org /changeset/3626848/cm-map-locations/trunk/controller/DashboardController.php
- plugins.trac.wordpress.org /changeset?old_path=%2Fcm-map-locations/tags/2.1.8&new_path=%2Fcm-map-locations/tags/2.1.9
Sources
- CVE List CVE-2026-16601
- NVD CVE-2026-16601
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.