CVE-2021-24375 json
Motor theme < 3.1.0 - Local File Inclusion
published 5y ago modified 4mo ago also EUVD-2021-11287
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
Lack of authentication or validation in motor_load_more, motor_gallery_load_more, motor_quick_view and motor_project_quick_view AJAX handlers of the Motor WordPress theme before 3.1.0 allows an unauthenticated attacker access to arbitrary files in the server file system, and to execute arbitrary php scripts found on the server file system. We found no vulnerability for uploading files with this theme, so any scripts to be executed must already be on the server file system.
Patch / fix
- stockware motor 3.1.0
Is CVE-2021-24375 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 FencerExploit prediction
2.63% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/d9518429-79d3-4b13-88ff-3722d05efa9f referenced PoC, tagged "exploit" by a source, unverified
- jetpack.com https://jetpack.com/2021/06/09/motor-wordpress-theme-vulnerabilities/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Stockware Motor
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
wpscan.com
/vulnerability/d9518429-79d3-4b13-88ff-3722d05efa9f
exploit, third-party-advisory
-
jetpack.com
/2021/06/09/motor-wordpress-theme-vulnerabilities/
exploit, third-party-advisory
Sources
- CVE List CVE-2021-24375
- NVD CVE-2021-24375
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.