Exponent CMS up to 2.5.x cron/find_help.php input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Exponent CMS up to 2.5.x. This issue affects some unknown processing of the file cron/find_help.php. This manipulation causes input validation. This vulnerability is tracked as CVE-2016-9023. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in Exponent CMS up to 2.5.x (Content Management System) and classified as critical. Affected by this vulnerability is an unknown code of the file cron/find_help.php. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 12/31/2020 as a8efd9ca71fc9b8b843ad0910d435d237482ee31. The advisory is shared at github.com. This vulnerability is known as CVE-2016-9023. Technical details are known, but no exploit is available.
By approaching the search of inurl:cron/find_help.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.6.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CMS 2.6.0
Patch: github.com
Timeline
12/31/2020 🔍12/31/2020 🔍
12/31/2020 🔍
Sources
Advisory: a8efd9ca71fc9b8b843ad0910d435d237482ee31Status: Confirmed
CVE: CVE-2016-9023 (🔍)
GCVE (CVE): GCVE-0-2016-9023
GCVE (VulDB): GCVE-100-167017
Entry
Created: 12/31/2020 08:39Changes: 12/31/2020 08:39 (41)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.